June 23, 2006 at 6:25 am
Seriously... It's not like I'm building a clustered index. Just leave the data in the order it's in and forget about it.
Is it rebuilding all non-clustered indexes on that same table or something? wtf?
tx, greg
June 23, 2006 at 8:50 am
Yes, it is rebuilding all non-clustered indexes on the table. The clustered index key is part of all non-clustered indexes on a table where both exist, so any time you drop or reindex the clustered index, all non-clustered indexes must also be rebuilt.
June 23, 2006 at 9:53 am
Why is it taking just as long when I drop all the non-clustered indexes first?
What else is it doing?
June 23, 2006 at 12:29 pm
A clustered index is part of the physical table. It must remove the index rows from the table to 'return' it to a heap (table w/o clustered index).
See books online for a graphic under clustered indexes, architecture
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply