October 5, 2007 at 10:30 am
I'm having problem witha transaction log of a database that has reached the HD size with almost 17GB.
The problem is that I have no space in the other disk to do perform a backup.
When I try to reduce its size or perform a checkpoint it says there is no space to do it.
Any suggestions?
October 5, 2007 at 11:15 am
I take it there's no chance you can connect a USB or FIREWIRE device and do a quick backup to that then shrink the Transaction log? Also for probably around $100 you could probably go pick one up from staples, officemax whomever...
October 5, 2007 at 2:18 pm
Also you Could Try Truncating the log ...Note that this is not recommended but given your situation it may get you out of the problem.
* Noel
October 5, 2007 at 2:27 pm
yeah I was going to recommend that as well, but there's that whole if you ever need to restore bit.
If you go this route make sure you understand the consequences. Make sure you read the bits in BOL about Transaction log Backups and what the implicatiosn are...
From BOL... [editted]
NO_LOG | TRUNCATE_ONLY
Removes the inactive part of the log without making a backup copy of it and truncates the log. This option frees space. Specifying a backup device is unnecessary because the log backup is not saved. NO_LOG and TRUNCATE_ONLY are synonyms.
After backing up the log using either NO_LOG or TRUNCATE_ONLY, the changes recorded in the log are not recoverable. For recovery purposes, immediately execute BACKUP DATABASE.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply