Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question

migrated from Dec 16 '11 at 16:13

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

up vote 6 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

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.