Re: Merge replication - Check network document
From: Hilary Cotter (hilaryk_at_att.net)
Date: 07/25/04
- Next message: Hilary Cotter: "Re: Replication Failure with Event ID 203"
- Previous message: Hilary Cotter: "Re: replicate 1 column to 2 columns(easy one for the gurus)"
- In reply to: Paul Ibison: "Merge replication - Check network document"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 25 Jul 2004 08:32:40 -0400
<quibble>
The keep alive script Paul mentions should be run on the Subscriber against
the Publisher as an osql script. When the script fails it will give you the
exact time of day when the script fails.
Here is a typical batch file I use. Replace hilary2kp with the name of your
publisher. Run this script on the Subcsriber. keepalive.sql is the name of
the file I store the tsql commands in Paul mentions.
osql -S hilary2kp -E -i c:\keepalive.sql -n
date /t
time /t
</quibble>
-- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message news:343201c4719e$caf63100$a601280a@phx.gbl... > Nathan, > to verify that there is a network issue, you can run a > ping -t for a day and then look at the statistics to see > if a hicup occured. > > You could run a tsql script: > > WHILE 1<>2 > BEGIN > SELECT GETDATE() > WAITFOR DELAY '00:00:01' > END > GO > > As it looks like a network issue, in this case I'd set the > step 3 to go to step 1 on the merge agent's job, > effectively automatically restarting the job on a network > error, which fixes the problem almost all the time. > > HTH, > Paul Ibison >
- Next message: Hilary Cotter: "Re: Replication Failure with Event ID 203"
- Previous message: Hilary Cotter: "Re: replicate 1 column to 2 columns(easy one for the gurus)"
- In reply to: Paul Ibison: "Merge replication - Check network document"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
