因为只在新附加分区上构建这一本地索引，并需要非常有限的日志，所以与全局索引相比，SETINTEGRITY甚至明显变快了。
Since this local index build happens only on the newly attached partition and requires very limited logging, SET INTEGRITY is still significantly faster compared to global indexes.
以下例子阐明了如何在不含全局索引的表上应用分区级别reorg ？
The following examples illustrate partition-level REORG on a table that has no global indexes.
A：索引查找利用全局索引扫描，来确定对分区的引用是否存在。
A: With global index scans, the index look-up determines whether a reference to a partition exists.
然而，由于xml列不属于表分区键的一部分，任何唯一xml值索引必须创建为全局索引。
However, since XML columns cannot be part of the table partitioning key, any unique XML values index will have to be created as a global index.
在这样的语句中，术语“global ”仅仅是指索引对于多个TP数据分区来说是全局的。
In statements such as this, the term "global" merely means that indexes are global across TP data partitions.
如果已分区表包含任何xml列路径索引以外的其他全局索引，重组一个分区会导致整个表脱机。
Reorganizing a partition will put the entire table offline if the partitioned table has any global indexes besides XML column path indexes.
用户不能向全局范围分区索引中添加分区，因为最后一个分区总是以MAXVALUE 作为分区边界。
You cannot add a partition to a global index because the highest partition always has a partition bound of MAXVALUE .
用户不能移除全局索引中的最后一个分区。
不能使用带有位图类型索引的全局分区。该分区将被设置为默认值。
Cannot have global partition with bitmap type index. The partition will be set to default.
全局范围分区索引的最后一个分区必须使用MAXVALUE设置一个分区边界。
The highest partition of a global index must have a partition bound, all of whose values are MAXVALUE.
全局范围分区索引的最后一个分区必须使用MAXVALUE设置一个分区边界。
The highest partition of a global index must have a partition bound, all of whose values are MAXVALUE.
应用推荐