It will if the log isn't getting truncated. Maybe he's not backing up
the log at all. More frequent log backups will help keep down the size
since transactions committed since the last log back up will be flushed
from the new one.

There are several reasons for huge transaction logs. A DBCC DBREINDEX
will cause a very large T log. So it would be wise to make sure the
maintenance plan isn't also doing a reindex. Separate those jobs. There
are a couple of bugs that do that, too. Search the MS KB for "large
transaction logs."

Try issuing a transaction log backup only and see what happens to the
log. It's something to try as you work out the timing of other db
processes that might be causing this.

Carolyn J




-----Original Message-----
From: Sam Rieta
[mailto:mssqldba-ezmlmshield-x73425941.[Email address protected]
Sent: Thursday, June 29, 2006 11:28 AM
To: LazyDBA Discussion
Subject: RE: Want to shrink !!!

Increasing the frequency of the log backups isn't going to decrease his
log size. You're on the right path though Carolyn.
Find out what is causing the Log file balloon up like that. Fix that if
you can, than adjust the log/transaction backup frequency.

MS Sql Server LazyDBA home page