Post reply

sql 2005 1 publisher and 2 subscribers for merge replication

  • November 18, 2010 at 7:25 am

    #243063

    Hi,

    We have 3 servers using sql 2005 having merge replication setup. If we use 1 publisher and 2 subscribers approach, can this replication topology handle single point of failure(i.e. when publisher server is down or not available, can the remaining 2 subscribers synchronize with each others?). If this approach cannot handle single point of failure, is there any other replication setup that can handle single point of failure and able to resolve conflicts for 3 servers using sql 2005?

    Thanks and regards,

    Wallace

  • November 18, 2010 at 8:19 am

    #1252554

    If the publisher was to fail there would be no way of syncronising between subscribers until the publisher was restored/recovered.

    Peer to Peer transactional replication could tollerate a single point of failure and requires Enterprise edition.

  • November 18, 2010 at 8:32 am

    #1252566

    MysteryJimbo (11/18/2010)

    If the publisher was to fail there would be no way of syncronising between subscribers until the publisher was restored/recovered.

    Peer to Peer transactional replication could tollerate a single point of failure and requires Enterprise edition.

    But as far as I know 2005 sql enterprise P2P transactional replication cannot resolve conflicts?

    Thanks and regards,

    Wallace

  • November 18, 2010 at 9:30 am

    #1252607

    Thats true, it depends on how likely concurrent editing is in the system. As the data is virtually real time this is usually sufficient.

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

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