Replication Over Internet via FTP

What is the syntax for the snapshop location setup referring to the "Client
path to this folder from the FTP root"? When my pull connects, it doesn't
seem to issue any change directory commands and does not find the snapshot
files which are there.
The client path is the path from the FTP root directory, so if your snapshot
directory is called TRSnapshot and is in the ftp root directory, the path
would be \TRSnapshot\ftp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks, worked like a charm but my main issue turned out to be the space in
the order details table in the Northwind db. I am doing a proof of concept
with that DB and it tried to run that script first and bombed.
"Paul Ibison" wrote:

> The client path is the path from the FTP root directory, so if your snapshot
> directory is called TRSnapshot and is in the ftp root directory, the path
> would be \TRSnapshot\ftp
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Jeffrey,
this isn't such a large table - at what point does it fail?
Might be worth using the compression if you have a slow link?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication monitor error but no error?!

Hello again,
The root node of my SQL Server replication monitor is showing a red X but
all the actual replications listed underneath are OK. What might be causing
this and how can I get rid of it! My DBA is getting twitchy...
Thanks
Will
If you run profiler and navigate to the replication monitor, you should see
why this is happening. The replication monitor gets its info from
tempdb.dbo.MSreplication_agent_status and running
sp_MSload_replication_status refreshes this table. As restarting the SQL
Server Service causes the tempdb to be recreated from the model database,
this also removes the problem.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .