Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Transactional replication Expand / Collapse
Author
Message
Posted Friday, April 19, 2013 1:01 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, March 13, 2016 8:47 AM
Points: 362, Visits: 1,821
today we lack of disk space for distribution database primary file and we added space

but during no space replication failed, agent thrown error

after some log reader and dist agent started their own and running fine

my question is will agents picksup where they left off?

Post #1444570
Posted Friday, April 19, 2013 1:23 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, November 21, 2016 9:50 AM
Points: 863, Visits: 1,318
Until and unless the transaction logs are not truncated, it will work fine because log reader agent works by monitoring the transaction log of each database configured for transactional replication and copies the transactions marked for replication from the transaction log into the distribution database. The Distribution Agent moves the transactions held in the distribution database tables to Subscribers.
Post #1444582
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse