Skip to main content
Database Administrators

Return to Question

Notice removed Draw attention by BeginnerDBA
Bounty Ended with Kin Shah's answer chosen by BeginnerDBA
Tweeted twitter.com/StackDBAs/status/1267561597058396160
added 10 characters in body
Source Link
BeginnerDBA
BeginnerDBA
  • 2.2k
  • 3
  • 26
  • 53

I was of belief that changing compatibility mode on primary database in database mirroring would make the change for mirror database.

But it proved to be wrong. I queried using sys.databasessys.databases on Primary where i changed compatibility mode to 120 , however on its mirrored database comptcompatibility level was still 100. Why?

Am i using the incorrect fn here sys.databases?

Also if it does not change what does it mean, do i need to do failover/failback to reflect?

What if i had log shipping secondary database in read only as well where this change needs to reflect? Do i need to rebuild log shipping then?

Thanks

I was of belief that changing compatibility mode on primary database in database mirroring would make the change for mirror database.

But it proved to be wrong. I queried using sys.databases on Primary where i changed compatibility mode to 120 , however on its mirrored database compt level was still 100. Why?

Am i using the incorrect fn here sys.databases?

Also if it does not change what does it mean, do i need to do failover/failback to reflect?

What if i had log shipping secondary database in read only as well where this change needs to reflect? Do i need to rebuild log shipping then?

Thanks

I was of belief that changing compatibility mode on primary database in database mirroring would make the change for mirror database.

But it proved to be wrong. I queried using sys.databases on Primary where i changed compatibility mode to 120 , however on its mirrored database compatibility level was still 100. Why?

Am i using the incorrect fn here sys.databases?

Also if it does not change what does it mean, do i need to do failover/failback to reflect?

What if i had log shipping secondary database in read only as well where this change needs to reflect? Do i need to rebuild log shipping then?

Thanks

Notice added Draw attention by BeginnerDBA
Bounty Started worth 50 reputation by BeginnerDBA
tag correction.
Link
edit approved May 29, 2020 at 1:17
Ronaldo
edit approved May 29, 2020 at 1:17
Ronaldo
  • 5.9k
  • 1
  • 13
  • 43
Source Link
BeginnerDBA
BeginnerDBA
  • 2.2k
  • 3
  • 26
  • 53

Compatibility mode change does not reflect on secondaries

I was of belief that changing compatibility mode on primary database in database mirroring would make the change for mirror database.

But it proved to be wrong. I queried using sys.databases on Primary where i changed compatibility mode to 120 , however on its mirrored database compt level was still 100. Why?

Am i using the incorrect fn here sys.databases?

Also if it does not change what does it mean, do i need to do failover/failback to reflect?

What if i had log shipping secondary database in read only as well where this change needs to reflect? Do i need to rebuild log shipping then?

Thanks