Help! cannot remove some of the replication remnants

Hope somebody can help because this is rather fustrating. I have recently
been doing some replication configurations between two servers. I started to
get a warning symbol on the replication monitor so I decided to uninstall
replication and start again. Unfortunately when I reinstall replication the
warning symbol returns.
How can I remove ALL history of replication on this server (I have tried
dropping distribution also). Although functinally replication still works
(regardless of icon) it is extremely annoying and does not relate to any
publications in existance.
Also I cannot remember any db names or publication names of those that were
published because they were dropped during cleanup.
Thanks in advance,
Mark
Mark,
if you've disabled publishing, this should take case of most things.
sp_removedbreplication can also be useful on individual databases.
Resrarting the services should remove error info on the replication monitor,
while sp_MSload_replication_status achieves the same but is less drastic.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||These commands may help:
sp_removedbreplication 'pubs' --replicated database on publisher
sp_dropdistpublisher @.publisher = '<sql server name>'
--, @.no_checks = no_checks
sp_dropdistributiondb distribution --name of dist db
Patrick
"Mark Broadbent" wrote:

> Hope somebody can help because this is rather fustrating. I have recently
> been doing some replication configurations between two servers. I started to
> get a warning symbol on the replication monitor so I decided to uninstall
> replication and start again. Unfortunately when I reinstall replication the
> warning symbol returns.
> How can I remove ALL history of replication on this server (I have tried
> dropping distribution also). Although functinally replication still works
> (regardless of icon) it is extremely annoying and does not relate to any
> publications in existance.
> Also I cannot remember any db names or publication names of those that were
> published because they were dropped during cleanup.
> Thanks in advance,
> Mark
|||disable replication. Then go through the databases looking for tables called
mssubscriptions or mspublications - the names elude me right now and I don't
have SQL installed on this machine.
Delete the content of these rows. Make sure mind you that you don't have any
active subscriptions on this database - other wise they will get hosed;)
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Broadbent" <Mark Broadbent@.discussions.microsoft.com> wrote in message
news:7CD45485-9352-449C-9170-618823D3856D@.microsoft.com...
> Hope somebody can help because this is rather fustrating. I have recently
> been doing some replication configurations between two servers. I started
> to
> get a warning symbol on the replication monitor so I decided to uninstall
> replication and start again. Unfortunately when I reinstall replication
> the
> warning symbol returns.
> How can I remove ALL history of replication on this server (I have tried
> dropping distribution also). Although functinally replication still works
> (regardless of icon) it is extremely annoying and does not relate to any
> publications in existance.
> Also I cannot remember any db names or publication names of those that
> were
> published because they were dropped during cleanup.
> Thanks in advance,
> Mark
|||Thanks Paul that stored proc did the trick. You have saved me a lot of grief,
thanks a million!
Thanks also to everyone else for their contributions.
"Paul Ibison" wrote:

> Mark,
> if you've disabled publishing, this should take case of most things.
> sp_removedbreplication can also be useful on individual databases.
> Resrarting the services should remove error info on the replication monitor,
> while sp_MSload_replication_status achieves the same but is less drastic.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>