August 14, 2009 at 1:06 pm
Hi,
We have configured Log shipping in SQL Server 2005, but the user database compatibility mode is 80 (we had upgraded from sql 2000) and everything working fine. Now we changed the compatibility mode of databases on Primary to 90 and Log shipping going on. But on Secondary instance, the databases are still in compatibility mode 80. How can we change the compatibility mode on Secondary instance with out disturbing the existing log shipping configuration? Is that possible?
August 14, 2009 at 1:27 pm
I am surprised it isn't logged shipped over to be honest??
August 16, 2009 at 5:19 am
If changing a compatibility mode isn't logged operation, i dont think you can achieve what you want to without breaking the configuration/re-setting it.
August 16, 2009 at 10:08 pm
after changing compatibility mode to 90 on Primary, we need to delete the databases on Secondary & reconfigure the Log shipping right?
August 16, 2009 at 10:42 pm
Yes.
August 16, 2009 at 11:06 pm
ps (8/16/2009)
If changing a compatibility mode isn't logged operation, i dont think you can achieve what you want to without breaking the configuration/re-setting it.
NO
i did a small test and found that .trn file captures the database compatibility mode and changes the secondary server database compatibility to 90 from 80 and vice versa as well.
August 16, 2009 at 11:22 pm
ps (8/16/2009)
If changing a compatibility mode isn't logged operation, i dont think you can achieve what you want to without breaking the configuration/re-setting it.
NO
i did a small test and found that .trn file captures the database compatibility mode and changes the secondary server database compatibility to 90 from 80 and vice versa as well.
August 16, 2009 at 11:24 pm
Sorry please ignore this post as it was wrongly posted here instead of other post. sorry
August 25, 2009 at 12:20 pm
Hi,
I have tested changing Compatibility mode 80 to 90 for Log shipping configured database. From the results:
1. I have configured log shipping in SQL Sevrer 2005 for a database having Compatibility mode 80 (which is upgraded from SQL 2000 to 2005)
2. Changed the Compatibilty mode to 90.
3. After the log applied to the Secondary instance, I brought the database online on secondary
4. Verified the Compatibilty on Secondary, It's 90.
So Changing Compatibility mode 80 to 90 is a LOGGED operation and Log shipping configuration won't break.
and also NO NEED to do the below:
after changing compatibility mode to 90 on Primary, we need to delete the databases on Secondary & reconfigure the Log shipping right?
thanks
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply