Yes, you can simply add another job step to use the DBCC SHRINKFILE statement.
However it is typically recommended that you not shrink the files on a regular basis. Doing so causes the database engine and disk subsystem to do extra work that it doesn't need to do. If the log has grown to that size there is a reason for that, and the log will probably grow to that size again. Shrink the file after each log backup gives you a false sense of security.
Last Wiki Answer Submitted: February 2, 2009 8:31 pm by Denny Cherry64,520 pts.
All Answer Wiki Contributors: Denny Cherry64,520 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Is your database in simple or fully logged recovery mode?
If fully logged you could considered increasing the frequency of your transaction log backups.
As Mr.D says it’s best not to shrink at all (from a performance perspective) if at all possible.
Regards,
SCM.