Transactional latency issues between Distributor and Subscriber

Question

Transactional latency issues between Distributor and Subscriber

Viewing 5 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 1

Replication could slow down when the distribution log clean up job runs. This is just one issue. If the Disk IO is busy, it could slow down replication. This can happen if someone is copying a large Back up file from the distributor to somewhere else. Check if there are any Bulk updates happening on the publisher at the time of the slow down. If there are lots of commands to be propagated from the distribution, this can cause slow down as well.

-Roy

ABAS101 SSCommitted Points: 1894 More actions · Answer 2

When this latency occurs, have you verified that there is nothing blocking at the Subscriber?

RML51 SSCarpal Tunnel Points: 4410 More actions · Answer 3

The Distrubution cleanup job runs every 10 minutes. I believe that this is a default interval and its always been set to 10 minutes. It seems to run okay even when latency is slow.

I know that there are no bulk copy processes of any kind running.

There is no blocking anywhere.

Thanks for your ideas - I'm stumped!

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 4

Do you see any high IO on the distributor or Subscriber?

And here is a wild question, Do you have antivirus installed on the servers and is it set to run at a certain time doing a full scan?

-Roy

RML51 SSCarpal Tunnel Points: 4410 More actions · Answer 5

We don't run antivirus software on any of the nodes.

I don't administer the SAN, but I've asked those administrators to look at I/O. They aren't in agreement that it is high. I don't think that they have a good stick to measure against. However they are performing some SAN upgrades this weekend that are suppose to improve throughput.