MSSQL LOG shrinking
Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.
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
discussion Filed Under:
Comments
It seems that bpnotify will not work with SQL backups....
http://support.veritas.com/docs/272332
You can use maintenance plan inside the db engine
Just create maintenance plan for shrink and run in schedule after the backup
I was thinking about it.
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 Veronezi Mendes
EMC TA - Pre Sales at Compwire
Londrina - Pr - Brazil
Thanks
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..
Claudio Veronezi Mendes
EMC TA - Pre Sales at Compwire
Londrina - Pr - Brazil
I know that the MS Admins
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.
Would you like to reply?
Login or Register to post your comment.