SQL Data Sync

Azure SQL Data Sync (Preview) is a service that enables you to synchronize the data you select across multiple SQL Server and SQL Database instances. To synchronize your data you create sync groups which define the databases, tables and columns to synchronize as well as the synchronization schedule. Each sync group must have at least one SQL Database instance which serves as the sync group hub in a hub-and-spoke topology.

If you have any feedback on Azure SQL Data Sync service, we’d love to hear it.

  1. Add support for circular foreign key dependencies

    Curently if the database contains circular foreign key dependencies the Azure Data Sync will not deploy the sync group reporting the error:
    Cannot deploy the sync group because there is a circular foreign key dependency

    323 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Automatic propagation of schema changes to one database to all databases in a sync group

    In addition to allowing Sync Group configuration to be updated to cater for schema changes, automatically propagate the schema changes to all databases in a Sync Group.

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    We are more focused around data synchronization than schema synchronization at the moment. We may revisit the priority of this in the future.

  3. Support for tables for which primary key is different than Clustered index

    In a lot of situations the Clustered index differs from the primary key in a table. At this moment, Data Sync supports only tables for which the clustered index is the primary key. It would be nice if this restriction is not needed. This will make live much easier to sync data between on-premise and SQL Azure db. We can't change current datamodel in our application. Current datamodel is made based on performance.

    107 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thanks for the suggestion! We are evaluating the priority and cost for implementing this.

  4. Support files and Windows Azure Blobs

    Add synchronization capabilities for the Windows Azure Blob Service. Allow data to be synchronized between storage accounts and allow on-premises file data to be synchronized with the Blob Service.

    103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    This is a very interesting idea! We would like to know what specific usage you have in mind – for example, are you continuously generating operational logs on-prem and would like an utility to easily upload these files into blob storage for further analysis, maybe using HDInsight? Please post your comments!

  5. Allow continuous synchronisation or intervals less than 5 minutes

    Current smallest interval is 5 minutes, allow me to set this to between 1 and 4 minutes or a continuous synchronisation option. A wait of up to 5 minutes for sync is not always acceptable.

    97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Mail notification

    support team should get mail notification on failure with required action to be taken to resolve it

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support compression

    Most of the data being passed as datasets is highly compressible. We have created methods to compress/decompress the data when batched, but it would be nice to support this option out of the box to minimize the amount of data being sent over the wire.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thanks for the suggestion! We are evaluating the priority and cost for implementing this.

  9. don't touch/modify my schemas

    I don't want the data sync or anything else for that matter to "touch" any of my databases.

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thank you for your suggestion! We would like to know what your concern is around schema modification – is it because you don’t always get granted schema modification rights? Are you concerned about administration/maintenance overhead of additional objects? Or are you concerned about additional overhead it places on the database?

  10. Enable SQL Azure Data Sync Agent to support / connect to multiple Subscriptions

    Currently the SQL Azure Data Sync Agent can only connect to one subscription so if you are supporting multiple clients your local server can't participate in multiple sync topologies. The abilty to connect to multiple subscriptions would enable all my client databases to be synced to one management server.

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide ability to replicate to Azure non-Azure SQL Server

    Allow data to be transactionally replicated to the cloud, with an alternative way (SFTP?) to provide snapshot initialization data.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    In addition to on-pre SQL Server, are folks interested in sync’ing SQL Azure to SQL Server in Azure VM or AWS? Or other non-Azure properties?

  12. Support syncing federated tables.

    When voting for this feature we would appreciate it if you enter a comment with the specific support you require; e.g. sync on-premises SQL Server with a federated database; sync between federated databases; sync reference data between partitions; etc.

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Given that most Windows Azure SQL Database customers are now advised to use with custom sharding pattern for scale-out, we are re-evaluating when you would want to use sync for a sharded environment – is it syncing from on-prem SQL Server to multiple shards in the cloud, synchronizing between the shards in the cloud, or syncing from multiple shards down to on-prem SQL Server? We’d appreciate your input on this.

  13. Support Windows Azure Tables

    Add synchronization capabilities for the Windows Azure Table Service. Allow data to be synchronized between storage accounts and allow on-premises data to be synchronized with the Table Service (from which on-premises stores?).

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thanks for the suggestion! We are evaluating the priority and cost for implementing this.

  14. Support Schema

    Support tables with same table name but under different scheams in one database.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Filtering support for master and detail tables

    Allow master and detail relationship to be specified so a filter and the filter value only needs to be present on the master table.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thanks for the suggestions. We will evaluate its relative priority as we decide how to move the overall Data Sync story forward.

  16. Support all data types like money, bigint and varbinary.

    I can't use SQL Data Sync because it doesn't support all data types yet.
    If MS Azure team starts to support other data types, I'll use the SQL Data Sync service.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    Thank you for your feedback! We will consider this request as we priority our feature backlog.

  17. SQL Data Sync API to manually trigger a sync

    We need a way to force a sync. With the minimum sync window of 5 mins we cannot guarantee prevention of data contention. For example, in a bookings system, the on premises database is always 5 mins out from potential web updates. Maintenance users want to add exclusions or blocks and need to know no new bookings were made in those slots. Likewise, if the on premises database makes entries, it needs to force those entries immediately to the web and not wait for the Sync. We see this as an important architectural requirement to an otherwise impressive service.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Off line Sync feature

    Feature to sync between two database, once they are connected to net or by moving some files to other machine and sync with othere database

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Shirley Wang responded

    This is an interesting idea – allowing source to turn on change tracking, but not requiring the sync group to be persisted but rather the sync relationship established dynamically.

  19. Support for different on-premises databases

    On-premises SQL Server databases can currently be included in a Sync Group. Would you like support for other databases; if so, which ones?

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Provide more meaningful error message

    To be helpful on problem investigation.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

SQL Data Sync

Feedback and Knowledge Base