Bookshelf v7.5: Capacity Planning

Siebel Server Installation Guide for UNIX > Creating the DB2 Universal Database for Windows and UNIX > Creating the Database >

Capacity Planning

One of the most important factors to determine about your database is its overall size. In your planning, you will need to allocate space for system storage, temporary tablespace, log files, and other system files required by DB2, and space for Siebel data and indexes. If you allocate too little space for your system, performance will be affected and, in extreme cases, the system itself may be halted. If you allocate too much, you waste space.

The space needed by DB2 will vary primarily based on the total number and types of users supported. It is recommended that you consult the IBM DB2 technical documentation for more information on these requirements.

The space required for Siebel data and indexes will vary depending on what Siebel functionality you implement and the amount and nature of data supported. At a minimum, Siebel 7 requires that you size your DB2 database to between 1 and
1.5 GB.

The process for making accurate database size calculations is a complex one involving many variables. The following guidelines will assist you in the process:

Determine the total number, and types, of users of Siebel eBusiness Applications (for example, 500 sales representatives and 75 sales managers).

Determine the Siebel functionality that you will implement and the entities required to support them. Typically, the largest entities are as follows:

Accounts

Activities

Contacts

Forecasts

Opportunities

Service Requests

Estimate the average number of entities per user (for example, 100 accounts per sales representative) and calculate an estimated total number of records per entity for your total user base.

Determine the estimated data sizes for the largest entities by using standard sizing procedures for your specific database, and Siebel Data Model Reference. Calculate the average record size per entity and multiply by the total number of records. Typically, these entities span multiple physical tables, all of which must be included in the row size calculation.

Add additional space for the storage of other Siebel data. A rough guideline for this additional amount would be one-half the storage required for these key entities.

NOTE: Indexes typically require approximately the same amount of space as data.

Allow for a margin of error in your total size calculation.

Factor growth rates into your total size calculation.

Create separate additional tablespaces and containers, preferably on separate disk devices, to better manage large or contentious tables and indexes.