Transaction Log Fails to Shrink

My buddy created a Shrink Transaction Log task for a Tran Log that grows to roughy 1.5 GB every night.  (A sizable job that must be logged runs every evening accounts for this increase.)  He'd like to reduce the log after the job runs, but his Shrink Database Task fails to shrink the log file at all.  The Maintenance Job Log file shows that the job runs successfully, but with no results.  What may be preventing the Tran Log from shrinking?
jdanaAsked:
Who is Participating?
 
dportasConnect With a Mentor Commented:
Log will only remove unused space from the log.

Shrinking should never be scheduled to run on a regular basis. It should be run in exceptional circumstances only. Continual shrinking and growing is a huge waste of resources, causes unwanted fragmentation and in practice it saves you no disk space at all. Don't schedule the shrink task. Set the log to the size it needs to be and then leave it alone.
0
 
jdanaAuthor Commented:
Sounds reasonable.  Thanks for the advice.
0
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.