你可能已经阅读了以上文章中的理论部分:

-聚类索引，我们可以看到直接指向记录，即它的直接，所以它需要更少的时间进行搜索。此外，它不会占用任何额外的内存/空间来存储索引

而在非聚集索引中，它间接指向聚集索引，然后它将访问实际的记录，由于它的间接性质，它将花费更多的时间来访问。此外，它需要自己的内存/空间来存储索引

聚集索引实际上描述了记录在磁盘上物理存储的顺序，因此只能有一个聚集索引。

非聚集索引定义的逻辑顺序与磁盘上的物理顺序不匹配。

你可能已经阅读了以上文章中的理论部分:

-聚类索引，我们可以看到直接指向记录，即它的直接，所以它需要更少的时间进行搜索。此外，它不会占用任何额外的内存/空间来存储索引

而在非聚集索引中，它间接指向聚集索引，然后它将访问实际的记录，由于它的间接性质，它将花费更多的时间来访问。此外，它需要自己的内存/空间来存储索引

聚集索引

一个表只能有一个聚集索引。 通常在主键上进行。 聚集索引的叶节点包含数据页。

非聚簇索引

一个表只能有249个非聚集索引(直到sql version 2005的后续版本支持多达999个非聚集索引)。 通常在任意键上。 非聚集索引的叶节点不包含数据页。相反，叶节点包含索引行。

//复制自MSDN，其他答案中没有明确提到非聚类索引的第二点。

集群

Clustered indexes sort and store the data rows in the table or view based on their key values. These are the columns included in the index definition. There can be only one clustered index per table, because the data rows themselves can be stored in only one order. The only time the data rows in a table are stored in sorted order is when the table contains a clustered index. When a table has a clustered index, the table is called a clustered table. If a table has no clustered index, its data rows are stored in an unordered structure called a heap.

非聚集

Nonclustered indexes have a structure separate from the data rows. A nonclustered index contains the nonclustered index key values and each key value entry has a pointer to the data row that contains the key value. The pointer from an index row in a nonclustered index to a data row is called a row locator. The structure of the row locator depends on whether the data pages are stored in a heap or a clustered table. For a heap, a row locator is a pointer to the row. For a clustered table, the row locator is the clustered index key.

群集索引对磁盘上的数据进行物理排序。这意味着索引不需要额外的数据，但只能有一个聚集索引(显然)。使用聚集索引访问数据是最快的。

All other indexes must be non-clustered. A non-clustered index has a duplicate of the data from the indexed columns kept ordered together with pointers to the actual data rows (pointers to the clustered index if there is one). This means that accessing data through a non-clustered index has to go through an extra layer of indirection. However if you select only the data that's available in the indexed columns you can get the data back directly from the duplicated index data (that's why it's a good idea to SELECT only the columns that you need and not use *)