Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Undistributed Transactions in replication Expand / Collapse
Author
Message
Posted Friday, January 31, 2014 8:48 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, April 09, 2014 3:22 AM
Points: 24, Visits: 73
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.
Post #1536813
Posted Saturday, February 01, 2014 4:01 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 6:34 PM
Points: 351, Visits: 1,653
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.
Post #1537105
Posted Thursday, February 06, 2014 3:32 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, April 09, 2014 3:22 AM
Points: 24, Visits: 73
Thanks for your reply, that's clarified it.
Post #1538547
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse