When partitioning a nonunique , nonclustered index , the database engine adds the partitioning column as a nonkey included column of the index , if it is not already specified 在对非唯一的非聚集索引分区时,如果未指定,则数据库引擎会将分区依据列添加为索引的非键(包含性)列。
When you partition a nonunique , clustered index , the database engine by default adds the partitioning column to the list of clustered index keys , if it is not already specified 在对非唯一的聚集索引分区时,如果未指定,则默认情况下数据库引擎会将分区依据列添加到聚集索引键的列表中。
When partitioning a nonunique , clustered index , the database engine by default adds any partitioning columns to the list of clustered index keys , if not already specified 在为非唯一的聚集索引分区时,如果未指定,则默认情况下,数据库引擎会将所有分区依据列都添加到聚集索引键的列表中。
This is because indexes , by default , are placed on the same filegroups as their underlying tables , and for a partitioned table in the same partition scheme that uses the same partitioning columns 这是因为在默认情况下,索引与其基础表放在同一文件组中,并且对应使用相同分区依据列的相同分区方案中的已分区表。
The drop existing clause does not rebuild the nonclustered indexes when the index definition has the same index name , key and partition columns , uniqueness attribute , and sort order as the original index 如果索引定义与原始索引具有相同的索引名称、键列和分区列、唯一性属性以及排序顺序,则drop _ existing子句不会重新生成非聚集索引。