Log file growing too much

[icemel]

Hi,

I just ran a performance analysis on one of our production databases, and it indicated that some of the logfiles are growing too much and too often.

I would like to verify this myself. What is the best way to track what's going on with the logfiles... that is, can I view how often the log files are growing, and what time of day this is occurring? Is there a history of this somewhere?

And how can I determine the optimal size of the logfile?

I am kind of confused as to how to go about this.

Thanks

 

[micha123]

Please try the following undocummneted command:

 dbcc sqlperf(logspace)

you can insert the results into a table on a regular basis and investigate them automatically.
The size of your transaction log depends on the size of your transactions between database/transaction log backups (depend in which recovery mode you are).
You decide the maximal size, and backup whenever you need to truncate the transaction log.

M.

"A long life is when each day is full and every hour wide!"
(A Jewish Mentor)
M.