Bookshelf v7.5: Capacity Planning

Siebel Server Installation Guide for Microsoft Windows > Creating the Microsoft SQL Server Database > Creating the Database >

Capacity Planning

One of the most important items to determine about your database is its overall size. Database size consists of the space required for system storage, temporary storage space, log files, and the like required by Microsoft SQL Server, as well as the space required for Siebel data and indexes.

The first of these factors will vary, primarily based on the total number and types of users supported. It is recommended that you consult the documentation provided by Microsoft for more information on these requirements.

The space required for Siebel data and indexes will vary depending on what Siebel functionality you will implement and the amount and nature of data supporting that functionality. At a minimum, Siebel 7 requires that you size your Microsoft SQL Server database to be a minimum of 1 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 applications (for example, 500 sales representatives and 75 sales managers).

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

Accounts

Activities

Contacts

Forecasts

Opportunities

Service Requests

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

Using standard sizing procedures for SQL Server, and using 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. This will determine the estimated data size for the largest entities.

You must add more 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.

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

Be certain to allow a margin of error in your total size calculation.

Be certain to factor growth rates into your total size calculation.

Allocating Sufficient MS SQL Server Database Log Space

You must place your log on a disk large enough to hold the log as it expands. It is recommended that you monitor the disk regularly for its level of utilization. Very large transactions may, for example, require at least 1 GB.