October 4, 2007 at 10:51 am
Hi
we have a transactional Replication between two 2K5 SQL Servers in our production with about 1-4 Mio I/O's per Day.
The Data from the OLTP DB is replicated in our DWH.
Everything worked fine till now. Since yesterday i keep getting this Error Message:
Replication-Replication Distribution Subsystem: agent %S% scheduled for retry. Query timeout expired.
Does anybody have seen this before??
... and Yes, I raised the timeout.
THX
October 5, 2007 at 11:45 am
When there are an excesive amount of lock or contention in the distribution database you get those time-outs. Are people deleting/inserting massive amount of rows in a single transaction ? That can be the cause of your problems.
* Noel
October 8, 2007 at 12:36 am
Hi,
Thanks for your reply. I just figured it out. It was like u said.
I foud an insert / update job wich was running for 6 (!!!!) hours.
I dont know where it came from and who did this evil thing but i killed it and now its running perfectly again.
THX
October 9, 2007 at 2:53 pm
Glad to know you solve the problem
* Noel
October 24, 2010 at 12:42 am
Hi,
As a clean up we deleted around 50 milliion records from a table and the changes are showing up in the two subscriptions. However I am getting query timeout expired for the some other subscriptions for different tables.
It raises the message initializing, Process is running and waiting for a response from the server and Query Timeout expired.
We have SQL2k5 to SQL2k5 Trans Replications through a remote dist running sql2k5. I would truly appreciate your thoughts...
Thanks,
Ram
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply