Post reply

Merge OR Peer to Peer Transactional replication?

  • December 28, 2010 at 12:14 am

    #232393

    Hi all,

    I'm confused in choosing the appropriate replication type (Peer to Peer Transactional or Merge).

    My Requirements:

    1) 1 Publisher and 1 Updatable Subscriber (I can maintain the range with my own logic so that there wont be any conflict while adding an entry)

    2) When an article is modified in Publisher, the change should be reflected to the Subscriber instantly and vice versa.

    3) If conflicts occur because of editing the same rows, the last modified article should win the conflict. Is it possible to configure this globally for all articles without adding TIMESTAMP column to every article?

    I went through some of the replication documents, but I have a doubt whether to choose Merge Replication or Peer to Peer Transactional replication.

    Please advise.

    Thanks & Regards,

    Kumaran

  • December 28, 2010 at 3:54 am

    #1266662

    as you posted this in sql 2005 forum i would go for merge. As peer to peer is only sql 2008 enterprise

  • December 28, 2010 at 4:09 am

    #1266668

    in perr-to-peer the other node is acting as subscriber, but as publisher. So both node will act as publisher and subscriber for each other

    ----------
    Ashish

  • December 28, 2010 at 4:27 am

    #1266676

    @Macro: Thanks for the reply. I have started a new thread under SQL2K8 section. Also, whats the difference between peer to peer replication and transactional replication with subscriber updatable.

    @Ashish: Thanks for your reply. Is it possible to have multiple subscribers in peer to peer replication? Also, is it possible to achieve the second point(in my main post) using Merge Replication?

    Thanks & Regards,

    Kumaran

  • December 29, 2010 at 12:06 am

    #1267038

    peer to peer is designed for low latency envoriments its the adult version of bi directional transactional replication

    merge is designed for envoriment where most of the times the "client" databases are not connected but synchronize when they are connected.

    handling conflicts

    peer to peer

    http://technet.microsoft.com/en-us/library/bb934199.aspx

    merge

    http://technet.microsoft.com/en-us/library/ms151257.aspx

    the handling conflicts of peer to peer is not the prettiest and manual labor. Guess it all depends on the application which fits you the best

Viewing 5 posts - 1 through 4 (of 4 total)

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