SQL2008R2 LAN Replication Subscription Real

10.129.186.37 this machine

10.129.186.95 Server

LAN environment

Replication type: Transactional replication

Note: The table to be copied must have a primary key, otherwise it is not optional to replicate the table.

Point 1, the LAN tries to save the snapshot folder in a shared way, I tried many times, unsuccessfully. And take the FTP way, one success.

Point 2, the Subscriber will automatically discover the FTP transfer mode.

Important 3,FTP Server, I use the IIS FTP program, simple and practical.

According to the requirements of the prompt to do so, there is no difficulty in the online a lot of information are misleading, do it on their own.

1, first of all to ensure that the FTP service can be accessed normally.

2, after the release point to publish the project point properties, look at the configuration of the FTP snapshot there, tick on the OK, there should be a hint.

3, after the success of the subscription, the two sides re-initialize a bit.

SQL does are quite automated, many do not need how to set up.

The Publisher will select a process in the following procedure.

Note: In the actual operation, I chose snapshot copy, at the Subscriber, see the relevant properties will have

The display cannot be connected, but when a table is randomly modified on the publication, subscribers will soon synchronize, so there is an estimate of the status of the problem, at least the sync status is problematic.

In the case of a wide area network for transactional replication, the extranet also needs to set the server name of the publisher with the IP mapping

SQL2008R2 LAN Replication Subscription Real