Yep. I've had this problem. My log device got to 550 Meg before I
figured out how to fix it :).
Quite simply, run a "DBCC CHECKDB (Emerald)". This will discover a few
little anomalies with the transaction log and fix them. Once this check is
done, truncate the transaction log and you should now see that most of the
log is now free.
I can't tell you how relieved I was when I saw that. There's something
depressing about watching your transaction log grow and grow, and you can't
do a thing about it.
Oh, it's a good idea to schedule a database check every month. That's
what I do now and everything has been working perfectly.
--------------------------------------#------------------------------------
David Khoury | "Where's the KABOOM ??
Technical Manager & Comms Engineer | There was supposed to be an
dave@flex.com.au | earth shattering KABOOM!!"
http://www.flex.com.au/~dave | Marvin the Martian
--------------------------------------#------------------------------------