October 1, 2007 at 3:04 pm
The replication job I have set up is fail every Sunday morning. I suspecting the the Optimization job we have that runs for 5-6 hours to be the problems.
Anyone else run into this problem.
Error:
"the process could not execute 'sp_ReplCmds' on ....."
October 1, 2007 at 3:23 pm
this is a common thing because those jobs that generate a lot of transaction log records create a big contention for replication stored procedures. You could stop the Log reader before those jobs run and -restart it after those jobs are done.
Cheers,
* Noel
October 2, 2007 at 4:47 am
Since the optimization took 5-6 hours to run I increased the "QueryTimeout" to 6 hours. It looks like everything was able to be completed. Doing a count compare between rows, looks like my rows are matching up now.
Anyone see any problems with letting the "QueryTimeOut" parameter at 6 hours?
I believe the only time it will run this long is on Sunday morning after the optimization runs.
Noel, you wrote, "You could stop the Log reader before those jobs run and -restart it after those jobs are done." Would you have to do this manually?
October 5, 2007 at 12:45 pm
Noel, you wrote, "You could stop the Log reader before those jobs run and -restart it after those jobs are done." Would you have to do this manually?
Not really that is as simple as adding a Job or a Jobstep ( depending on your usage ) which calls sp_stop_job where job_id is the LogReader job_id.
Cheers,
* Noel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply