MSSQL LOG shrinking

[Claudio_Veronez]

Hi there,

I would like to know if is there any way of automatically run an script or something to Shrink a MSSQL-log file after the end of the backup (status 0)


Any Idea? material ?

Thanks a Lot

[Mouse · Accepted solution]

Just create maintenance plan for shrink and run in schedule after the backup 

[Mouse]

Document ID: 272332 
http://support.veritas.com/docs/272332

The bpstart_notify and bpend_notify scripts do not get called during a SQL database backup.

---

Details:

This issue is related to a limitation of the DBBACKUP.EXE process. During SQL backups, DBBACKUP.EXE is the process responsible for the backups. This process does not have the capability of calling thebpstart_notify and bpend_notify scripts; therefore, the scripts will fail to execute. 

[Claudio_Veronez]

the problem is,

Lets supose that the backup fail..

MSSQL will try to shrink a LOG that isn't truncated yet.


Would it be a problem??

[Claudio_Veronez]

Thank you Mouse,

Our DBA will make a script to shrink every hour, there is no problem on shrinking a log that isn't truncated.


thanks..

[James_Perry]

I know that the MS Admins here have something inline with the backup job that shrinks/truncates the logs for all SQL backups when run successfully.  If the backup fails then they run a log job that backups the logs and then shrinks them.  Normally the log job is scheduled to start half an hour after the SQL job and closes the window two hours before the SQL job normally completes.  That way if it does fail the SQL Server does not have issues with huge logs.