March 7, 2012 at 2:33 am
Hi All,
I have had a secondary server die, but has been replaced with a new host (different name), log shipping was reconfigured, have a standalone monitor server which is still alerting for the old secondary instance how can I remove this orphaned record?
using a sp or just manually hack it out of the tables?
Any help appreciated
March 7, 2012 at 3:02 pm
If anyone has a same issue i found a method that works.
So i cannot find any SP's that do the tidy up work for you.
On the monitor server check table log_shipping_monitor_secondary, this holds the monitored second instance details, simply removing that record cleans things up.
delete from [log_shipping_monitor_secondary]
where secondary_server = 'myinstance'
If anyone finds a better way please post it.
August 15, 2014 at 2:46 pm
I know this is old, but just in case anyone needs it. Looking in the master db and MSDN, I found sp_delete_log_shipping_secondary_database stored proc. Running this removed the entry for me.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply