Merge replication - Check network document
From: Paul Ibison (Paul.Ibison_at_Pygmalion.Com)
Date: 07/24/04
- Previous message: Paul Ibison: "one distributor can act both for transactional and merge replicati"
- In reply to: Nathan: "Merge replication - Check network document"
- Next in thread: Hilary Cotter: "Re: Merge replication - Check network document"
- Reply: Hilary Cotter: "Re: Merge replication - Check network document"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 24 Jul 2004 09:53:49 -0700
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
- Previous message: Paul Ibison: "one distributor can act both for transactional and merge replicati"
- In reply to: Nathan: "Merge replication - Check network document"
- Next in thread: Hilary Cotter: "Re: Merge replication - Check network document"
- Reply: Hilary Cotter: "Re: Merge replication - Check network document"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|