Should I shrink DB Logfile?

I have a production database that is 132GB but has a log file of 59GB.  I perform a full backup each night but the log file continues to grow.

Is there any harm or what is the preferred process to shrink the log file.

This is a SQL 2005 database.
jdr0606Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Steve WalesSenior Database AdministratorCommented:
You log file will continue to grow (if you are in Full Recovery Mode) unless you are running transaction log backups too.  Full backups alone are not enough.

Have a read of this article I wrote to address the hows, whys and where fores of SQL Server Transaction logs and why they grow and what you can do about it.

http://www.experts-exchange.com/articles/11077/How-to-shrink-a-bloated-log-file.html

Come back with any questions.
jdr0606Author Commented:
I have maintenance plans setup to run transaction log backups every 30 minutes from 8:00am to 7:30PM 7 days a week in addition to the full backups each night.
jdr0606Author Commented:
Based on my previous comment am I OK to perform an .LDF backup and then a DBCC Shrink on the log file?
Anoo S PillaiCommented:
The size of log file has grown for a reason, It could be failed log backups OR long running transactions OR a large transaction etc. If you shrink the log file and if the root cause scenario repeats , the log file would grow again and that operation is comparatively costly ( side note - your transaction may fail if not enough space is available for log file to grow ).

If you could identify the reason behind log file is grown and you are sure that the same scenario is not going to repeat, a shrinkfile may not do that much harm.

Please refer DBCC SHRINKFILE for further details.
Steve WalesSenior Database AdministratorCommented:
You can attempt to shrink the log file any time really.

Ideally try to do it in a maintenance window or period of low activity.

When I need to do this, I usually run the log backup twice in a row and then run the shrink command twice (in flight transactions may stop the shrink from happening).

Then watch the size of the file.  If it grows back to a large size again, then you have an issue of a large transaction volume making the log file grow that is happening between log file backups.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.