June 11, 2014 at 9:14 am
Hi all,
I met with a strange replication error today...at least it is strange for me though. Our replication was active and running well. However, I had to start the log reader agent job to make it work. Once, it started fine I checked on the synchronization status for that particular subscription and it errored out stating this "msdb is under recovery...wait until recovery is finished", but this is bull crap...if it was in recovery how can I see my db's and agent jobs. I ignored that and went ahead and opened replication monitor but then I could see records being applied at the subscriber but it was heck lot slow and I couldn't notice any pending transactions even though there were lot of transactions to be applied.
Basically, I wanted to tweak in some parameters but I am not sure how to do those for e.g: maxbcpthread, commitbatchsize...etc. Pls. let me know how I can reduce the replication lag and increase the commit rate at the subscriber and also wanted to know about the weird error noticed.
Regards,
Faisal
June 11, 2014 at 9:25 am
Not sure about the error you are receiving, but you can look at setting subscription streams to potentially get a performance boost - check out this article here: http://blogs.msdn.com/b/repltalk/archive/2010/03/01/navigating-sql-replication-subscriptionstreams-setting.aspx
This and other options are pretty easy to set up at the job-level
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply