[dba-SQLServer] Clustered index

A clustered index physically re-orders the table into the specified
sequence. Given the size of your table, this may take some time.

The point of a clustered index (AFAIK) is to group objects in contiguous
proximity for the most rapid retrieval of proximate objects. For example,
given Customers and Orders, a covering index might be clustered so as to
guarantee that Customer X's Orders are available within a single page or
perhaps two, thus causing minimal disk hits.

If this sort of thing is not important, then clustered indexes are beside
the point, and create needless index-creation time.

A.

On 12/8/07, jwcolby <jwcolby at colbyconsulting.com> wrote:
>
> I have a table with physical fields PKID, FldNameID, Data.  I want to
> create
> a clustered index on that based on the field order FldNameID, Data, PKID.
> Is the index based on the physical order of the fields or the order of the
> fields specified when you create the index?
>
> IOW I went into the widget that creates indexes, specified the fields in
> the
> order I desire them in the index, and checked the Clustered check box.  It
> certainly appears that the index will create by the order I specified them
> in the index widget (which is what I want).
>
> But is that true?
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>