alter compatibility level

All we need is an easy explanation of the problem, so here it is.

I plan to change the compatibility level on the databases in an sql server 2016 sp1 instance from 100 to 130. When upgraded from sql 2008 to sql 2016 the compatibility level was changed from 80 to 100.
I also am in the planning stages of installing the SP2 and the latest cumulative update.
What is best practice for changing the compatibility level – before or after the SP2 and cumulative updates are installed?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

What is best practice for changing the compatibility level – before or after the SP2 and cumulative updates are installed?

SQL Server 2016 SP1 is out-of-support so you should upgrade to supported service pack first.

Then the best practices for altering the database compatibility level are documented here: Change the Database Compatibility Level and use the Query Store

alter compatibility level

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply