This article is for anyone who is planning to use SQL Data Sync, especially those who are in the planning and design phase. Topics covered include selecting a location for your SQL Database, ensuring that when you create your SQL Database it is large enough
to work with your data and SQL Data Sync, selecting which tables to include in a particular synchronization group, and more.
SQL Data Sync service enables bi-directional synchronization of data between two or more geographically distributed SQL Database and SQL Server databases.
The SQL Databases may exist in any of the Windows Azure data centers around the world.
The SQL Server databases may also be geographically distributed.
You must have at least one SQL Database that SQL Data Sync uses as the
hub for synchronizations.
As data passes into and out of a data center there may also be ingress and egress charges.
If you schedule your sync group to sync every five minutes, T0, T0+5, T0+10 ..., but it takes the group six minutes to complete a synchronization then your synchronizations take place at T0, T0+10, T0+20 and so on. T0+5 and T0+15 fail because synchronizations
T0 and T0+10 haven't completed.
There are three steps to provisioning your target database.
Figure 1 - Introduction Screen
Figure 2 - Choose Objects
Figure 3 - Set Scripting Options
Figure 4 - Script for Database engine type Figure 5 - Types of data to script
Figure 6 - Summary Page
Figure 7 - Save or Publish Scripts