1433 open. Are you saying that tranactional replication would not be
practical? Dataflow would only go from Publisher to web subscriber. Two
"Hilary Cotter" wrote:
> It is unlikely your ISP will open port 1433 for inbound communication, so it
> will be difficult to get this running unless they open a port for you and
> you can configure your SQL Server to run on this port.
>
> As ftp is probably open to you, you might be able to bcp the data out to an
> ftp site, and have the remote SQL Server bcp the data into staging tables
> and then only push the delta's into the live tables. With tracking you can
> keep the data flow to a minimum.
> --
> Hilary Cotter
>
> Looking for a SQL Server replication book?
>
http://www.nwsu.com/0974973602.html >
> Looking for a FAQ on Indexing Services/SQL FTS
>
http://www.indexserverfaq.com >
>
>
> "EdwardH" <EdwardH@discussions.microsoft.com> wrote in message
> news:B19177EC-3E93-4076-8D01-34EB36750585@microsoft.com...
> >I have SQL 2000 tables (5) that I want to replicate to SQL 2005 Workgroup
> >on
> > Remote web Server which need to synchronise else say twice a day but
> > without
> > taking Remote off-line. How can I achieve this?
>
>