December 7, 2007 at 12:35 am
In sql 2005 while I try to truncate/shrink the log file
manually after taking full backup the transactional log backup gets failed.But after again full backup completion the transactional log backup runs fine.
My question is why it is happened.in sql 2005 is it not possible manually shrink/truncate transactional logs.if possible how?
Thanks,
Litu
December 7, 2007 at 4:20 am
Off course, its possible & very simple to do.
Just go to SSMS > Right click on the Database > All Tasks > Shrink > Files (In file type option select log)
--Ramesh
December 7, 2007 at 8:31 am
You should not need to do this after a full backup. You either have a misconception about what is happening or are not administering the system properly.
The log does not need to be shrunk regularly. Maybe after some large import, but if you do large imports regularly, leave the log large. It does not hurt your system or slow it and you're performing unnecessary IO.
If you don't have enough disk space, get more. This is poor configuration and the more a disk is full, the slower it runs on your system. That should be enough reason to add more space.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply