asked on

Replication issue

Hi,

I have configured transactional replication on my servers.
Log reader agent is moving transactions from publisher to distributor correctly.
but for some reason the transaction from distributor to subscriber is taking a long time,
Undistributed commands from distributor to subscriber is high
and the estimated time to apply the transaction to subscriber is also increasing.
How can i push this transactions to the subscriber.

Please advise.

TempDBA

Check the server status of the subscriber. I mean to say in terms of CPU, memory, blocking,etc. If the subscriber health is good then you can run a profiler on the replication stored procedure to find out what time it is taking and why with the help of the plan.

ASKER CERTIFIED SOLUTION

Zberteoc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jim P.

Also what version of SQL are you using, and what OS?

Select @@Version

Open in new window

Jim P.

Can you give us an idea of the resolution?

Zberteoc

That is not enough my friend. People here spent time to give you decent answers so just saying the issue is solved won't work. Maybe you can give some more details on this. After all what you owe are just some points not money.

SP_2018 .

ASKER

Hi,

Log reader agent showed some undistributed transactions which were not marked for
replication.
I guess that was the reason the latency was increasing.
I simply dropped the subscription and the target database,
Rebuild all the indexes at the publisher side.
Created a new publication and subscrber and and it seems to have resolved the issue.

Thanks all for your help...

.