MSSQL transactional replication failure timeout / general network error

Hi all,
I was hoping someone can assist me in a problem that has been going on
for some time.
We have been experiencing replication problems for a while, when
replicating data (1 table of approx 150,000 records, 1 of 75,000) to
our SQL server on our website.
We have noticed a lot of general network errors, and although it often
sorts itself out, it sometimes fails and needs to be started by hand.
The data changes in batches every hour and sometimes 5% of the records
may be replaced.
This has recently got worst, to the point that SQL server is now
refusing to connect to our web database when I delete and re-push the
replication job. It simply waits for quite a while and then times
out. If I try and replicate a small table from the same publisher to
the same subscriber it works fine.
Does anyone have any ideas?
By the way
Using SQL server 2K, transactional replication over a 2Mb leased line.
Many thanks
Chris
enable replication logging to see where it is failing.
Follow the instructions here on how to enable logging.
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Chris Bartington" <chris.bartington@.orange.net> wrote in message
news:175eba94.0411231017.76ce38d3@.posting.google.c om...
> Hi all,
> I was hoping someone can assist me in a problem that has been going on
> for some time.
> We have been experiencing replication problems for a while, when
> replicating data (1 table of approx 150,000 records, 1 of 75,000) to
> our SQL server on our website.
> We have noticed a lot of general network errors, and although it often
> sorts itself out, it sometimes fails and needs to be started by hand.
> The data changes in batches every hour and sometimes 5% of the records
> may be replaced.
> This has recently got worst, to the point that SQL server is now
> refusing to connect to our web database when I delete and re-push the
> replication job. It simply waits for quite a while and then times
> out. If I try and replicate a small table from the same publisher to
> the same subscriber it works fine.
> Does anyone have any ideas?
> By the way
> Using SQL server 2K, transactional replication over a 2Mb leased line.
> Many thanks
> Chris