Sync services, merge replication etc RRS feed

  • Question

  • I have been reading up on sync services, merge replication etc and been trying to map this to our scenario to see which fits best. We have several databases (geographically spread out) with for example customer data and users have access to "their" local database via a windowsapplication. Now we want to give the users access to all databases through a web-interface to be able to read the customerdata in each of the databases. To minimise network and db load, we are planning to have a database in the middle that will sync the data that needs to be accessible from the web-interface.


    So the question is, does Sync Services fit into this scenario? Or should we look more on the replication technologies like merge replication, transactional replication?

    Wednesday, November 5, 2008 7:46 AM


  • It depends on what capabilities you are looking for when replicating data.

    Trasactional replication gives you replication of data with low latency. So you would typically use it for high availability. It does not provide you rich filtering and conflict handling.

    Merge replication on the other hand provides you with rich filtering and conflict handling support. But it also comes with latency and some overhead because of change tracking using triggers.

    Both the above are packaged solutions and provide little flexibility and control on what and how you want to sync.

    Sync framework provides you with the flexibility and control on how and what you want to sync. It also provides you with filtering and conflict handling support. Like merge replication it handles disconnects well. It is complelty programming oriented approach of data sync.


    Please refer to our site: http://msdn.microsoft.com/en-us/sync/default.aspx for additional information.


    Thursday, November 6, 2008 6:21 AM