In a multi-partition environment, you can have single-partition tables or multi-partitioned tables.
在多分区的环境中，可能具有单分区的表和多分区的表。
We demonstrate how to partition tables and migrate the database from ESE to a DPF logical node (scaling up) environment, offline.
我们将演示如何在脱机情况下划分数据库，以及如何将数据库从ese迁移到DPF逻辑节点(纵向扩展)环境。
When Symantec Ghost restores from an -id image, it relocates partitions to cylinder boundaries and adjusts partition tables accordingly.
当SymantecGhost从-id映像还原时，重新确定分区与柱面的边界并相应地调整分区表。
Summary: Roger E. Sanders explains why, where, when, and how to partition tables with DB2 for Linux, UNIX, and Windows—and shows how enhancements in DB2 9.7 make the process easier and faster.
简介：RogerE. Sanders解释使用DB2forLinux,UNIX,andWindows 进行表分区的原因、地点、时间和方式，并展示 DB2 9.7 中的增强如何使分区过程更简单快速。
Another strategy to improve the collocation of the join is to replicate smaller dimensional tables on each database partition.
改善合并并置的另一个策略是复制每个数据库分区上的较小的表。
The partitioning key for each table in a tablespace that is associated with a database partition group determines if the tables are collocated.
在与一个数据库分区组相关联的表空间中，每个表的分区键可以确定表是否是并置的。
The joined tables must be defined in the same database partition group.
被合并的表必须在相同的数据库分区组内定义。
Based on your application's business processes, you need to identify which tables to partition with the correct partitioning key.
您需要根据应用程序的业务流程，确定用正确的分区键划分哪些表。
Another advantage of using partitioned tables is that new data can be easily added to a table (as another data partition) while old or obsolete data can be easily removed and archived.
使用分区表的另一个优点是，可以轻松地在表中添加新数据(作为新的数据分区)，同时可以轻松地删除并存档老数据。
Database partition 0 is typically used for storing small, non-partitioned lookup tables.
数据库分区0通常用于存储小型的非分区的查找表。
IBMDEFAULTGROUP - default database partition group for the tablespaces containing the user tables.
IBMDEFAULTGROUP-用于包含用户表的表空间的默认数据库分区组。
Collocation between two joined tables in a query means that the matching rows of the two tables always reside in the same database partition.
一个查询内的两个合并表之间的并置意味着两个表的匹配行将总是处于相同的数据库分区内。
IBM TSOM USES range partitioning for event tables, so you can detach a partition, archive the detached partition on an external storage, or drop the detached partition.
IBMTSOM使用范围分区实现事件表，所以您可以分离一个分区，将分离的分区保存在一个外部存储上，或者删除所分离的分区。
To ensure fast recovery of the partition containing system catalog tables, avoid placing user tables on the same database partition.
为了确保包含系统编目表的分区能够快速恢复，应避免将用户表也放在那个数据库分区上。
This is accomplished by placing user tables in database partition groups that do not include the database partition in the IBMCATGROUP database partition group.
为此，可以将用户表放在不包括IBMCATGROUP数据库分区组中的数据库分区的数据库分区组中。
Media preference could be controlled at the partition (member level) for SQL partitioned tables, but the same was not possible for DDS-created physical files with multiple members.
对于已分区的sql表来说，媒介首选项可以在分区(成员)级别进行控制，但是对于具有多个成员的DDS创建的物理文件则无法实现这一点。
The catalog partition is the database partition where the catalog tables for the database are stored.
编目分区是存放数据库编目表的数据库分区。
Now, when creating partitioned tables, the partition boundaries are determined by the CREATE table statement instead of CREATE INDEX.
这时，当创建分区的表时，分区的边界由CREATEtable语句决定，而不是由CREATEindex语句决定。
The hypervisor converts a virtual address to a system-wide physical address using the global partition page tables.
Hypervisor使用全局分区页表将虚拟地址转换为系统范围的物理地址。
Since DB2 z/OS utilities run at either table space level or partition level for partitioned-table space, they would affect all tables present in the table space.
由于DB2z/OS实用程序在分区表空间的表空间级或分区级运行，所以它们会影响表空间中存在的所有表。
The results shown in these tables demonstrate that Domino 7 supports a significantly larger number of users in a single partition and also lowers CPU requirements per user.
这两个表中的结果展示了Domino7 可以在一个分区中支持大量的用户，并且每个用户对于CPU 的需求更低。
A user temporary tablespace, for declared temporary tables, can be created in IBMDEFAULTGROUP or any user-created database partition group, but not in IBMTEMPGROUP.
用于已声明的临时表的用户临时表空间可以在IBMDEFAULTGROUP或任何用户创建的数据库分区组中创建，但不能在IBMTEMPGROUP中创建。
When there are no dependent materialized query tables (MQT), the system initiates the second phase after the first phase (ALTER table DETACH PARTITION) commits.
当不存在依赖的物化查询表(MQT)时，系统在完成第一阶段(ALTERTABLEDETACHPARTITION)的提交后，启动第二阶段。
Distributing both tables by hashing on their join key (pdb_id) also ensures that all atom rows for a given PDBML document are stored in the same database partition as the PDBML document itself.
通过对上述两个表的连接键(pdb_id)进行散列处理来分布两个表也能确保给定pdbml文档中所有原子行均能作为本身的PDBML文档存储在相同的数据库分区中。
Each TP partition is a separate database object (unlike other tables which are a single database object).
每个TP分区是一个单独的数据库对象(不同于其他作为单个数据库对象的表)。
Staging tables (not supported by the load utility in multiple partition database environments).
分段表(在多分区数据库环境中装载实用程序不支持这种表)。
Small tables should be placed in single-partition database partition groups, except when you want to take advantage of collocation with a larger table.
除非想要利用与更大的表的并置，否则应该将小型的表放在单分区的数据库分区组中。
The catalog tables for partitioned databases reside only on the partition from which the CREATE database command was issued.
分区数据库的编目表只存储在发出CREATEDATABASE命令时所在的那个分区上。
You can specify compression for a tablespace, a table, or a partition. If specified at the tablespace level, then all tables created in that tablespace are compressed by default.
你可以为表空间，表或者一个分区指定压缩。如果指定为表空间基本，那么该表空间所有表创建后默认都启用压缩。
You can specify compression for a tablespace, a table, or a partition. If specified at the tablespace level, then all tables created in that tablespace are compressed by default.
你可以为表空间，表或者一个分区指定压缩。如果指定为表空间基本，那么该表空间所有表创建后默认都启用压缩。
应用推荐