Skip to main content
added 31 characters in body; edited title
Source Link
Tony Hinkle
  • 8k
  • 1
  • 22
  • 46

changing Changing master database compatibility level

We did an upgrade of SQL Server 2014 to 2016. In devthe development environment we did an inplacein-place upgrade. This, which left the master database at compatibility level 120. But in production we did migration to new server so there master is compatibility level 130.

I would like to have both environments as similar as possible. Additionally we have one application which is running its queries from the master database, so theoretically they can behave differently between environments.

Is it safe to change compatibility level of the master database from 120 to 130?

changing master database compatibility level

We did an upgrade of SQL Server 2014 to 2016. In dev environment we did an inplace upgrade. This left the master database at compatibility level 120. But in production we did migration to new server so there master is compatibility level 130.

I would like to have both environments as similar as possible. Additionally we have one application which is running its queries from master database, so theoretically they can behave differently between environments.

Is it safe to change compatibility level of master from 120 to 130?

Changing master database compatibility level

We did an upgrade of SQL Server 2014 to 2016. In the development environment we did an in-place upgrade, which left the master database at compatibility level 120. But in production we did migration to new server so there master is compatibility level 130.

I would like to have both environments as similar as possible. Additionally we have one application which is running its queries from the master database, so theoretically they can behave differently between environments.

Is it safe to change compatibility level of the master database from 120 to 130?

Source Link
rois
  • 595
  • 1
  • 4
  • 12

changing master database compatibility level

We did an upgrade of SQL Server 2014 to 2016. In dev environment we did an inplace upgrade. This left the master database at compatibility level 120. But in production we did migration to new server so there master is compatibility level 130.

I would like to have both environments as similar as possible. Additionally we have one application which is running its queries from master database, so theoretically they can behave differently between environments.

Is it safe to change compatibility level of master from 120 to 130?