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 |
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-04-27 : 09:16:19
|
It seems my transact replication is all mucked up. I've deletedthe publisher within replication/publications... but in replicationmonitor it still shows up... did not delete cleanly. When I runbackup scripted replication it produces this message 'Could not drop publication. A subscription exists to it.'Does anyone have any ideas how to clean this down and removeall previous repl setup. Ite seems that this is rather buggy asI've struggled with these types of issues before.Any help would be appreciated,John |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-27 : 09:37:07
|
You should remove subscribers first before deleting publication. |
 |
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-04-27 : 10:06:11
|
Using sp_dropsubscription will not work because I don't have the publisher and I dont' have the subscriber any more, they are just alone sql servers now both using sql 2000 |
 |
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-04-27 : 10:21:34
|
Any way to manually clean up?thank you |
 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-27 : 12:59:41
|
Go to tools -> replication in em, check if disable publishing and distrubition still available. |
 |
|
john.burns
Posting Yak Master
100 Posts |
Posted - 2007-04-27 : 15:13:27
|
I ended up cleaning manually. This worked well.Deleted from the following tables in dist. db:MSarticles MSdistribution_agentsMSdistribution_historyMSlogreader_agentsMSsnapshot_agents MSlogreader_historyMSsnapshot_historyMSsubscriber_infoMSsubscriptionsMspublications |
 |
|
|
|
|