Re: Merge replication error
From: Hilary Cotter (hilaryk_at_att.net)
Date: 07/11/04
- Next message: Hilary Cotter: "Re: Hilary Cotter's repl cleanup script"
- Previous message: Hilary Cotter: "Re: Push vs Pull subscriptions"
- In reply to: DBard: "Re: Merge replication error"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 10 Jul 2004 21:51:52 -0400
but the network problem might exist only between this subscriber and
publisher.
I'd try to run a ping -t for a day and then look at the statistics to see if
a hicup occured.
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 I use to run this script:
osql -S hilary2kp -E -i c:\keepalive.sql -n
date /t
time /t
-- Hilary Cotter Looking for a book on SQL Server replication? http://www.nwsu.com/0974973602.html "DBard" <DBard@discussions.microsoft.com> wrote in message news:D10215EC-A700-4E92-8142-D567F8C50E34@microsoft.com... > Paul - Thanks for your response. > > The connectivity is fine - which is proven by 4 databases on this same server replicating just fine to the same subscriber. > > Another other ideas? > > - David > > "Paul Ibison" wrote: > > > Looks like a networking issue; when the error occurs, please try pinging the > > distributor from the subscriber, to test your network connectivity and name > > resolution. > > Regards, > > Paul Ibison > > > > > >
- Next message: Hilary Cotter: "Re: Hilary Cotter's repl cleanup script"
- Previous message: Hilary Cotter: "Re: Push vs Pull subscriptions"
- In reply to: DBard: "Re: Merge replication error"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|