We’ve made improvements to SQL Information Sync including PowerShell programmability, meliorate security and resilience, enhanced monitoring and troubleshooting, and availability in more than regions. Equally part of these changes, SQL Data Sync will only exist bachelor in the Azure portal beginning July 1, 2017. This blog postal service will cover the steps electric current active users will use to migrate to the new service. This only applies to customers that have used their Sync Groups later March one, 2017.
For details on the improvements, please see our Data Sync Update weblog mail service. If you are a new user that would like to try Data Sync, await at this blog post on Getting Started with Information Sync.
Starting June ane, 2017, existing Sync Groups will begin migrating. Existing Sync Groups will proceed to work until the migration is completed. Please come across the section below that fits your case for details.
A Sync Database will be created for each region where yous have a Sync Group to store metadata and logs.
Yous will own this database. This will be created in the same server as your Hub Database.
On June 15, 2017, Information Sync will be available to all customers in the new Azure portal.
If you would like early access please email united states with your subscription ID.
On July 1, 2017, SQL Data Sync will be retired from the Azure classic portal.
After July i, 2017, the original service volition continue to run, merely you won’t be able to brand any changes or have portal access until you complete your migration.
On September 1, 2017, the original SQL Data Sync service will exist retired.
If y’all haven’t migrated your sync groups by September 1, 2017, your Sync Group will be deleted.
What y’all demand to do
Plan and prepare for your migration.
You will receive emails in the coming weeks with your migration date and instructions.
Practise non make topologies in the onetime portal afterwards your migration date.
This engagement will be sent to the subscription email of each Sync Group being migrated.
If you lot have any on-premises member databases install and configure the local agent.
Y’all need one on each machine or VM hosting a member database. Detailed steps are included below.
Test for successful migration.
Do this past clicking “Sync Now” in the Azure SQL Data Sync portal.
After verifying migration, disable scheduled sync in the old service.
You must practice this before making any topology changes or this could crusade errors with Information Sync. Do not drop your sync groups in the quondam service.
Afterwards completing these steps you tin can utilize Data Sync in the new portal.
Installing and configuring local agent
Your local agent from the original service can remain running and installed while you exercise the following steps. You tin download the local agent.
You will need to:
Download and install the local agent.
This local amanuensis is specific to Data Sync two.0. This agent and the sometime one are not interchangeable. Install the local amanuensis in the default location on every auto which hosts a member database.
Get the amanuensis cardinal.
You tin find this in the new Azure SQL Data Sync portal after your migration date. To do this select the Sync Amanuensis under the “Sync to other databases” tab for the Hub database. This volition launch a blade that volition allow you to generate a central. Note that this key needs to exist from the new Azure portal.
Click the “Submit Agent Fundamental” button and connect to the Sync Grouping and Sync Database.
You’ll need to enter credentials for your Sync Database. This is the aforementioned as your credentials for the server on which the Sync Database is located.
Update your credentials.
a. Click the edit credentials push button and update the information. Utilize this method if you only have a few on premises databases.
If y’all have a lot of on-premise members or practice non have the credentials do the following:
1. Follow step i equally shown above.
2. Follow step 2 as shown in a higher place.
3. Copy the configuration file from the original service.
a. Copy the
from the original service. The path will be as follows:
Microsoft SQL Data Sync\data\AgentConfigData.xml
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 erstwhile service. The path will be as follows:
Microsoft SQL Data Sync 2.0\data\AgentConfigData_Old.xml
four. Follow step 3 every bit shown above.
- Getting Started with Information Sync
- Data Sync Refresh Blog
- Download the Local Agent
If you take any feedback on Azure SQL Data Sync service, we’d dearest to hear from you lot! To go the latest update of Azure SQL Data Sync, please join the SQL Advisor Yammer Grouping or follow the states @AzureSQLDB on Twitter.