Posted by John Rivers on 04/28/06 15:41

Hello,

when a clustered index is present the records *are* physically ordered
on disk to match the index

that is the whole point of a clustered index

and by default a select statement with no ORDER BY will always return
data in the order of the clustered index (when present)

this can easily be proved by watching the Execution Plan

the issue i am trying to highlight concerns the order of the records on
disk when a *compound* clustered index is present

i have seen cases when it is not as expected

maybe you can enjoy reading that RDBMS book :-)

best wishes,

john

• Next in forum: Re: Compound Primary Key - order not as expected
• Prev in forum: Re: SQL Function
• Thread view: Re: Compound Primary Key - order not as expected

[Reply to this message]