i have a table with a clustered index on a GUID......
it has 2.2 million records.
we are having a time out error when trying to do a summary query....
from what i have read it is a bad idea to put a clustered index on an essentially random key.
records added are effectively placed all over the drive and there would be a lot of shuffling to get them back in order...
so i think i have made the correct decision to remove the clustering from the index.
from what i can determine this is the command to do that
alter table tikdet
drop constraint PK_TikDet
however, i think ... from what i read also... that in order to do this sql does something with all the existing indexes as well
there are 7 indexes on this table and 1 clustered index the indexes were mostly a result of running the sql profiler and using its reccomendations.
question 1... am i correct in the descision to remove the clustering from the guid? i still want the index, just not clustered.
question 2... to remove the clustering, does sql have to rebuild all the keys? what kind of performance hit would the system get while this was happening.