Re: Compound Primary Key - order not as expected
- From: "David Portas" <REMOVE_BEFORE_REPLYING_dportas@xxxxxxx>
- Date: 28 Apr 2006 06:20:48 -0700
John Rivers wrote:
and by default a select statement with no ORDER BY will always return
data in the order of the clustered index (when present)
Not true at all. As Joe says, tables are not logically ordered. There
is no guarantee that any queries will match the physical order on disk
or in a clustered index.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
.
- References:
- Compound Primary Key - order not as expected
- From: John Rivers
- Re: Compound Primary Key - order not as expected
- From: --CELKO--
- Re: Compound Primary Key - order not as expected
- From: John Rivers
- Compound Primary Key - order not as expected
- Prev by Date: Re: Compound Primary Key - order not as expected
- Next by Date: Re: Limits on rows in a table
- Previous by thread: Re: Compound Primary Key - order not as expected
- Next by thread: Re: Compound Primary Key - order not as expected
- Index(es):
Relevant Pages
|
