[dba-SQLServer]index limits

Francisco H Tapia my.lists at verizon.net
Mon Apr 14 18:20:58 CDT 2003


Susan,
>From BOL, Why Not use that vitamin A if you're gonna eat all those carrots
Rabbit :D
Keyword Create Index....
NONCLUSTERED

Creates an object that specifies the logical ordering of a table. With a
nonclustered index, the physical order of the rows is independent of their
indexed order. The leaf level of a nonclustered index contains index rows.
Each index row contains the nonclustered key value and one or more row
locators that point to the row that contains the value. If the table does
not have a clustered index, the row locator is the row's disk address. If
the table does have a clustered index, the row locator is the clustered
index key for the row.

Each table can have as many as 249 nonclustered indexes (regardless of how
they are created: implicitly with PRIMARY KEY and UNIQUE constraints, or
explicitly with CREATE INDEX). Each index can provide access to the data in
a different sort order.

For indexed views, nonclustered indexes can be created only on a view with a
clustered index already defined. Thus, the row locator of a nonclustered
index on an indexed view is always the clustered key of the row.

-Francisco
http://rcm.netfirms.com

On Monday, April 14, 2003 3:07 PM [GMT-8],
Susan Harkins <harkins at iglou.com> wrote:

: I know SQL Server limits a table to one clustered index -- how about
: nonclustered? Access' limit is 32 -- does SQL Server have a limit on
: nonclustered indexes in one table? Thanks!
:
: Susan H.




More information about the dba-SQLServer mailing list