October 5, 2009 at 7:51 am
How to handle the situation if the transaction log diskspace was full?
October 5, 2009 at 8:20 am
First, You should take the necessary precautions to see that the transaction log disk pace is never full.
You should either put the database in simple recovery mode or should have regular transaction log backups scheduled as part of recovery process.
From MSDN
Alternatives for responding to a full transaction log include:
Backing up the log.
Freeing disk space so that the log can automatically grow.
Moving the log file to a disk drive with sufficient space.
Increasing the size of a log file.
Adding a log file on a different disk.
Completing or killing a long-running transaction.
October 5, 2009 at 8:28 am
Also, please read the last article I have referenced in my signature block below regarding Managing Transaction Logs.
October 5, 2009 at 9:02 am
It varies by version, but first, you need to clear the log out.
The basic steps are to clear the log of active transactions, then shrink it, and then set up log backups. You can use the maintenance plan wizard to do this. Once you have a few days of log backups, you can tell if your log is sized well by looking at the largest backup size. Give yourself a bit of a pad beyond that.
And read the article Lynn mentioned. Even if you don't understand it all, it will help you better deal with a log.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply