transaction log & transactional replication

[kitty]

I have a Ms sql db which always bears a continuous growing transaction log. It seems that there is lots of active transaction log there because the log never drops even I manually make checkpoints. I didn't enable the 'trunc. log on chkpt.' because transactional replication is running. I think tranasactional replication can cause the log grows quickly.

Is there any method that can shrink the log under such situation?

Regards
Kitty [sig][/sig]

 

[jnicho02]

Normally, transaction logs are shrunk by backing them up. A (nightly) main backup should reset the log, and this can be added to be regular (1/2 hourly) transaction log backups.

There is a server setting that says how long it should take for a restore. This can affect how much transaction log is cleared.

However, I would have to see exactly how replication transfers the transactions to the other machine, and whether it has to somehow mark transactions as sent before they can be cleared from the log? Anyone got any details?

In general, people see the transaction log as some giant file that inexplicably grows and should be truncated as often as possible. There are almost NO situations in which this should be done on a live server. Anyone who does that should write 'the transaction log is my saviour and not my enemy' on the blackboard 100 times. It is of course a log of all the changes that have been made to your database since the last backup, meaning that you could restore your database to almost the last minute before failing....rather than to yesterday's state. Sorry to ramble on, but if your server crashes and you lose a whole days worth of customer orders they are going to kill you! [sig]<p> <br><a href=mailto: > </a><br><a href=

http://www.geocities.com/jnicho02/>my

home</a><br> [/sig]

 

[TomSark]

Make sure that your log reader agent is functioning properly.

Tom
[sig][/sig]