Apparently the index you tried to move was the one supporting the primary key of your table.
That index must 100% match your tables PK definition.
Altering that column sequence results in a drop and re-create of the primary key constraint !
Also keep in mind, the (uniquified if needed) clustering index key will be added to all NCI !
That's one of the reasons why you should keep your clustering index as narrow as possible.
Also keep in mind that the actual data resides IN the clustering index (at leaf level), so altering the clustering index's column order will cause the clustering index to be rebuilt, hence, 100% rewritten and all NCI will have to be modified to get the new CLIX key ref.
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