Replication for deployment

  • I want to know if anyone has used replication to keep 2 servers in line with each other making down time minimal during deployments / system maintenance.

    E.g. Server A and Server B in line. Server A downed for maintenance while transactions accumulate on Server B. Once maintenance finished on Server A, it is tested and once all is okay, the accumulated transactions on Server B need to be updated to Server A before. This is where it gets difficuilt, anyway, say you get the data back on to Server A so Server A and Server B are in line with each other, Server B is downed so the updates can be applied to it. Once again, while Server B is down, transactions are accumulating on Server A so these also need to be brought accross to Server B once Server B is back on-line.

    Has anyone used SQL Replication to achieve this? If so, what type of replication and how?

    Cheers

    Deon

  • I'm sure people will have done it, but the maintenance of it is a nightmare. Try looking at http://www.incepto.com, their product SQLup is going to be reviewed by Brian Knight soon (hopefully the sooner the better!!).

    Regards

    Simon

  • Thanks for the prompt reply and I will have a look at the suggested site.

    Cheers

    Deon

  • Merge replication might not be so bad, that way you can make your changes to data on either server.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

  • Wouldn't using merge replication require a lot of coding to resolve conflicts, or are you assuming that either A OR B are live at any moment, but never both receiving transactions?

    If this were to be adopted, would you configure a third server to work as the distributor for A and B ?

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

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