How to fix transactional replication latency
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 63%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECK%3C/text%3E%3C/svg%3E)
Chaitanya Kiran
801
Reputation points
Good Morning All,
We are facing replication latency issue. I checked for blocking, long running transactions or bulk operations running. I tried re-running the distribution agent job also. But still the latency exists. Could you please tell me what all I need to do to fix the latency
Thanks,
Chaitanya
SQL Server Database Engine
{count} votes
-
Ben Miller-(DBADuck) 195 Reputation points MVP2025-07-29T14:41:45.12+00:00 Replication latency is a broad topic. Latency in what fashion? What is your link between the replicas? Where is the distributor? Is it a Pull subscription or Push?
-
Chaitanya Kiran 801 Reputation points
2025-07-30T07:36:45.05+00:00 Latency is about 20 minutes between distributor and subscriber. I already checked slow storage or slow network or large transactions and they all are good. It is a Push subscription.
Sign in to comment
Sign in to answer