asked
Rolling upgrade to 2014 - Master compatibility issue
We recently upgraded from MSSQL 2008 to 2014. I discovered the master database still have 100 as the compatibility level. The upgrade went fine without problems. In the logging I see the upgrade steps from the master database without problems. This issue is also on servers which were upgraded from SQL2005. Any reason why this comptlevel is not altered? Any reason NOT to change the compt level?
It is default behavior for Master to be at a lower comp level after an upgrade. The main reason behind it is that upgrades should run more smoothly(not seen any official statements on this myself). If you have legacy systems that create objects in master they could be affected by compatibility changes after the upgrade. The downside is everything you can't do with an older compatibility level for master. So Microsoft apparently chose more successful upgrades for statistical reasons I guess. I can't find a reason for master to stay at a lower compatibility level than above. So if you have no legacy junk, you can raise it. **<- Please do this in test environment first** Couple of links on this: [master-database-compatibility-level-after-an-in-place-upgrade][1] [master-database-compatibility-level][2] [upgrading-comp-level-sql-server][3] [1]:
http://sqlblog.com/blogs/jonathan_kehayias/archive/2010/05/04/master-database-compatibility-level-after-an-in-place-upgrade.aspx [2]:
https://sqlrx.wordpress.com/2010/10/28/master-database-compatibility-level/ [3]:
http://blogs.lessthandot.com/index.php/datamgmt/dbadmin/upgrading-comp-level-sql-server/
15 People are following this question.
