October 8, 2007 at 7:17 am
Our transaction log gets really big after the optimizations job runs on our DB. This job is part of a generic DB Maintenance Plan that was created by our remote DBA. We no longer contract with these remote DBA's and I am concerned about the transaction log size. I am not a DBA by trade but I know enough to be dangerous. Any suggestions on why this optimizaitons job is causing the transaction log to grow so rapidly and any alternative strategies for this activity? Thank you.
October 8, 2007 at 7:42 am
There are many reasons for the tlog to grow, during maintenance one frequent reason is dbreindex. Switching to bulk recovery mode before the reindex and then switching back reduces the growth of the transaction log (the backup of the log is likely to be larger though).
Regards,
Andras
October 8, 2007 at 9:53 am
A rebuild of the indexes usually requires 1.5x the space of the largest table for data, depending on fragmentation it might require more in the log. That's likely what is.
Andras has a good suggestion for helping with space, but you might just need that space allocated. If you have the space, then it doesn't hurt to let it just stay that large.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply