SQLServerCentral.com / SQL Server 2008 - General / SQL Server 2008 / Concerns with Transaction replication parameters / Latest PostsInstantForum.NET v99.99.99SQLServerCentral.comhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 09 Dec 2016 19:05:45 GMT20RE: Concerns with Transaction replication parametershttp://www.sqlservercentral.com/Forums/Topic1402157-391-1.aspxI'm interested to see if changing those values fixes your issues. The connect item is old, but the Microsoft comment about readbatchsize being fixed in next release was on Feb 2011, after R2 was already released, so not sure if they're referring to R2 or 2012.Thu, 03 Jan 2013 18:36:21 GMTAndrew GRE: Concerns with Transaction replication parametershttp://www.sqlservercentral.com/Forums/Topic1402157-391-1.aspx[quote][b]foxxo (1/2/2013)[/b][hr]Reduce your readbatchsize, it's too high which is why you're seeing the message:[url]http://www.sqlservergeeks.com/blogs/Abhay_c/sql-server-bi/455/sql-server-fine-tuning-transactional-replication-performance-part-1[/url]I'm thinking of changing the readbatchsize parameter from 5000 to 1000. And see if that makes sense. I've read that changing Readbatchthreshold can cause very slow performance in 2008[url]http://connect.microsoft.com/SQLServer/feedback/details/478792/using-the-readbatchthreshold-parameter-in-logreader-agent-leads-to-slow-performance[/url][/quote]This connect I think is for SQL 2008. Our's is SQLserver 2008 R2 Sp1. This issue would have been resolved. The date of the issue reported is also in 2009. I assume the issue would have been resolved in SQLserver 2008 R2. Thanks for answering the post. Thu, 03 Jan 2013 01:20:25 GMTbaabhuRE: Concerns with Transaction replication parametershttp://www.sqlservercentral.com/Forums/Topic1402157-391-1.aspxReduce your readbatchsize, it's too high which is why you're seeing the message:[url]http://www.sqlservergeeks.com/blogs/Abhay_c/sql-server-bi/455/sql-server-fine-tuning-transactional-replication-performance-part-1[/url]I've read that changing Readbatchthreshold can cause very slow performance in 2008[url]http://connect.microsoft.com/SQLServer/feedback/details/478792/using-the-readbatchthreshold-parameter-in-logreader-agent-leads-to-slow-performance[/url]Wed, 02 Jan 2013 23:59:45 GMTAndrew GConcerns with Transaction replication parametershttp://www.sqlservercentral.com/Forums/Topic1402157-391-1.aspxHi SQL Experts, We have an OLTP that was configured in P2P replication. Both the peer nodes were running with SQLserver 2008 R2 SP1. We noticed that one of the DB we have a lot of latency issues and decide to change the readbatchsize from default 500 to 5000. it took 10 hours before we removed the latency. But on the other hand we are seeing a lot of messages in the log reader. We are using push subscription. " Approximately 500000 log records have been scanned in pass # 3, 1 of which were marked for replication, elapsed time 6006 (ms).'."These messages popup every 10 or 15 mts time. Is these message a real concern for us to look and reduce the readbatchsize parameter. Will Readbatchthreshold is a better option than readbatchsize? Can you help me?Thank youWed, 02 Jan 2013 20:42:09 GMTbaabhu