Take the 2-minute tour ×

I am administering a SQL Server 2008 instance in a dev environment. At some point before I became an administrator, someone enabled log shipping from one of the databases on this dev instance to another dev instance. Now, the log shipping destination server no longer exists, and the source instance is creating hourly error log entries indicating the transaction log backups are severely out of sync. When I attempt to remove the destination server or disable log shipping for this database, I receive an error, since I cannot login to the nonexistent destination server.

Short of rebuilding the destination server, which is the last resort option, what can I do to disable log shipping without having to login to the destination server?

Thank you.

share|improve this question
add comment

migrated from stackoverflow.com Dec 16 '11 at 16:13

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 4 down vote accepted

You just need to run two stored procedures to remove the setup of log shipping from the primary database How to: Remove Log Shipping (Transact-SQL). As the secondary doesn't exist you shouldn't need to perform step 2 & 4.

share|improve this answer
This did the trick. Thanks! –  Andrew E Dec 16 '11 at 17:02
@AndrewE: if this did the trick, please mark this answer as the answer. You have a check mark near the voting signs. –  Marian Jan 23 '12 at 22:10
add comment

Your Answer


