May 14, 2008 at 2:35 pm
We implemented transactional replication on a large database (350 gb).
The snapshot has been applied (took around 12 hours) and things seem fine, however when I look in the subscription under undistributed commands I see 887647 and this number has not gone down any at all even after 30 minutes.
I have set my remote timeout to 0 and I don't see any errors in the replication, but why are the 887647 commands replicating?
May 14, 2008 at 3:00 pm
After another 40 minutes this number has dropped to 395420 so it is working.
I suppose I was expecting the number to drop gradually over short periods versus dropping in large chunks over longer periods.
Someone suggested changing the -CommitBatchSize and -CommitBatchThreshold parameters in the distributor job (I also read here that it may be a good idea http://www.sqlservercentral.com/articles/Transactional+Replication/62446/).
Can I simply stop the distributor job, make the change, and restart the job? Will that cause any issues?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply