Professional Microsoft® SQL Server® 2008 Administration
by Brian Knight, Ketan Patel, Wayne Snyder, Ross LoForte, Steven Wort
19.12. Upgrading to SQL Server 2008 Log Shipping
SQL Server 2005 log shipping cannot be directly upgraded to SQL Server 2008, as the log-shipping procedures have changed. Therefore, when upgrading a SQL Server 2005 instance, the log-shipping process stops functioning. There are three common approaches to upgrading log shipping.
19.12.1. Minimum Downtime Approach
The minimum downtime approach requires that the secondary server be upgraded in place using the setup program to SQL Server 2008 first. This will not break log shipping, because SQL Server 2005 transaction logs can be applied to SQL Server 2008. Afterward, a planned failover takes place whereby the role-switch procedures are followed and users are redirected to the secondary server, which has been promoted. After the role switch and after users are redirected, stop and disable the log shipping jobs. The newly upgraded SQL Server 2008 primary server cannot log-ship to the old primary server running SQL Server 2005.
Complete an in-place upgrade on the old primary server using the SQL Server 2008 setup program and leave it as the secondary server. Configure SQL Server 2008 log shipping from the new primary server to the secondary server using the same log-shipping shared folders used by SQL Server 2005. Additionally, in the Secondary Database Settings, on the Initialize Secondary Database page, choose "No, the Secondary database is initialized." SQL Server 2008 log shipping will then start shipping the transaction log. If ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access