October 17, 2011 at 10:58 pm
Does the existence of Transactional Replication affect on the speed of Insert into Publisher table,specially when we try to insert 1000-3000 record in 2-3 sec?
October 18, 2011 at 12:02 am
It can. Mainly in terms of making the transaction log hold onto data longer and the usual effects from that.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
October 18, 2011 at 12:19 am
In our production environment(SQL SERVER 2008 R2) We have transactional replication,Recently we have added a process that try to insert large number of Records(1000-3000)in 2-3 second.When I run the profiler,I noticed that after some Inserts(Insert runs very fast 0 ms),I have delay from 10-700ms.I am wondering if this delay is related to Log read agent or generally cause of Replication?How can I test that?
October 18, 2011 at 12:25 am
Please configure the perfmon counters for the latency and see the result.
October 18, 2011 at 1:13 am
Aspet Golestanian Namagerdi (10/18/2011)
In our production environment(SQL SERVER 2008 R2) We have transactional replication,Recently we have added a process that try to insert large number of Records(1000-3000)in 2-3 second.When I run the profiler,I noticed that after some Inserts(Insert runs very fast 0 ms),I have delay from 10-700ms.I am wondering if this delay is related to Log read agent or generally cause of Replication?How can I test that?
Recommeded Readings:
How to: View Information and Perform Tasks for the Agents Associated With a Publication (Replication Monitor)
http://msdn.microsoft.com/en-us/library/ms151148(v=SQL.105).aspx
How to: View Information and Perform Tasks for a Publication (Replication Monitor)
http://msdn.microsoft.com/en-us/library/ms151771(v=SQL.105).aspx
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply