New service update available for SQL Data Sync!

While it has been 3+ years since we last announced an update to SQL Data Sync service, we have been continuously deploying updates to the backend service to address top customer issues.  We are listening to your feedback, and today we are happy to announce the latest update which includes both service changes and a new SQL Data Sync agent install.  This update includes two main enhancements:

  1. Support for synchronizing tables that have column collations:
    • If the selected sync schema tables do not already exist in your hub or member databases, upon deploying the sync group, SQL Data Sync will automatically create corresponding tables and columns in the empty database with the same collation settings as the select sync schema.
    • If the tables to-be-synced are already created in both hub and member databases, SQL Data Sync requires the primary key columns have the same collation between hub/member databases to successfully deploy the sync group.  There is no collation restriction on the non-primary key columns.
  2. Improvements to performance and resilience:
    • We enhanced batch transfer of serialized changes from source to destination, so you should see faster sync throughput.
    • We improved transient error handling logic when reading from the source or writing to the destination.

The new version of SQL Data Sync agent in the download center.  Please follow the step-by-step instructions here to install a new Data Sync agent.  If you have an existing agent, you can refer to this MSDN article for detailed upgrade procedures.  A previous version of Data Sync agent will continue to work until it expires on 8/18/2015.

Comments (7)
  1. Bowen says:

    Cheer! Can't wait to upgrade to the latest version!

  2. Zach says:

    Noticed i lose the ability to use SSDT to generate a deployment preview when a database is added to SQL Data Sync. Is this a bug / intended behavior?

  3. Bowen says:

    @Zach, could you please provide more details about the issue you encountered? Generally, SQL Data Sync service/local agent won't "lock" any object on a database joined sync.

  4. Sigsby Rusk says:

    I just installed SyncSDK-v2.1-x64-ENU.msi  on my win7 desktop and in following the walkthrough demo on the web I discovered that I couldn't add a reference to "Microsoft.Synchronization.Data". What else do I need to install to get the assembly containing this reference?

  5. Tommy says:

    Dear Sync Team Blog,

    It seems that MSF is not under active development.  We are about to embark on a new project that requires synchronization as one of the core component.  

    From the Internet, there are a lot of talks/awareness/blogs/videos about MCF but somehow, they appear to be more conceptual and PoC than real implementation.  

    Would like to establish if MSF is a viable option given its current state of development from MSFT.



  6. Jupagose says:

    Hi. same as Tommy we are about to start a new project and could be usefull to know about the actual state of MSF. There is plans to maintain it?

    Is MSF a dead project ?

  7. Nicholas Rogoff says:

    Hello…is anyone out there. Please confirm either way. Is this great tool staying…going into production or ultimately going to die?

    9 months since the last update is pretty poor!

Comments are closed.

Skip to main content