Removing conflict Tables after replication is removed

Removing conflict Tables after replication is removed

Post by David Gabrielso » Wed, 19 Dec 2001 02:17:55



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

 
 
 

Removing conflict Tables after replication is removed

Post by Sre?ko Kosmin » Wed, 19 Dec 2001 05:30:51


Hello David,
we had the same problem with 'onflict's. Now we execute a simple drop
script in QA, like:
DROP TABLE aonflict_<tablename>
DROP TABLE bonflict_<tablename>
...
We prepare script with a simple program, which searches DB and creates a
drop for each table, containing 'onflict' in tablename.
Regards - Srecko

David Gabrielson je napisal:

> 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



 
 
 

Removing conflict Tables after replication is removed

Post by David Gabrielso » Wed, 19 Dec 2001 06:21:00


Quote:>Hello David,
>we had the same problem with 'onflict's. Now we execute a simple drop
>script in QA, like:
>DROP TABLE aonflict_<tablename>
>DROP TABLE bonflict_<tablename>
>...
>We prepare script with a simple program, which searches DB and creates a
>drop for each table, containing 'onflict' in tablename.
>Regards - Srecko

Thank you....

    I was trying to do drop the conflict_xxx tables under the Enterprise
Manager.   Enterprise Manager has the conflict tables marked as System and
would not allow me to drop them.  Once I tried droping the tables under
Query Analyzer, they dropped like flies!!!