[dba-SQLServer] full transaction logs

I know that some people have received a message that their transaction log
is full, but I personally never have. I don't know what I'm doing right.
Recently we changed our strategy on transaction logs. Now we back up the log
(only the log) four times a day and nightly do a dbcc shrinkfile, so the
living log is peanuts compared to what it used  to be. Before I got here
there was a nightly process that dropped a table and then recreated it and
did thousands of inserts. As a result, the log file was huge -- way larger
than the 18 gig db itself. We changed that process dramatically and the log
file shrank dramatically too.
Arthur
On Wed, Sep 10, 2008 at 4:33 PM, Susan Harkins <ssharkins at gmail.com> wrote:

> Are full transaction logs still a problem in 2005 and 2008? I'm just
> wondering if they've done anything automatic to warn the administrator or
> to
> avoid the problem altogether.
>
> Susan H.
>