Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
 Posted - 2010-11-05 : 13:55:48
|
| I had transactional replication established on three databases. Two of these databases have been obsoleted and dropped BUT the replication is still showing up in Replication Monitor and (surprise! surprise!) are showing errors.The publications no longer appear under the publisher's list of local publications nor on any of the subscriber's list of local subscriptions.I'd like to remove these orphaned publications but all of the usual system procedures involve being run on or referencing the publishing database which, by now, does not exist.Ideally, I would not have to disable publishing for the entire server since the third, active, replicating database is, of course, the huge data source.Any ideas?=======================================In all life one should comfort the afflicted, but verily, also, one should afflict the comfortable, and especially when they are comfortably, contentedly, even happily wrong. -John Kenneth Galbraith, economist (1908-2006) |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-11-05 : 14:02:49
|
My idea:restore an old backup, then remove publications...then delete that old db again.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
Bustaz Kool
Master Smack Fu Yak Hacker
1834 Posts |
Posted - 2010-11-05 : 14:07:05
|
| Thanks for your response. I'll give it a try.=======================================In all life one should comfort the afflicted, but verily, also, one should afflict the comfortable, and especially when they are comfortably, contentedly, even happily wrong. -John Kenneth Galbraith, economist (1908-2006) |
|
|
|
|
|
|
|
|
Dropped Databases Still Replicating