Post reply

3 servers, 2 replications = 1 Name Conflict!

  • June 27, 2005 at 10:16 am

    #87931

    Hello again!

    I am implementing the following situation:

    a) Server A - MSDE replicates Table_x to Server B - MSDE.

    b) Server B - MSDE (has now Table_x and) replicates Table_x to Server C - SQL Server.

    All replications are Snapshot type.

    a) works well

    b) When I create the publication in Server B, replication in Server A get the error:

    "Cannot DROP Table_x because it is used for replication."

    I discover that the problem is a Name Conflict, because at the time is scheduled, the distribution agent cannot delete table_x in server B. That table is used by server B in replication!!!

    I solve the problem in article properties (Server A) in the tab Snapshot, Name Conflicts. I enabled "Delete all data in the existing table."

    I am correct?

    This is the best solution?

    Thanks!

    Claudia

     

    Regards,

    Cláudia Rego

    www.footballbesttips.com

  • June 28, 2005 at 4:42 am

    #568868

    you are correct - this is the way to do this.

     

    --

    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

  • June 28, 2005 at 10:54 am

    #569056

    why don't you just create 2 subscriptions, one from Server_a to Server_b and one from Server_a to Server_c. This is much more efficient and if Server_b dies data will still get replicated to Server_c.

    Good Luck...

    Don't count what you do, do what counts.

    SQL Draggon

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply