March 25, 2014 at 9:51 am
A vendor was backloading a ton of data. At one point they asked for more disk on the K drive. Filegroups are spread across both K and L drives but they only asked for K. So our SysAdmins added disk to K and they continued. Soon after L was getting close to full so the same additional disk was added to L. Backload is all done, but now K has only 10% disk free and L has 30%. Is there some way to even this out? Should I not care? Shouldn't I see L getting used more as it has the most free space?
Thanks all.
March 25, 2014 at 10:03 am
SQL will allocate to the different files using a round robin and proportional fill algorithm, so L will be hit more.
To even them out you could do a CREATE INDEX … WITH (DROP_EXISTING=ON).
See this article:
http://sqlmag.com/blog/rebalancing-data-across-files-filegroup
March 25, 2014 at 2:21 pm
Randy Doub (3/25/2014)
A vendor was backloading a ton of data. At one point they asked for more disk on the K drive. Filegroups are spread across both K and L drives but they only asked for K. So our SysAdmins added disk to K and they continued. Soon after L was getting close to full so the same additional disk was added to L. Backload is all done, but now K has only 10% disk free and L has 30%. Is there some way to even this out? Should I not care? Shouldn't I see L getting used more as it has the most free space?Thanks all.
I think that you should not care. How much free space is open in each file in the group? If you rebuild indexes, as was suggested earlier, you will even things out. But, I'd use Michelle Ufford's outstanding index rebuild mechanism instead of a home brew. Depending on insert and update traffic, I'd consider using a scheduled job weekly.
Index defrag utility URL: http://sqlfool.com/2010/04/index-defrag-script-v4-0
Thanks
John.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply