Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rubs_65
Posting Yak Master
144 Posts |
 Posted - 2013-01-22 : 13:20:28
|
| We have a SQL Server 2008 database A hosted on a cluster and is involved in the following:• Replication to SQL Server 2008 database B (hosted on a cluster), Distributor is on Server A (same server as Publisher); Database B is also involved as Primary in log-shipping to databases E and F• Log-Shipping to SQL Server 2008 database C in standby-mode• CDC and that is used to refresh database DAll 3 database A,B and C are using compatibility mode(90, SQL Server 2005) that is not required anymore so we need to change the compatibility mode to 100.So we are wondering what is the recommended order of machines we need to change the compatibility (without breaking clustering, replication, log-shipping and CDC) and how will the change be propagated to log shipping secondary database. (we can test replication, log-shipping using test machine but we don’t have cluster in test environment)Thanks--Rubs |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2013-01-24 : 16:00:12
|
| As long as you aren't using any incompatible code, it won't break any of those.Nothing to do for clustering and replication. For log shipping, not 100% sure, but I think you'll need to change it on the target db at the same time as primary. |
 |
|
|
|
|
|
Changing compatibility mode question