A partitioning key consists of one or more columns defined at table creation.
一个分区键由在表创建时定义的一个或多个列组成。
The partitioning key for each table in a tablespace that is associated with a database partition group determines if the tables are collocated.
在与一个数据库分区组相关联的表空间中，每个表的分区键可以确定表是否是并置的。
If the database designer has created a Primary partition Index on a table, queries should incorporate the partitioning column.
如果数据库设计者已在表上创建了主分区索引，那么查询应当与分区列结合。
This routine creates a copy of your existing table with the new partitioning key and loads it partially or fully with the data from the original table.
这个例程用新的分区键创建了现有表的一个副本并用来自原始表的数据对它进行部分或全部加载。
If database partitioning and range partitioning are used together, the rows in a table are first hashed across the database partitions and then range-partitioned within each database partition.
如果数据库分区和范围分区一同使用，那么表内的行首先会跨数据库分区做散列处理，然后再在每个数据库分区中执行范围分区。
It is useful when a table has a finite set of values for the fragment key (or partitioning key) and queries on the table have an equality predicate on the fragment key.
如果表格有一定数量的片段键(或者分区键)值，而且在片段键上有同等谓词的表格上查询时，它会很有用处。
You can store data in different partitions in the same table of a database using table partitioning.
您可以使用表分区将数据存储在同一个数据库表的不同分区中。
DB2 V9 introduced a table partitioning feature that can increase the potential size of a single table, and significantly reduce the maintenance effort required to manage very large databases.
DB 2V 9引入了一个表分区特性，它能够增加一个表的可能大小，同时能够显著减少管理大型数据库所需要的维护。
For TP, design decisions include selecting the column to use as the table partitioning key and number of partitions.
对于TP，设计决定包括选择用作表分区键的列和分区的数量。
Under index-controlled partitioning, the concepts of partitioned table, partitioning index and clustering were all intertwined.
对于索引控制的分区方法，分区的表、分区索引和群集这几个概念之间有点纠缠不清。
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.
然而，由于xml列不属于表分区键的一部分，任何唯一xml值索引必须创建为全局索引。
A new routine in DB2 9.7 named ADMIN_MOVE_TABLE allows you to automatically change the partitioning key of a table while keeping the table fully accessible for reads and writes.
在DB 2 9.7内有一个名为admin_move_table的新例程，可用来自动更改表的分区键，同时又能保持表对读写的完全可访问性。
However, the design of an MQT can be affected by which partitioning features are used on the base table.
然而，MQT的设计却可能受到基本表上使用的分区特性的影响。
TP will only benefit those queries that include the table partitioning key column.
TP只对那些包括表分区键列的查询有利。
The use of partitioning features on the base table does not need to take into account whether MQTs will be built upon this table.
基本表上分区特性的使用不需要考虑将来是否会在这个表上创建MQT。
The primary key and any unique index of the table must be a superset of the associated partitioning key.
表的主键和所有惟一索引都必须是相关分区键的超集。
This section discusses some observations about table partitioning that might not be very obvious and some things that we frequently get questions on.
本部分讨论关于表分区的一些不明显的观察值，以及一些常见的问题。
Whether a column should be used as table partitioning key for TP is not affected by whether that column is also used an MDC dimension and vice versa.
一个列是否被用作MD c维对于是否应该将它作为表分区键没有影响，反之亦然。
A partitioning key is defined on a table with the CREATE table statement.
分区键是在一个表上用CREATEtable语句定义的。
Usually the table partitioning key will be a time-based column.
通常表分区键是基于时间的列。
The columns used in this definition are referred to as the table partitioning key columns.
该定义中使用的列被称为表分区键列。
While the ADMIN_MOVE_TABLE procedure is running, the TPCD.PART table is fully accessible and the change to the partitioning key is transparent to the end users.
在 ADMIN_MOVE_TABLE过程运行时，TPCD.PART表是完全可访问的并且分区键的更改对于终端用户是透明的。
This article introduced the following DB2 table design features: table partitioning, MDC, DPF, and MQT.
本文介绍了以下DB2表设计特性：表分区、MDC、DPF和 MQT。
If the partitioning key for a table to be loaded in the database is an integer that has possible values between 1 and 500,000, the partitioning key is hashed to a partition number between 0 and 4 095.
如果数据库中所装载的表的分区键是1到500,000之间的整数，则分区键被散列到0到4 095之间的一个分区号。
If there is no partitioning key provided explicitly in the CREATE TABLE command, the following defaults are used.
如果在CREATETABLE命令内没有显式地提供分区键，那么就会使用如下的这些默认值。
Table partitioning offers the following.
表分区特性提供以下收益。
How to change partitioning keys while keeping the table fully accessible?
在保持表的可访问性的情况下如何更改分区键？
A typical design for a database with monthly roll-out based on sale_date, would be to use sale_date as the table partitioning key and create a separate partition for each month.
对于需要每月根据sale_date转出数据的数据库，一种典型的设计是使用sale_date作为表分区键，并为每个月创建一个单独的分区。
Choose the right initial partitioning key (PK) prior to defining and populating a table.
在定义和填充一个表之前，选择正确的初始分区键(PK)。
By default, 128 partitions are supported, although you can change the partition table size if the partitioning software supports such changes.
GPT默认支持128个分区，当然您也可以更改分区表的大小，如果您的分区软件支持这种更改的话。
应用推荐