[Theforum] Re: Changes to the VotingReqs document

Madhu Menon webguru at vsnl.net
Thu Feb 7 00:42:16 CST 2002

(sigh) This will be my last message on the subject.

At 05:46 PM 2/6/2002, Warden, Matt wrote:
> >Setting a clustered index on a column (often the primary key) in a table
> >in SQL Server physically rearranges the order of the rows in the
> >table. The original comment was about whether data could be rearranged in
> >a table itself, to which I responded that a clustered index did this.
>I know. Which is why I responded.
>It doesn't.
>(see first message)

Then you need to read the SQL Server docs more carefully.



A clustered index determines the physical order of data in a table. A
clustered index is analogous to a telephone directory, which arranges data
by last name. Because the clustered index dictates the physical storage
order of the data in the table, a table can contain only one clustered index.


and yet again:


Clustered tables are tables that have a clustered index.

The data rows are stored in order based on the clustered index key.

The indices you're talking about are *non-clustered* indices.

Other articles that say the *same* thing:



<<<   *   >>>
Madhu Menon
User Experience Consultant
e-mail: webguru at vsnl.net

More information about the theforum mailing list