I am having the same issue but all the articles point to Sharepoint 2010. I am actually running SP2013 with SQL2014.
Title | Databases running in compatibility range, upgrade recommended. |
Severity | 2 - Warning |
Category | Configuration |
Explanation | The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range: Secure_Store_Service_DB_0e76051508ef46df8afa25edfb6725cd, Search_Service_Application_AnalyticsReportingStoreDB_898742c2d77b4f6eb3159836527f9f66, Bdc_Service_DB_b48450835c95487285ed7e927175bf8f, SharePoint_Config, Search_Service_Application_CrawlStoreDB_6d9196fc9918447298269f71bc9f546e, AppMng_Service_DB_0e09bc7070714993bcf060f673728c5f, SharePoint_AdminContent_620a2090-4215-467f-9f06-25aee07e473f, WSS_Content, Search_Service_Application_DB_e62d4b99016d46009b00cdc39a84f677, WSS_Logging, Search_Service_Application_LinksStoreDB_9f1c912edb3a419b8d05930e1d876136. |
Remedy | To achieve optimal results from these databases, use Upgrade-SPContentDatabase to upgrade Content databases, or psconfig.exe to upgrade other databases. For more information about this rule, see "http://go.microsoft.com/fwlink/?LinkID=142697". |
Failing Servers | |
Failing Services | SPTimerService (SPTimerV4) |
Rule Settings | View |
Microsoft manager to programmer: You start coding. I'll go find out what they want ...










