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

Replication affecting Tran Log Expand / Collapse
Author
Message
Posted Thursday, March 21, 2013 10:33 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Sunday, April 13, 2014 8:33 PM
Points: 456, Visits: 415
We have a server that we just recently setup transactional replication on and we have begun to see that the T-Log is not logically truncating in a timely manner. We removed the subscriber hoping to resolve the issue temporarily, but it doesn't seem to have resolved the issue.

I have two questions:
1. What officially has to happen for a transaction to be marked replicated?
2. What is the minimum operation to remove the hold on the offending transactions?

Thanks for all the help,
Dane
Post #1433901
Posted Thursday, March 21, 2013 10:44 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Sunday, April 13, 2014 8:33 PM
Points: 456, Visits: 415
Found this on books online:

Transactional Replication and the Transaction Log
If a database includes one or more transactional publications, the log is not truncated until all transactions relevant to the publications have been delivered to the distribution database. If the transaction log is growing too large, and the Log Reader Agent is running on a scheduled basis, consider shortening the interval between runs or setting it run in continuous mode. If it is set to run in continuous mode (the default), ensure that it is running.

Hopefully this helps someone later!

-Dane
Post #1433909
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse