April 10, 2013 at 2:43 pm
Hi
I've 2008 R2 transactional replicatin establishe. One table is cauing an issue which is out of sync by 30K rows out 1.7 mil. But the other tables are doing fine and the agent seems to be running with few sec latency.
Any suggestions to troubleshoot are welcome .
April 10, 2013 at 3:45 pm
Have you looked at monitoring replication?
http://msdn.microsoft.com/en-us/library/ms151780(v=SQL.90).aspx
Are the 30k rows recent ones changed/added in the publisher? are you sure there is no filtering taking place for this article?
April 10, 2013 at 9:12 pm
As Steve has mentioned, look at the provided article...it could help. I'd also like to ask what is the nature of the table? Does it frequently get inserted/updated or have records removed? If so, this could contribute to excessive "churn" causing the replication commands to appear to always fall behind. Can you also verify whether or not if these 30,000+ rows are always the same ones or are they always different?
I've had a similar experience with a table used for processing transactions in an OLTP environment. There was so much activity in this specific table that replication couldn't keep up with it (and we only have about 300K records in the table at any given time)
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
April 12, 2013 at 7:46 am
Increase default value of the ReadBatchSize in Log reader agent & CommitBatchSize in Distribution Agent.
If the table is out of sync because of load, this may help.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply