ms sql 2k merge replication horror stories

Say you have an ms sql 2k server and are replicating a database using merge replication. What happens if you decide to stop merge replication. Normally the microsoft tools will clean up all of the triggers, and tables that replication adds. Unless of course you have tables owned by a user other than dbo. If that little situation arises, you my friend are in a world of hurt. To remove all of the cruft that is added I suggest looking at my wiki page regarding the fix. As usual, make backups before doing anything.

A quick look at the sysobjects, syscolumns are you're best friends in a situation like this. Just remember the object_name and user_name will come in handy.