|Bookshelf Home | Contents | Index | PDF|
The default partitioning scheme is optimized for online activities from the Siebel Client. Storage control files are described in detail in Configuring the Database Layout.
Requirements for which Siebel tables to partition and how to partition them are determined by the use and the size of tables in your deployment. Careful planning, requirements analysis, and monitoring are necessary to achieve optimal partitioning. You also must monitor access path and data distribution, because changes might occur that require you to repartition table spaces.
Siebel Systems supports the use of any column as the partitioning key. Based on data access and data distribution, you can choose which column is best for partitioning in your implementation. Likewise, you should determine the number of partitions required in your implementation.
NOTE: When choosing a partitioning key for a Siebel table, follow all rules, restrictions, and concerns listed in IBM DB2 documentation. These considerations include data distribution and potential updates of partitioning keys.
The partitioning index is by definition the clustering index in DB2. Therefore, by optimizing your clustering order, you optimize performance. Make sure your partitioning strategy supports more than day-to-day online access to the Siebel tables. Consider processes such as EIM, Siebel Remote, Assignment Manager, and Workflow. See Strategies for Special Types of Tables.
|Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390|