Thanks Andrew, this is what I get today from DBCC OPENTRAN on that DB >"No
active open transactions." BUT, I modified the configuration to SIMPLE and
cleared out the log, it is now 1024k. I'm sure there is a better way of
handling this, and I would appreciate any recommendations. If I returned it
to FULL, what other settings should I put in place to ensure that the log
file does not become too large?? There are 2 statistics settings on the
Options tab can you also explain those and recommend best performance
settings.. Thank you !!
========================================
[quoted text, click to view] "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message
news:%23I202md4GHA.3400@TK2MSFTNGP04.phx.gbl...
> Most likely you have a long running open transaction that is preventing
> the log from being truncated. What does DBCC OPENTRAN() say for that db?
>
> --
> Andrew J. Kelly SQL MVP
>
> "WANNABE" <breichenbach AT istate DOT com> wrote in message
> news:eEkMBXX4GHA.1544@TK2MSFTNGP04.phx.gbl...
>> What is the best way to manage Log file growth?? We have a document
>> management program and the MDF file is about 3.5 gig, but the LDF file
>> suddenly ballooned up to 34 gig. The data is backed up nightly and the
>> logs are backed up hourly. I thought that would allow the log file to
>> "flush out", obviously I was wrong. The file is set to full recovery
>> Model with torn page detection, (SQL2000) and when I look at the
>> percentage of unused space on that file there's only about 15% . Can
>> someone tell me why this grows this big and what I can do to keep in
>> under control??? I am running low on HD space... Thanks...
>>
>
>