March 28, 2011 at 1:13 am
This is a General Question. We have a Transaction Repliation with Update Subscriber. There is alway latency happening . Can any one tell why this Latency happens. I have found that there were few blocking that happened is this due to Blocking or some other reason. ?? Can any one please explain
Regards,
Sandeep.
March 28, 2011 at 3:36 am
latency is a kind of counter which give you information on how much time it take subscriber to get updated.
In your case as its transaction replication with updating subscriber you can use replication monitor and then latency counter to determine how frequently your data is being replicated/synced and also updating the data from subscriber to publisher also depends on the the type of configuration is either queued updating or immediate updating.
----------
Ashish
April 12, 2011 at 7:14 pm
Analyze the latency using tracer token. Also check the LAN or WAN staus.
-MJ
Please do not print mails and docx unless it is absolutely necessary. Spread environmental awareness.
April 21, 2011 at 1:11 am
Tracer token are useful in determining the latency, but as you mentioned blocking, Check for distributor clean job it is most often blocking spid. Try schedule the job by inspecting the blocking information.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply