|Bookshelf Home | Contents | Index | PDF|
Partitioning table spaces on DB2 allows tables to be spread across multiple physical partitions based on a partitioning key, a partitioning index, and a set of key value ranges for each partition. Using partitioned table spaces increases the maximum size of a table and improves the manageability of large tables.
Any table, including any of the high-volume tables listed in Table 8, can be partitioned during the installation or upgrade process. You can define partitioned table spaces and key ranges for Siebel tables during or after installation, based on your business requirements. For a complete list of prepartitioned Siebel tables, see About Prepartitioned Siebel Tables.
You can choose to partition tables yourself by following Siebel guidelines, or you can take advantage of the default partitioning scheme that Siebel Systems developed, based on Siebel customer experience using the Siebel data model with DB2 UDB for z/OS and OS/390. If you use the Siebel default partitions, you can either accept them as-is, or you can reconfigure them to suit your requirements.
When a table is created on a partitioned table space, the table is assigned a partitioning key that is composed of one or more columns. Value ranges are assigned to each partition based on value ranges within the partitioning key. The value ranges determine which partition a particular row is assigned to.
The partitioning index specifies the key values that determine how data is partitioned. You can divide a large table such as S_ORG_EXT (which holds a list of new accounts) to store records of names beginning with letters A-L in one partition and records of names beginning with letters M-Z in another partition, as shown in Figure 2. The partitioning index defines the key ranges for the partitioning column. A key range must be specified for each partition.
|Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390|