February 14, 2009 at 4:53 am
Hi all, I deleted some replication(merge and transactional both) from SQL2005. yet those are displayed in the replication monitor showing error mark. Clicking on the details it gives the error that the publication do not exists. Can any one tell me how to remove those? Thanx in advance
February 16, 2009 at 12:50 am
Hi,
Try to use sp_droppublication and sp_dropmergepublication. You can find more info on them at bol.
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
February 16, 2009 at 4:12 am
Hi mohan thanks for the reply. But i have deleted the publication and the susbsciption databases also which are parameters to the SPs. yet the name of the replication appears in the replication monitor with the red crossed sign.
March 12, 2009 at 12:37 pm
One thought that might work -
Did you check the replication jobs that you have running? In theory, if you go in and disable the jobs (uncheck the 'enabled' box), then they won't run. IF all the jobs do is relate to replication, then even if you don't delete the jobs, they should not appear in your monitoring.
If you are really trying to eliminate all content, then delete jobs.
If you are doing a partial elimination, then remove the articles you no longer replicate.
This is terse and probably confusing, but it may help focus you without being long winded.
March 16, 2009 at 11:46 am
ritesh (2/16/2009)
Hi mohan thanks for the reply. But i have deleted the publication and the susbsciption databases also which are parameters to the SPs. yet the name of the replication appears in the replication monitor with the red crossed sign.
Right Click on the publisher and select "refresh".
* Noel
January 26, 2011 at 5:31 am
Hi all!
I got the same behavior. Finally searching the help for transact sql leads me to the sp
sp_removedistpublisherdbreplication
wich removes the obsolete entry in the replication monitor and in MSpublisher_databases, MSpublications, MSsnapshot_agents etc. as well.
Hth
Peter
January 27, 2011 at 2:15 am
I had this same problem and the only resolution that I found was to create a publication with the same name (using the same database) then delete it immediately (choose not to 'create snop shot immediately' and dont schedule', this then removed the entry from replication monitor. Next time I have this issue i will try the Sp suggested by the previous post.
Ash
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply