I have a table which has a clustered index on two columns - the primary key for the table. It is defined as follows:
ALTER TABLE Table ADD CONSTRAINT [PK_T
Clustered indexes don't actually change the physical order of the data being stored in the table it self. It hasn't been this way since SQL 6.5.
The data on the pages is stored in the correct order. The pages can be stored on the disk in any physical order.