Re: Transactional Replication Timeout Problems
From: Boze (andre.beauzec_at_hotmail.com)
Date: 02/19/04
- Next message: Anonymous: "Re: Article on replication for management"
- Previous message: zafer: "Re: SQL 2000 Replication Problem (18483) and IP addresses, computer names"
- In reply to: Simon: "Transactional Replication Timeout Problems"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 19 Feb 2004 14:05:59 +0200
Hi,
We were experiencing the exact same problem on a table of the same size. We
found that logging and increasing the timeout value provided no help. We
used profiler and discovered that once the distribution agent had completed
copying across all the rows in the table, it was then trying to update the
subscriber with all the transactions that had occurred since the snapshot
was taken. Our db's are extremely busy and there were just too many
transactions for it to ever catch up. We also noticed that indexes are not
properly created on the table on the subscriber until all the transactions
have caught up. This obviously does not help the catch up process.
The solution was simple. We stopped all the jobs that were updating the
table giving problems. Then we added the table as an article and then we ran
the snapshot. Following this process the table replicated without a problem
and the error, 'The process is running and is waiting for a response from a
backend connection', was gone.
"Simon" <x_3n@hotmail.com> wrote in message
news:BBA7FD73-3BE0-4B3E-91AC-7DAB0F44A7B7@microsoft.com...
> I have a large table (approx 43million rows) which I need to replicate.
The problem I am getting is that after going through the replication process
(Setup Publication>Snapshot>Bulk Copy) the distribution agent then just sits
there with the message 'The process is running and is waiting for a response
from a backend connection'.
>
> I have tried to rectify this by increasing the Query Timeout in the agent
profile to 3600000 so if there is ever going to be a response I will still
be waiting for it. So far the agent has been waiting for the response for
3hrs 30mins.
>
> Could anyone shed any light on this message or come up with a solution for
replicating the table (it has to be transactional replication with the
minimum amount of latency for reporting purposes) ?
- Next message: Anonymous: "Re: Article on replication for management"
- Previous message: zafer: "Re: SQL 2000 Replication Problem (18483) and IP addresses, computer names"
- In reply to: Simon: "Transactional Replication Timeout Problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
