SQL Server master-slave database synchronization using a publish subscription is an implementation

The Publish subscription feature has been available since SQL 2005

The configuration method can be consulted: http://blog.csdn.net/wanmdb/article/details/7515277

Problems encountered:

1.

If the agent fails to start, perform the configuration

2.

SQL server2008 copy error due to operating system error 3, the process could not read the file "D:\Program files (x86) \sql Server\repldata\March 04, 2014 ⁄sql server⁄ A total of 625 characters ⁄ font size small big ⁄ no comments ⁄ read 1,378 views

SQL server2008 with copy to do hot spare time error, error message is as follows:

The command to try:
D:\Program Files (x86) \sql Server\repldata\unc\win-k0sv1q3fakr_refbook_1_refbook_1\20140304150003\slorimdportdata _35.pre
(Transaction serial number: 0x000031f7000001a5008c00000000, command id:38)

Error message:
Unc\win-k0sv1q3fakr_refbook_1_refbook_1\20140304150003\slorimdportdata_35.pre ". (Source: MSSQL_REPL, Error number: mssql_repl20024)
Get help: http://help/MSSQL_REPL20024
The system could not find the path specified.

Tangled up half a day, very egg pain solved the problem, the idea is such.

It is possible that the account of SQL Server cannot read the snapshot files of the publisher remotely, because it is a privilege to see the error visually. Then follow this line of thought, let the subscriber have permission to read the snapshot file of the publisher.

Assign the snapshot file of the Publisher to the Subscriber:

My publisher is 192.168.1.2 Subscriber is 192.168.1.3

Share folders on 192.168.1.3 d:\sql server

To set snapshot properties at the Publisher:

At the Subscriber:

OK, run the copy task again, the permissions problem is solved perfectly, share the time must pay attention to permissions, to the Publisher all permissions.

SQL Server master-slave database synchronization using a publish subscription is an implementation