What is compatibility level in SQL Server 2012?
Arguments
| Product | Database Engine Version | Supported Compatibility Level Values |
|---|---|---|
| SQL Server 2016 (13.x) | 13 | 130, 120, 110, 100 |
| SQL Server 2014 (12.x) | 12 | 120, 110, 100 |
| SQL Server 2012 (11.x) | 11 | 110, 100, 90 |
| SQL Server 2008 R2 | 10.5 | 100, 90, 80 |
What is the database compatibility level for SQL Server 2017?
When a SQL Server 2005 (9.x) database is upgraded to SQL Server 2017 (14.x), the database compatibility level will be changed from 90 to 100. (In SQL Server 2017 (14.x), valid values for the database compatibility level are 100, 110, 120, 130, and 140.)
Can a SQL Server 2005 database be upgraded to SQL Server 2017?
Restore a SQL Server 2005 (9.x) database to SQL Server 2017 (14.x) instance of database engine from a backup. Back up a SQL Server 2005 Analysis Services (SSAS) cube and restore it on SQL Server 2017 (14.x). When a SQL Server 2005 (9.x) database is upgraded to SQL Server 2017 (14.x), the database compatibility level will be changed from 90 to 100.
Why is Transact-SQL not protected by compatibility level?
Breaking changes introduced in a given SQL Server version may not be protected by compatibility level. This refers to behavior changes between versions of the SQL Server Database Engine. Transact-SQL behavior is usually protected by compatibility level. However, changed or removed system objects are not protected by compatibility level.
What’s the default compatibility level for Azure SQL?
As of November 2019, in Azure SQL Database, the default compatibility level is 150 for newly created databases. Microsoft does not update Database Compatibility Level for existing databases. It is up to customers to do at their own discretion.