Using SQL Azure Data Sync Service to provide Geo-Replication of SQL Azure databases

Sign in to queue

Description

In this second of a 3 part webcast series, I introduce you to the Data Sync Service for SQL Azure.  This service extends on the SQL Azure Data Sync tools’ ability to provide symmetry between SQL Server and SQL Azure where data changes at either location are bi-directionally synchronized between on-premises and the cloud.  With SQL Azure Data Sync Service, we have extended that capability to allow you to easily geo-distribute that data to one or more SQL Azure data centers around the world.  Now, no matter where you make changes to your data, it will be seamlessly synchronized to all of your databases whether that be on-premises or in any of the SQL Azure data centers.  To learn more and register for access to SQL Azure Data Sync Service please visit: http://sqlazurelabs.com/.

Embed

Download

Download this episode

The Discussion

  • User profile image
    Bas Soons

    Nice video, thanks! But what about conflict management. What if someone in europe changes the same customer as in the US? How do you handle this?
    Can you also synchronize to mobile devices? And what about filtering? For example: I only want to send VIP customers to europe. Is this possible?
    Thanks,
    Bas

  • User profile image
    LiamCavanagh

    Yes, SQL Azure Data Sync does support conflict handling and automatically resolves any conflicts for you.  As for filtering the only level of filtering currently available is at a table level (meaning you can choose to sync only specific tables).  Over time we will add more filtering down to the level of rows and columns.

    Liam

  • User profile image
    ehuna

    Liam, awesome demo, thanks!

    >Yes, SQL Azure Data Sync does support conflict handling and automatically resolves any conflicts for you

    Do you have the rules on how conflicts are handled listed anywhere?  Here's an example -

    - Suppose three databases in a sync group: NorthCentral US (HUB), Europe (Member), and Southeast Asia (Member).

    Here are some scenarios -

    - Update record in Asia, Update same record/same field in Europe, sync, check records in asia, europe, us - last change (Europe) should win?
    - Delete record US, update same record in Europe, sync, check records in asia, europe, us - the deletion should win? Even if it happened before the update in Europe?
    - Add field to table in US, sync, check schema changes are made in Asia, Europe - are schema changes sync'ed?
    - Add table to US, sync, check schema changes are made in Asia, Europe - same question on schema changes.

    Emmanuel

Add Your 2 Cents