{"id":3855,"date":"2017-05-15T00:00:00","date_gmt":"2017-05-15T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/migrating-to-azure-data-sync-2-0"},"modified":"2025-06-19T08:21:00","modified_gmt":"2025-06-19T15:21:00","slug":"migrating-to-azure-data-sync-2-0","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/migrating-to-azure-data-sync-2-0\/","title":{"rendered":"Migrating to Azure SQL Data Sync 2.0"},"content":{"rendered":"\n

We’ve made improvements to SQL Data Sync including PowerShell programmability, better security and resilience, enhanced monitoring and troubleshooting, and availability in more regions. As part of these changes, SQL Data Sync will only be available in the Azure portal beginning July 1, 2017. This blog post will cover the steps current active users will use to migrate to the new service. This only applies to customers that have used their Sync Groups after March 1, 2017.<\/p>\n\n\n\n

For details on the improvements, please see our Data Sync Update<\/a> blog post. If you are a new user that would like to try Data Sync, look at this blog post on Getting Started with Data Sync.<\/p>\n\n\n\n

Overview<\/h2>\n\n\n\n

Starting June 1, 2017, existing Sync Groups will begin migrating<\/strong>. Existing Sync Groups will continue to work until the migration is completed. Please see the section below that fits your case for details.<\/p>\n\n\n\n

A Sync Database will be created for each region where you have a Sync Group to store metadata and logs.<\/strong> You will own this database. This will be created in the same server as your Hub Database.<\/p>\n\n\n\n

On June 15, 2017, Data Sync will be available to all customers in the new Azure portal. <\/strong>If you would like early access please email us<\/a> with your subscription ID.<\/p>\n\n\n\n

On July 1, 2017, SQL Data Sync will be retired from the Azure classic portal.<\/strong> After July 1, 2017, the original service will continue to run, but you won\u2019t be able to make any changes or have portal access until you complete your migration.<\/p>\n\n\n\n

On September 1, 2017, the original SQL Data Sync service will be retired.<\/strong> If you haven\u2019t migrated your sync groups by September 1, 2017, your Sync Group will be deleted.<\/p>\n\n\n\n

What you need to do<\/h2>\n\n\n\n
    \n
  1. Plan and prepare for your migration.<\/strong> You will receive emails in the coming weeks with your migration date and instructions.<\/li>\n\n\n\n
  2. Do not make topologies in the old portal after your migration date.<\/strong> This date will be sent to the subscription email of each Sync Group being migrated.<\/li>\n\n\n\n
  3. If you have any on-premises member databases install and configure the local agent.<\/strong> You need one on each machine or VM hosting a member database. Detailed steps are included below.<\/li>\n\n\n\n
  4. Test for successful migration. <\/strong>Do this by clicking \u201cSync Now\u201d in the Azure SQL Data Sync portal.<\/li>\n\n\n\n
  5. After verifying migration, disable scheduled sync in the old service.<\/strong> You must do this before making any topology changes or this could cause errors with Data Sync. Do not drop your sync groups in the old service.<\/li>\n<\/ol>\n\n\n\n

    After completing these steps you can use Data Sync in the new portal.<\/p>\n\n\n\n

    Installing and configuring local agent<\/h3>\n\n\n\n

    Your local agent from the original service can remain running and installed while you do the following steps. You can download the local agent<\/a>. <\/p>\n\n\n\n

    You will need to:
    1. Download and install the local agent.<\/strong> This local agent is specific to Data Sync 2.0. This agent and the old one are not interchangeable. Install the local agent in the default location on every machine which hosts a member database. <\/p>\n\n\n\n

    \"Download<\/figure>\n\n\n\n
    \"Download<\/figure>\n\n\n\n

    2. Get the agent key.<\/strong> You can find this in the new Azure SQL Data Sync portal after your migration date. To do this select the Sync Agent under the \u201cSync to other databases\u201d tab for the Hub database. This will launch a blade that will allow you to generate a key. Note that this key needs to be from the new Azure portal.<\/p>\n\n\n\n

    \"Sync<\/figure>\n\n\n\n
    \"Sync<\/figure>\n\n\n\n

    3. Click the “Submit Agent Key” button and connect to the Sync Group and Sync Database.<\/strong> You’ll need to enter credentials for your Sync Database. This is the same as your credentials for the server on which the Sync Database is located.<\/p>\n\n\n\n

    \"Sync<\/figure>\n\n\n\n

    4. Update your credentials. <\/strong><\/p>\n\n\n\n

    \n

    a. Click the edit credentials button and update the information. Use this method if you only have a few on premises databases.<\/p>\n<\/blockquote>\n\n\n\n

    \"SQL<\/figure>\n\n\n\n

    Alternate method:<\/strong> If you have a lot of on-premise members or do not have the credentials do the following:<\/p>\n\n\n\n

    1. Follow step 1 as shown above.<\/p>\n\n\n\n

    2. Follow step 2 as shown above.<\/p>\n\n\n\n

    3. Copy the configuration file from the original service.<\/p>\n\n\n\n

    \n

    a. Copy the \u201cAgentConfigData.xml\u201d<\/strong> from the original service. The path will be as follows: Microsoft SQL Data SyncdataAgentConfigData.xml<\/strong><\/p>\n\n\n\n

    b. Put the copy of that file in the new Data Sync folder. Please rename the file AgentConfigData_Old to avoid confusion and potential issues with the old service. The path will be as follows: Microsoft SQL Data Sync 2.0dataAgentConfigData_Old.xml<\/strong><\/p>\n<\/blockquote>\n\n\n\n

    4. Follow step 3 as shown above.<\/p>\n\n\n\n

    Related links<\/h2>\n\n\n\n