SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Cleaning up Replication Monitor


Cleaning up Replication Monitor

Author
Message
Wired-528862
Wired-528862
SSC Veteran
SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)SSC Veteran (250 reputation)

Group: General Forum Members
Points: 250 Visits: 56
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.
annejo
annejo
SSC-Addicted
SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)SSC-Addicted (482 reputation)

Group: General Forum Members
Points: 482 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!



madyson3
madyson3
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 191
I also had to remove remenents of the subscription from the distribution database. Tables: MSsubscriptions and MSpublications
ceeatch
ceeatch
SSC Rookie
SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)SSC Rookie (37 reputation)

Group: General Forum Members
Points: 37 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
wmleonar
wmleonar
Valued Member
Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)Valued Member (51 reputation)

Group: General Forum Members
Points: 51 Visits: 123
Nice solution, added a merge publication with the same name and was able to clear replication monitor. Thanks again!
Martin-226012
Martin-226012
SSC-Enthusiastic
SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)SSC-Enthusiastic (108 reputation)

Group: General Forum Members
Points: 108 Visits: 86
Nice !!
Adding a new Publication with the name and the deleting it worked perfectly.
Many Thanks
praveen.srpk
praveen.srpk
SSC Rookie
SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)SSC Rookie (29 reputation)

Group: General Forum Members
Points: 29 Visits: 57
Bravo...I'm gratified with your solution. It worked...:-)
DBA-640728
DBA-640728
SSCertifiable
SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)SSCertifiable (7.5K reputation)

Group: General Forum Members
Points: 7512 Visits: 2005
what about if you just remove the publication from the table select * from MSpublications , would that work too?
Resender
Resender
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3846 Visits: 1578
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.
Roderick McBan
Roderick McBan
SSC Rookie
SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)SSC Rookie (45 reputation)

Group: General Forum Members
Points: 45 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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search