SQL azure (10) SQL azure Data sync data synchronization function (I)

First, let's take a simple example: if a large production enterprise contains two subsystems:

-There is a product production system deployed inside the Enterprise. Employees (production employees) working inside the enterprise can access the system through the Intranet. The background database is SQL Server 2008 R2 in the LAN.

-Another product inventory system is run on the Windows azure platform. Employees outside the company, such as sales personnel, can quickly access the company through mobile phones and tablets to view inventory conditions for timely sales activities. The background database uses Microsoft SQL azure cloud database.

Then there will be a problem: how can we maintain consistency between the SQL Server database and the SQL azure cloud database to facilitate the work of production personnel and sales personnel in collaboration?

SQL azure Data sync can achieve this function. Its core is the sync framwork technology, which can synchronize "cloud database-cloud Database" and "cloud database-local database (cloud to local.

-To implement the cloud to cloud function, you must create two different SQL azure databases.

-To implement cloud to local, you must create an SQL azure dB and use SQL Server dB locally.

Data sync uses a concept called "Hub Database". Through integration of hub databases, data sync enables different databases (on premise dB and on cloud dB) the synchronization can be smoother. This Hub database is located in Microsoft's data center.

Some netizens may ask: why do we need to use the hub database? In fact, this hub database plays an arbitration role. Let's take the previous factory production example as an example: if the inventory of the product is 0 due to power failure in the factory, the sales staff will not be able to sell the product normally. When the power supply is restored, a new batch of products are produced on the pipeline, with a total of 1000 products. In the local SQL Server 2008 R2, employees change the inventory quantity to 1000; but this is the SQL azure inventory status is 0 (yes, because no one has to modify it ). At this time, the hub database runs automatically in the background and queries the local dB and cloud dB respectively, and finds that the inventory status values are different. According to the policy (customizable) of the hub database, we can set the local database as the standard. At this time, the hub dB writes the value 1000 to the value corresponding to the same table in the cloud dB. In this way, the local dB and hub dB are synchronized.

Obviously, SQL azure Data sync provides you and your enterprise with many benefits:

• No need to writeCodeYou can create various complex synchronization tasks.
  • Microsoft SQL azure Data sync supports synchronization groups for multiple databases in one data center or geographically dispersed data center. Each synchronization group can be customized based on your business needs to reduce costs.
• You can use the Microsoft Windows azure platform and Microsoft SQL azure without creating and managing your own cloud.
  • Microsoft handles all infrastructure, security, and scaling issues, allowing you to focus on business management.