Running at older compatibility level – Database Health Monitor

In the November 2018 release of Database Health Monitor the check for older compatibility levels was added.

This check goes through all the databases on the server (excluding distribution that is used for Replication), and checks to see if the database is running on the latest compatibility level supported by your SQL Server.

Sometimes you may want to stay on an older compatibility level if there is something specific that your application needs or if it is not compatible with the latest SQL Compatibility level.

Here are some of the compatibility levels for SQL Server:

60 = SQL Server 6.0
65 = SQL Server 6.5
70 = SQL Server 7.0
80 = SQL Server 2000
90 = SQL Server 2005
100 = SQL Server 2008 and SQL Server 2008 R2
110 = SQL Server 2012
120 = SQL Server 2014
130 = SQL Server 2016
140 = SQL Server 2017
150 = SQL Server 2019

Here is the syntax to make the change.

ALTER DATABASE database_name SET COMPATIBILITY_LEVEL = { 150 | 140 | 130 | 120 | 110 | 100 | 90 }