July 5, 2005 at 12:56 pm
T-log grows to 20GB everytime I rebuild all indexes on DB even though I'm backing up the log file every 15 mins. DB size is 50 GB with 30GB of data on it. Do you think there's a very big table that is around 20GB that's why everytime I rebuild all indexes it grows to 20GB also?
July 5, 2005 at 12:57 pm
What is the size after you back it up?
July 5, 2005 at 1:00 pm
it's 30GB.
July 5, 2005 at 1:02 pm
Does it shrink down eventually?
July 5, 2005 at 1:06 pm
The used space on the log file do shrink but the file doesn't. Log file doesn't shrink once it's been increase. any more thoughts?
July 5, 2005 at 1:09 pm
Maybe this can help :
http://qa.sqlservercentral.com/forums/shwmessage.aspx?forumid=92&messageid=93685
July 6, 2005 at 5:26 am
H!!,
I feel you are having an ERP system in the front end with more number of users..if you are very pirticular about decreasing the size of log file then you can change the recovery model to simple..but yu won't be able to restore the T-log in case of any disaster...
Vinod (DBA)
HTC Global Services..
09840856202
July 6, 2005 at 11:46 am
We have a procedure in place before reindexing (during maint window), which kicks out all users and put db in a simple mode...
...and subquently, after it finishes the process. remember to put it back to the full recovery mode.
my 2cents
July 7, 2005 at 5:08 am
We have a large ERP system of 0,5+TB
When we are reindexing we are making a full backup then we swith to bulk logged, reindex, switch back to full recovery and do an another backup.
Bye
Gabor
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply