how to completely remove replication?

What's the easiest scripted way to completely remove replication?
I've seen this article:
http://support.microsoft.com/default...b;en-us;324401
...but what I'd really like to find is a script that goes on a search
and destroy mission for replication related stuff (tables, data in
tables, jobs) and gets rid of it, without having to manually go through
all this.
The goal is to set up a test server with replication (it will be
publisher, distributor, and subscriber), and be able to rerun
replication setup from scripts - the first step being to remove
replication completely.
thanks for any tips,
Sylvia
have a look at this
http://groups.google.com/group/micro...7?dmode=source
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
"Sylvia" <sylvia@.vasilik.com> wrote in message
news:1130803614.051309.52110@.g49g2000cwa.googlegro ups.com...
> What's the easiest scripted way to completely remove replication?
> I've seen this article:
> http://support.microsoft.com/default...b;en-us;324401
> ...but what I'd really like to find is a script that goes on a search
> and destroy mission for replication related stuff (tables, data in
> tables, jobs) and gets rid of it, without having to manually go through
> all this.
> The goal is to set up a test server with replication (it will be
> publisher, distributor, and subscriber), and be able to rerun
> replication setup from scripts - the first step being to remove
> replication completely.
> thanks for any tips,
> Sylvia
>
|||Hilary Cotter wrote:
> have a look at this
> http://groups.google.com/group/micro...7?dmode=source
>
Thanks for the reference, Hilary, this looks very useful. I'm assuming
it's to be run in the Publication database?
One question - I'm confused as to why there's a lot of table create
statements at the end, instead of just deleting from those tables?
thanks,
Sylvia
|||It was meant for a subscriber, but it can be used for a publisher.
The create statements are there because if you restore a published db it may
be restored as published and then when you go to remove it, it will complain
about these missing objects.
"Sylvia" <Puget4753@.yahoo.com> wrote in message
news:1131998262.792041.14720@.g44g2000cwa.googlegro ups.com...
> Hilary Cotter wrote:
> Thanks for the reference, Hilary, this looks very useful. I'm assuming
> it's to be run in the Publication database?
> One question - I'm confused as to why there's a lot of table create
> statements at the end, instead of just deleting from those tables?
> thanks,
> Sylvia
>