Delivering snapshots through FTP and Web Synchronizing the merge publication

For network replication, the Default Snapshot Folder name must be shared, so UNC pathname can be used. SNAPSHOTS will be accessed by UNC path.

Snapshots can be delivered through FTP protocol.

Work at DC:Server computer
Install the FTP service;
FTP site configuration;




Local Distributor:

VIP\Agent is a member of db_owner role of AdventureWorks and distribution databases.

Publisher Properties:
Default Snapshot Folder--\\SERVER\ftproot\snapshots

Creating a publication --AdventureWorks:Document

PAL: VIP\Agent

As shown above, \snapshots\ftp must be specified. When a publication is created, the snapshot files will be automatically put --\\SERVER\ftproot\snapshots\ftp folder.

It is better to specify a login for FTP access.

"Put files in the following folder" -- if specified, a copy of snapshot files will be put under the folder. If the snapshot is compressed or the PUBLISHER is running Microsoft SQL Server 2000, you must specify the property.

After FTP publishing is configured, when subscription is created by the New Subscription Wizard, the Subscriber will use the FTP method to retrieve snapshot files.

Work at Member:KingPC computer
Subscription database: Kdata
USE MASTER
CREATE LOGIN [VIP\Agent] FROM WINDOWS
GO
USE Kdata
CREATE USER [VIP\Agent] FOR LOGIN [VIP\Agent]
GO
EXEC sp_addrolemember N'db_owner', N'VIP\Agent'
GO
Creating a pull subscription
The DOCUMENT table will be created.

Distribution Agent retrieves the snapshot files through FTP.

Drawback using FTP

FTP passwords is sent from the Subscriber to the FTP server in plain text. A single account controls access to the snapshot share.

Filtered merge publication has difficult to be implemented.

===============