May 4, 2011 at 1:42 pm
I have a table with 3 indexes, one clustered, one primary key, and one other index. I dropped the primary key constraint and dropped the non-clustered index. I verified that the only remaining index on the table was the clustered index. I then dropped the clustered index and it ran for more the 40 minutes. I was expecting it to run quickly since it was the only remaining index. Can anyone explain why the drop of the clustered index takes so long in this case?
May 4, 2011 at 1:53 pm
that may be normal, depending on the size of your table.
The clustered index actually holds the data rows at its leaf level (bottom level)
So, if you drop the clustered index, it has to move all rows to a heap space, so it will rewrite the whole table.
Check books online "Table and Index Architecture"
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply