May 14, 2009 at 6:37 pm
This primarily Oracle DBA who has also had SQL Server responsibilities could use a good description under 2005 of what happens with transaction log backups. At my former employer we use to take a backup of databases on server nightly (full recovery model) with hourly transaction log backups which I understand removes inactive transaction entries. That should serve to manage the size of the log but does not shrink it. If the transaction log blows up in size what is the best method to decrease its size? Additionally, what would the reason to backup the transaction log with the NO_TRUNCATE option? I believe my former team would use that option to manually capture active transactions since the last backup before doing a recovery.
May 14, 2009 at 8:14 pm
Gail wrote a great article I link to in my signature. It would be worth the read for you.
As for using TRUNCATE_ONLY - there is absolutely no reason to use that at all. Ever!
If you have an extraordinary event that grows the log file, then once you have backed up the transaction log you can use DBCC SHRINKFILE to shrink the file back to normal. This should not be something that you schedule on a regular basis, since then the log file is just going to grow again.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply