Post reply

Merge or Transactional Replication

  • March 12, 2010 at 12:55 am

    #217786

    Hi All

    I have a database on two server and I want to have same data on them. Some tables are updated on one of servers and some on another server and any table need updating on both server.

    Which of merge or bidirectional replication topology is better for my case?

    Thanks

  • March 12, 2010 at 2:45 am

    #1132536

    if u're running enterprise edition, you can go for peer to peer replication...


    Pradeep Singh

  • March 12, 2010 at 3:33 am

    #1132550

    Thanks. I'm going to read about peer to peer.

  • March 12, 2010 at 3:59 am

    #1132555

    Paul Ibison's site is good for replication.

    www.replicationanswers.com[/URL]

    You can start P2P replication here


    Pradeep Singh

  • March 12, 2010 at 11:06 pm

    #1133135

    Dear Pradeep

    I want to separate updating data on each server so that some data will updated on one server and some on another for avoiding conflicts, but it seems that in P2P you can define only one publication and all servers should work by this publication.I think bidirectional transaction is better because I can define two publication with their related tables on each server. Aren't you agree?

    Thanks

  • March 12, 2010 at 11:39 pm

    #1133143

    Looks like Merge replication will suit your requirement not peer to peer, elaborate your business requirements we can suggest you which replication.

    From BOL

    To avoid potential data inconsistency, make sure that you avoid conflicts in a peer-to-peer topology, even with conflict detection enabled. To ensure that write operations for a particular row are performed at only one node, applications that access and change data must partition insert, update, and delete operations. This partitioning ensures that modifications to a given row originating at one node are synchronized with all other nodes in the topology before the row is modified by a different node. If an application requires sophisticated conflict detection and resolution capabilities, use merge replication. For more information, see Merge Replication Overview and Detecting and Resolving Merge Replication Conflicts.

    EnjoY!

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

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