impact on log file because of reindexing

  • we have a database of around 800 gb , the log file size is 9 gb and the free space on the drive hosting the log file is 30 gb. I want to know beforehand how much the log file would grow if i do the reindexing. Is there any mechanism to calculate this

  • There's not any real good way to predict the log space needed.

    It's worth noting that if you're in the full recovery mode, rebuilding indexes takes a lot of log space, while in simple or bulk-logged mode it won't take quite so much space. Frequently it might be better to defrag (reorganize) the index and rebuild the statistics as this will often times use less log space if that is a concern.

    Either way, I'd definitely look into increasing the space available for your log files.

  • The thing is that i have to give some approx amount of free disk space to my storage guy, currently i have 30gb free space on the log drive, i just want to make sure that i dont run out of the disk space while reindexing

    i have to get the approx disk space allocated beforehand if the space would be an issue

     

  • You might try testing rebuilding a few indexes to see what the log utilization is for varying sizes of indexes first. I'm sure it's not going to be the exact same but if you can get a general idea of how much log space is needed for X bytes of index you might be able to get a general idea of what your space requirements will be. I'm no expert on SQL Server internals so that's about all the help I can provide.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply