Excess Log file sizes

Hello, we've had some issues with our backups and some of our log files have
grown to 15 GB. We since corrected the problem and backups are running
again but the log files remain the same size.
In one particular case, I have a database that, via Taskpad, I can see is
45GB with 26GB of free space and the log is 15GB with 14.8 GB of free space.
I notice on the properties page for this database that AutoShrink is not
checked. Is this the problem? Is there any downside to enabling
autoshrink?
I've read all different articles that give instructions on compacting this
and wanted to know what you folks thought would be the preferred way to A)
reducing the log file size issues I not face and B) best practices for
keeping them from reoccurring once I get these files down to where they
should be.
Any help would be appreciated!
Jim
If you've seen this article, then the rest will probably tell you the
same...
http://www.karaszi.com/SQLServer/info_dont_shrink.asp
Ekrem nsoy
"Jim" <jj@.nospam.com> wrote in message
news:%23Lz1vbwnIHA.2396@.TK2MSFTNGP02.phx.gbl...
> Hello, we've had some issues with our backups and some of our log files
> have grown to 15 GB. We since corrected the problem and backups are
> running again but the log files remain the same size.
> In one particular case, I have a database that, via Taskpad, I can see is
> 45GB with 26GB of free space and the log is 15GB with 14.8 GB of free
> space.
> I notice on the properties page for this database that AutoShrink is not
> checked. Is this the problem? Is there any downside to enabling
> autoshrink?
> I've read all different articles that give instructions on compacting this
> and wanted to know what you folks thought would be the preferred way to A)
> reducing the log file size issues I not face and B) best practices for
> keeping them from reoccurring once I get these files down to where they
> should be.
> Any help would be appreciated!
> Jim
>