When pushing a major release to a large production database, you want to know that you'll be able to rollback changes if the need arises. These are some simple steps which we can follow to ensure that we don't have to reconfigure log shipping all over again thereby saving time and ensuring systems are not affected when rolling back changes.
Freshly minted MCM Wayne Sheffield fills a log shipping crack that could otherwise cause you to re-initialize your log shipping.
This tip I will explains a step-by-step method to perform the SQL Server Log Shipping migration.
I have a requirement to add the Log Shipping Monitor for an existing installation. I have heard you can only complete this by rebuilding the Log Shipping infrastructure. Is that true? Are there any other options? In this tip I will explain how we can add the Log Shipping monitor to a SQL Server 2005, 2008, 2008 R2 or 2012 environment without rebuilding the Log Shipping installation.
This topic explains the log shipping if the primary database is suspected or corrupted and how you can convert the secondary database into primary database.
This article describes the requirements to log ship databases between workgroup computers