After migrating a database from SQL Server 2000 to 2008, in what situations is it justified to leave compatibility level to 80 permanently. The system consists of stored procs, triggers, views and tables only. No DTS, reports and other non-database engine stuff.
SQL Server compatibility level is one of the database settings. It helps to keep the database compatible with SQL server versions. By default compatibility level of the database is lower than the SQL server version. It impacts many objects in the server.
SQL Server 2019 allows you to directly upgrade from SQL Server 2008/R2 and keep the database compatibility to the earlier version.
The minimum compatibility level supported by SQL Server 2012 is 90, which is a SQL Server 2005 database. You will eventually get an error similar to: The database was backed up on a server running version 8.00. 0760. That version is incompatible with this server, which is running version 11.00.
SQL Server 2008 is not supported on Windows 10 or Windows Server 2016.
Some possible reasons:
*=
and =*
operators for outer
join are supported with a warning
message.PIVOT, UNPIVOT, REVERT, TABLESAMPLE
but not as keywordsSo if you are currently doing any of those things and don't want to rewrite anything you might consider staying at 80.
You can take a look at this link to see the full list.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With