Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2006
    Posts
    13

    Unanswered: Bi-directional Transaction Replication

    Besides loopback detection, is there anything else that is needed to prevent the replication command from sending back to the source. Cos i am having problem with the subscriber B sending back the replication to A in the form of B as the publisher and A as the subscriber.



  2. #2
    Join Date
    May 2002
    Location
    General Deheza, Cba, Arg.
    Posts
    276
    hi
    what is the problem? a error in the sync. Can you writr more information about your problema.

    TIA
    Abel.

  3. #3
    Join Date
    Jan 2006
    Posts
    13
    It gives me an error " violation of primary key constraint..." And when i search the record at the subscriber, it shows that the record is already there. Meaning A send to B....then B send to A....If I'm not wrong in reading about loopback detection, B shouldnt send to A already...correct me if I'm wrong. Tks.

  4. #4
    Join Date
    May 2002
    Location
    General Deheza, Cba, Arg.
    Posts
    276
    hi, you have a Transactional replication in a SQL Server? this type of replication not is a "bi-direccional" (by defualt, the data of subscriber be read only, do you can't modified this data), how implement this replication?
    In your case use the merge, this type of replication is "bi-directional".

    bye.
    Abel.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •