Post reply

Undistributed Transactions in replication

  • January 31, 2014 at 8:48 am

    #396203

    Hi,

    I recently had a problem with replication where there were large numbers of Undistributed transactions/commands building up.

    In Replication monitor, I right clicked my publisher and stopped and started synchronisation which cleared them all down and reset the undistributed transactions counter to zero.

    I just wanted to know, are all of the undistributed transactions pushed through and applied to the other replicated databases or are these undistributed transactions lost forever?

    What happens to them when Replication is re-started?

    I'm using SQL Server 2008 R2.

    Thanks.

  • February 1, 2014 at 4:01 pm

    #1685315

    It happens when the log reader agent /distribution agent are running slow. They will not get lost. They will get applied to the subscriber database in order. If they don't get applied you will receive error --log scan occurs before the current start of replication in the log. This might because of the server activity.

  • February 6, 2014 at 3:32 am

    #1686509

    Thanks for your reply, that's clarified it.

Viewing 3 posts - 1 through 2 (of 2 total)

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