Unable to shrink SQL log file

Hello - we are running SQL Server 2005 on a 2003 Windows Server, and have a miantenance script in place to maintain the database.  Part of the script issues a DB shrink command:

[USE [LaCo_AX_Test]

"LaCo_AX_Test" is the name of our database.  The log file is at 3.7tg, and has stayed that size for the past few shrink executions.  What are reasons that a log file would not shrink down in size?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Guy Hengel [angelIII / a3]Connect With a Mentor Billing EngineerCommented:
if the database is in full recovery mode, while there are not regular transaction logs performed, that is normal.

note: if the database is in full recovery mode, you HAVE to run regular transaction log backups, and the .ldf file will NOT grow endlessy (except someone keeps a transaction open forever ...)
note: if the above is implemented, or the database is in simple recovery mode, you shall NOT need to run the shrink regulary. doing so just wastes I/O ....
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Damian_GardnerAuthor Commented:
Thanks to everyone for all of your info.  How do I tell if we're in FULL or SIMPLE mode?
Guy Hengel [angelIII / a3]Billing EngineerCommented:
it's in the database properties (advanced tab)
Damian_GardnerAuthor Commented:
Great. So looks like I'm in FULL mode.

Thanks to all again.  I'll split up the points.
no problem. :) good luck
Damian_GardnerAuthor Commented:
I know I closed the case, but I came up with another question.  I went ahead and created a backup of my logfile (which I hadn't done before), and then tried issuing a Shrink command through the SQL Mgmt interface.  It executes very quickly, and has no effect on the file size.  I'm reading about the Truncate Only command, and one of the gurus discourages using it.  If I've just made a backup of the log, should Truncate Only be ok to use?  This is an active production database, and active transactions are open against the log right now, BTW.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
the first log backup usually is not enough on it's own to make the shrink file effective.
after that first log backup, some transactions + another log backup will do the effect.
Damian_GardnerAuthor Commented:
Ah - ok.  I'll wait to see how the auto backup plan runs tonight then, and check it again in the morning.

Thanks again
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.