Cleaning up Replication Monitor

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 7,2000 » Replication » Cleaning up Replication Monitor

22 posts, Page 2 of 3

««1 2 3 »»

Cleaning up Replication Monitor

Rate Topic

Display Mode

Topic Options

Author

Message

Wired-528862

Posted Friday, August 08, 2008 8:45 AM

Forum Newbie

Group: General Forum Members
Last Login: Friday, September 03, 2010 3:29 PM
Points: 8, Visits: 48

I would still try what Nuwins suggests. If you're having the same problem as the others on here, we didn't have an issue with the subscription, but rather the publication was still showing up when it is actually not there. This is really just a way to trick SQL. I believe once you delete a server with subscriptions on it, it contacts the distribution server and deletes those subscriptions; however, the publications can still exist. I could be wrong though.

Post #549268

annejo

Posted Friday, August 08, 2008 1:18 PM

SSC Journeyman

Group: General Forum Members
Last Login: Wednesday, September 29, 2010 1:53 PM
Points: 78, Visits: 198

This same thing has happened to me and what resolved it in my case was to open up the MSreplication_agent_status table in tempdb and delete a record that had a publication named the same as the one I had been trying to get rid of in the first place. No more red Xs!

Post #549545

madyson3

Posted Tuesday, March 31, 2009 8:31 AM

Forum Newbie

Group: General Forum Members
Last Login: Monday, May 13, 2013 12:25 PM
Points: 7, Visits: 123

I also had to remove remenents of the subscription from the distribution database. Tables: MSsubscriptions and MSpublications

Post #687099

ceeatch

Posted Friday, March 05, 2010 5:59 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, August 31, 2011 4:54 AM
Points: 1, Visits: 101

Take a look at distribution.dbo.MSReplication_Monitordata as well. It may indicate that you have a logreader agent still set up. I had to remove it from the MSlogreader_agents table in order for my monitor to stop reporting a replication issue when there wasn't any.

EDIT: SQL2005

Post #877561

wmleonar

Posted Friday, March 05, 2010 6:35 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, January 17, 2012 12:29 PM
Points: 1, Visits: 122

Nice solution, added a merge publication with the same name and was able to clear replication monitor. Thanks again!

Post #877584

Martin-226012

Posted Tuesday, April 06, 2010 9:25 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, December 05, 2012 11:09 AM
Points: 4, Visits: 85

Nice !!
Adding a new Publication with the name and the deleting it worked perfectly.
Many Thanks

Post #897633

praveen.srpk

Posted Friday, August 06, 2010 7:40 AM

Forum Newbie

Group: General Forum Members
Last Login: Saturday, February 18, 2012 12:10 AM
Points: 1, Visits: 56

Bravo...I'm gratified with your solution. It worked... Smile

Post #965151

DBA-640728

Posted Thursday, January 06, 2011 10:40 AM

SSC-Addicted

Group: General Forum Members
Last Login: Wednesday, May 08, 2013 5:21 PM
Points: 496, Visits: 1,724

what about if you just remove the publication from the table select * from MSpublications , would that work too?

Post #1043882

Resender

Posted Friday, April 22, 2011 2:45 AM

SSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 8:55 AM
Points: 289, Visits: 683

I got the same problem on a SQL Server 2008, a general database failure (the files got deleted and the database was put offline by sql server at the same time)occured yesterday in 1 of our non-critical databases.
It was quickly restored but the replication was unable to work again, after spending a few hours looking I found out a new publication had been created on the restored database and that this was conflicting with the publication from for the crash.

This was strange since our company policy in such cases says that the old publication has to be removed and recreated. We found out that we could recreate the publication under the old name but their were still problems. Deleting it kept it in the replication monitor, this morning I once again recreated the publication under the same name and deleted it and the publication was removed in replication monitor.

Post #1097366

Roderick McBan

Posted Thursday, October 13, 2011 6:02 AM

Forum Newbie

Group: General Forum Members
Last Login: Wednesday, June 06, 2012 6:21 AM
Points: 1, Visits: 30

Old thread but the trick of creating a new subscription to the same target box and then cleaning it up using exec sp_dropmergesubscription worked for me too.
Replication monitor is not clean and not reporting any errors.

Oh, and I am under 2008R2

Post #1189758

« Prev Topic | Next Topic »

22 posts, Page 2 of 3

««1 2 3 »»

Permissions