Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a table with a clustered index, which shows ~70% fragmentation on a SQL Server 2008 database. I'm trying to rebuild this index:


The statement returns immediately with success, however the fragmentation is not changing. If I review the fragmentation in the SSMS, it remains the same.

I'm suspicious that it returns immediately, so it seems as if it's not doing anything. Since a clustered index determines the table layout on disk, I'd assume that this would have to be an offline task?

I guess I'm missing something and was hoping somebody could shed some light.

share|improve this question
How big is the table? – gbn Sep 16 '11 at 15:14
up vote 1 down vote accepted

How big is the table?

A small table that is only a few pages/extents rows will always show high fragmentation

share|improve this answer
This particular table is 199 rows. Data space: 0.023Mb, Index space: 0.016Mb. So yes, it's pretty small. So you are saying there is no way to improve that, and it doesn't matter? – Lucky Luke Sep 16 '11 at 15:52
It doesn't matter. This 5 8k database pages and fragmentation is measured over extents (simply) which is 8 x8 8k pages. Normally these tables should be filtered out. See – gbn Sep 16 '11 at 16:22
Thanks, this makes sense now. For some reason I thought that the tables were larger, but so far they are all small. – Lucky Luke Sep 17 '11 at 4:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.