asked on

Deleting Log Shipping

Hi. ServerA (2005) was log-shipping to ServerB to have a warm failover.

However, ServerB has completely bitten the dust and is with us no longer. ServerA, however, is not easily letting go of this log-shipping relationship.

Going into the GUI DB Properties of ServerA allows me to turn it off--theoretically--but the subsequent dialog after disabling log-shipping never ends. I think it's still waiting to hear from ServerB, who ain't never coming home.

I think I've killed the LS jobs in Agent.

How do I, as gracefully as possible, end this relationship? End log-shipping for certain databases on ServerA?

Thanks.

Ryan McCauley

If it's the only other server for which replication is configured, can you delete the publisher on the main server? If not, can you at least delete the publication? If you do, it will have nothing more to replicate, so that should end the relationship. If it was push replication, you may also be able to delete the subscription from the publisher as well to help end that relationship.

Though this is what the GUI should be doing, you may have more luck doing the TSQL directly instead of using the GUI:

http://msdn.microsoft.com/en-us/library/ms147833.aspx

bamapie

ASKER

Thanks, Ryan. I just don't know how to set this up, though.

Their example looks like this:

DECLARE @publication AS sysname;
SET @publication = N'AdvWorksProductTran';

-- Remove a transactional publication.
USE [AdventureWorks2008R2]
EXEC sp_droppublication @publication = @publication;

It's just not clear to me, however, what the value that they assign as 'AdvWorksProductTran' would be in my situation.

Thanks

ASKER CERTIFIED SOLUTION

bamapie

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bamapie

ASKER

This worked well and did what I needed when I couldn't get anything else to work.