by dave charlto » Sun, 24 Sep 2000 14:36:42
thought I'd share..
I had a database that thought it was being replicated, but even completely
uninstalling replication wouldn't help.
(I'm sure you've seen the issue before.)
Nonetheless, I stumbled across a stored procedure that quickly set things
right!
try:
sp_removedbreplication 'dbname'
1. Removing conflict Tables after replication is removed
I have a database that gone through the ringer with replication. Currently
the database is not replicated, but it still has all of the replication
tables in it (system tables). From my understanding if I add merge
replication back, the system will see the existing tables and start
lettering a new set of tables
conflict_AO_xxxx
aconflict_AO_xxxx
bconflict_AO_xxxx
I guess I am looking at how to remove these tables cleanly or the best
method to rebuild this database.
--
David Gabrielson
3. FYI some replication info that you will not find in Books Online
4. Identity value after INSERT
5. FYI the Solution - Replication was failing
6. transfer passwords to a new server
7. FYI, replication errors resolved...
9. FYI the Solution - Replication was failing
10. REMOVE, remove, PLEASE REMOVE this idoit out of this group
11. Removing merge replication/conflicting triggers
12. How to remove replication correctly