SQL Azure Data Sync Service Update

SQL Azure Data Sync Service Update

  • Comments 5

Thanks for trying out our Preview version and sending us suggestions and feedback. We released a minor service update a few days ago based on the input we have received so far.

Some of the important changes in this update are:           

  • Log-ins with either username@server or just username are accepted.
  • Column names with spaces are now supported.
  • Columns with a NewSequentialID constraint are converted to NewID for SQL Azure databases in the sync group.
  • Administrators and non-Administrators alike are able to install the Data Sync Agent.
  • A new version of the Data Sync Agent is now available on the Download Center, but if you already have the Preview version of the Data Sync Agent it will continue to work.
Leave a Comment
  • Please add 4 and 2 and type the answer here:
  • Post
  • Really love the data synchronisation facility.  Couple of things I have noted which you may wish to think about as you work on the product.

    Make it clear prior to installation that the agent can reference and synchronise more than one database.

    I set up data sync against development area while I played.  When I wished to switch to a more representative database I could not give the agent a more appropriate name without deleting the agent and reinstalling.  The fact that one agent allows me to connect to a number of local databases wasn't clear when I installed the agent and I had used the first database name in agent name - hence the need to change agent name later.

    One on-premises agent should address each subscription.

    I have a development subscription and a live subscription yet it appears I should use the same installed agent to communicate with both subscriptions from my on-premises environment.  When databases have similar names on two different subscriptions then there is a significant opportunity for mistakes as I could be linking to live rather than development DBs or vice versa.  One agent for each subscription allowing access to only databases within that subscription which I can then name 'test' or 'live' may be better.

    Allow tables which fail to synchronise to be dropped from the synchronisation plan.

    If I select tables to synchronise that fail because of (for example) referential integrity rules then I cannot drop that table from synchronisation plan and I am forced to rework the sync topology.  I should be able to drop items that have failed to synchronise successfully so that I can fix them and then add them back in afterwards.

    Keep up the good work guys.

  • Thanks for the feedback Ed, we appreciate it and will try to address your issues in future service updates.

  • HI,

    is SQL Azure Data Sync Service available to test Databases in South East Asia Databases, As in Hub option provides only Europ and US options

  • Hi,

    When can we expect "Automatic cleanup of the metadta _tracking tables on a regular basis" feature become available to SQL Azure Data Data Sync Service? Any timelines? Thank you.

  • I tried to find in forum also. I was able to access my Azure database with credentials in management studio. The same servername, username(without @servername or with @servername), password connection failed at the time of  addding database to azure sync group.

Page 1 of 1 (5 items)