SQL database compatibility level changes after applying Configuration Manager updates

Applies to: System Center Configuration Manager (current branch - version 1902)System Center Configuration Manager (current branch - version 1906)Microsoft Endpoint Configuration Manager (current branch)

Symptoms


After installing a Configuration Manager current branch update rollup or standalone update, the SQL database compatibility level unexpectedly changes from 110 (SQL Server 2012) to 130 (SQL Server 2016).
The current recommended compatability level value is 110 for sites that have encountered SQL performance issues.

This occurs if the site database server is using Microsoft SQL Server 2016, combined with the following Configuration Manager product versions:

  • System Center Configuration Manager current branch, version 1902
  • System Center Configuration Manager current branch, version 1906
  • Microsoft Endpoint Configuration Manager current branch, version 1910

For example, installing KB 4500571 Update rollup for System Center Configuration Manager current branch, version 1902 will change the database compatibility level from 110 to 130.

Note: Only sites that were updated from version 1706 or earlier are affected; sites that were originally installed at version 1710 or later will not encounter this issue.

Resolution


This issue is corrected with the release of the following:
KB 4537079 Update Rollup for Microsoft Endpoint Configuration Manager current branch, version 1910

Refer to the following documentation for additional details on the database compatability level.

Configuration Manager site sizing and performance FAQ

SQL query times out or console slow on certain Configuration Manager database queries

View or Change the Compatibility Level of a Database