Post reply

peer to peer replication

  • May 13, 2012 at 5:58 pm

    #260816

    can someone please point me in right direction (links to articles)

    i would like to impelment peer to peer replication with 2 nodes and allowing writes to be performed on only one node.

  • May 14, 2012 at 9:16 am

    #1487182

    DBA_AUS (5/13/2012)

    can someone please point me in right direction (links to articles)

    i would like to impelment peer to peer replication with 2 nodes and allowing writes to be performed on only one node.

    If you want to allow writes on only one server then peer to peer replication appears to be redundant. Can you let me know why you have chosen this replication technology?

  • May 14, 2012 at 10:12 am

    #1487231

    MysteryJimbo is correct. If writes occur on only one node, then you should be looking at transactional.

    If you are somehow trying to get people to connect to either node A or B, but writes on only node A, then you need separate connection strings for reading and writing. You could point the writes to Node A, but the reads could go through some load balancer to either node.

  • May 14, 2012 at 4:11 pm

    #1487435

    thanks for your response guys. yes my aim is to point reads to node A and B and writes to Node A only. but to achieve this i need to point reads and writes accordingly. can i do this at db level or it has to be done at app level. if at app level then this option isn't available means in that case i should forget about doing this. i should conside mirroring in that case.

  • May 14, 2012 at 4:22 pm

    #1487439

    There is no way in SQL Server 2008 to do this inside the database. Actually, this always is the app level, even in SQL Server 2012.

  • May 14, 2012 at 4:24 pm

    #1487440

    thx for your response. i thought so.

  • May 15, 2012 at 9:07 am

    #1487794

    DBA_AUS (5/14/2012)

    thanks for your response guys. yes my aim is to point reads to node A and B and writes to Node A only. but to achieve this i need to point reads and writes accordingly. can i do this at db level or it has to be done at app level. if at app level then this option isn't available means in that case i should forget about doing this. i should conside mirroring in that case.

    As Steve says it cant be done.

    You can implement third party load balancing using something like a Citrix netscalar but this would equally spread both reads and writes between two or more servers and you would have to allow for some latency between nodes in your application as you are likely to hit a different server with every connection.

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

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