About Using Partitioning Indexes

Although the prepartitioned Siebel tables use table-controlled partitioning, you can also define partitioning indexes for Siebel tables that are not partitioned using PARTITION_COLUMN. For information on the role of PARTITION_COLUMN in partitioning tables, see Partitioning for Even Data Distribution.

You might want to define a partitioning index for a Siebel table-controlled partitioned table to improve query performance, if, for example, the table and its associated index are very large. You can partition the index provided it has the same columns and limit keys as the partitioning key values defined for the table.

Partitioning indexes are distinguished from partitioned indexes. A partitioning index must:

• Contain all of the columns from the partitioning key, at a minimum

  Note: A partitioning index can also contain additional columns, for example, columns required to support optimal clustering or performance enhancement.

• The columns must be in the same order

• The columns must have the same sort order

A partitioned index does not have the same partitioning key values as the key values on the table. Siebel CRM does not support partitioned indexes.

Partitioning indexes are defined in the storage control file templates for the prepartitioned Siebel base tables that do not use PARTITION_COLUMN. These tables are:

• S_CONTACT

• S_OPTY

• S_ORG_EXT

• EIM_ACCOUNT

• EIM_PROD_INT

• EIM_OPTY

• EIM_CONTACT

• EIM_SRV_REQ

• EIM_ACTIVITY

• EIM_DEFECT

• EIM_ASSET

• EIM_ACCNT_CUT

• EIM_FN_CONTACT1

• EIM_FN_ASSET

• EIM_FN_ASSET1

• EIM_FN_ASSET2

• EIM_FN_INSITM1

• EIM_FN_INSCLM1

• EIM_FN_ORGGRP

• EIM_ASSET_AT

• EIM_VHCL_SRV

For more information about the Siebel partitioned tables, see Prepartitioned Siebel Tables.