Implementation Features: The master server maintains data changes and synchronizes the data from the master server when the server needs it.
configuration: the master and slave servers are SQL Server R2.
Implementation method:
Prepare:
1. Master and slave servers need to establish the same account name and password account (at that time I think it is a permissions issue, as long as the permissions to set up the folder, but later found that it seems not so, from the server to synchronize the time needed to call the primary server SQL Agent service, so need to use their user account and password) , you do not need administrator privileges to change the SQL Server Agent service users on the master and slave servers to the new user.
2. Create a shared folder on the primary server to make sure that the user you just created is able to read.
Primary server:
1. Open SQL Server and SQL Server Agent service.
2. Create a new publication, follow the bootstrap (select Snapshot publication).
3. Until you need to fill in the account information, here I chose the Administrator account and Dbowner database account, the other prompts generally no problem.
From the server:
1. Create a new subscription at "Local subscription" and select "Pull subscription" until the user information is filled in.
2. After the creation, right click to view the synchronization status, pop-up box, select Start.
This completes the database synchronization.
About the SQL SERVER R2 Publishing subscription feature