Merge Replication without network connectivity.

Hi All,
Firstly an apology in advance if this question gets asked 15 times a week -
I'm not normally involved in SQL Server development and a quick scan of the
newsgroup didn't show anything...
Here's the scenario. We will have an application running in a central office
that uses SQL Server. This application will also be distributed to a large
number of remote sites - each with their own copy of the application and
database (possibly MSDE). At irregular intervals they will be asked to
synchronise their data with head office, however there is no network
connectivity AT ALL between these sites (they are really, really remote)
meaning the only way of shipping the changes is via some physial media. At
equally irregular intervals, the head office will ship out the latest copy
of their data which will be merged back to each offices database.
Is this scenario (or anything resembling it) possible using the built-in
features of SQL Server, or should I begin the not-so-fun task of developing
my own solution?
Thanks in Advance,
mr
There is no built in capability. In the intro to SQL Server 2000 Bible Paul
Nielsen mentions someone doing this via email - which you need network
connectivity for.
The name he mentions is Dave Catherman. I can't find any references to him
on the net.
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
"Mark Richards" <m@.mr.com> wrote in message
news:OdvUwTaGFHA.624@.TK2MSFTNGP15.phx.gbl...
> Hi All,
> Firstly an apology in advance if this question gets asked 15 times a
week -
> I'm not normally involved in SQL Server development and a quick scan of
the
> newsgroup didn't show anything...
> Here's the scenario. We will have an application running in a central
office
> that uses SQL Server. This application will also be distributed to a large
> number of remote sites - each with their own copy of the application and
> database (possibly MSDE). At irregular intervals they will be asked to
> synchronise their data with head office, however there is no network
> connectivity AT ALL between these sites (they are really, really remote)
> meaning the only way of shipping the changes is via some physial media. At
> equally irregular intervals, the head office will ship out the latest copy
> of their data which will be merged back to each offices database.
> Is this scenario (or anything resembling it) possible using the built-in
> features of SQL Server, or should I begin the not-so-fun task of
developing
> my own solution?
> Thanks in Advance,
> mr
>
|||Oh well.
Thanks Hilary.
MR
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:e4H8IdbGFHA.1932@.TK2MSFTNGP14.phx.gbl...
> There is no built in capability. In the intro to SQL Server 2000 Bible
> Paul
> Nielsen mentions someone doing this via email - which you need network
> connectivity for.
> The name he mentions is Dave Catherman. I can't find any references to him
> on the net.
> --
> 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
> "Mark Richards" <m@.mr.com> wrote in message
> news:OdvUwTaGFHA.624@.TK2MSFTNGP15.phx.gbl...
> week -
> the
> office
> developing
>

Merge replication very very slow

You could enable logging as per this article:
http://support.microsoft.com/?id=312292 in order to try
to get more info.
To troubleshoot connectivity issues:
(a) run a ping -t for a day and then look at the
statistics to see if a hicup occured.
(b) You could run this keep alive script which will tell
you exactly when you get a failure. Save this as
c:\keepalive.sql
WHILE 1<>2
BEGIN
SELECT GETDATE()
WAITFOR DELAY '00:00:01'
END
GO
Here is the batch file that Hilary posted up a while back
to run this script:
osql -S hilary2kp -E -i c:\keepalive.sql -n
date /t
time /t
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
I'm not convinced that this is a network error. I think it could be that the
merge agent is busy processing the articles and has not completed within the
inactivity threshold and the error has resolved as a general network error.
Logging will help you to determine exactly what the problem is, but you
should bump up the QueryTimeout values and the inactivity threshold levels
in hopes that the added time interval your merge agent has to work with will
allow it to successfully complete.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:1d1201c4d7b9$9a29f8a0$a501280a@.phx.gbl...
> You could enable logging as per this article:
> http://support.microsoft.com/?id=312292 in order to try
> to get more info.
> To troubleshoot connectivity issues:
> (a) run a ping -t for a day and then look at the
> statistics to see if a hicup occured.
> (b) You could run this keep alive script which will tell
> you exactly when you get a failure. Save this as
> c:\keepalive.sql
>
> WHILE 1<>2
> BEGIN
> SELECT GETDATE()
> WAITFOR DELAY '00:00:01'
> END
> GO
> Here is the batch file that Hilary posted up a while back
> to run this script:
> osql -S hilary2kp -E -i c:\keepalive.sql -n
> date /t
> time /t
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>