February 1, 2008 at 8:27 am
I'm working with a SQL2K database. I noticed that the log file size is more than 150mb, but it only contained 11mb of data. Apparently it had grown large in the past before someone implemented log file backups.
The drive has more than 500GB of free space, so we're not in danger of filling it up soon. Is there a compelling reason to shrink the log file at this point? Or would the "if it's not broke, don't fix it" rule apply in this case?
February 1, 2008 at 9:29 am
Y, if space isn't an issue it's always best to let the log keep some free space. If performance isn't an issue you can shrink it, but it really doesn't sound like there's a need to.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARant
February 1, 2008 at 9:34 am
I agree with crever. No need to do it if you don't need the space.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply