Bookshelf Home | Contents | Index | PDF |
Siebel Performance Tuning Guide > Tuning Siebel EIM > Siebel EIM Architecture Planning Requirements > Database Sizing GuidelinesThis topic is part of Siebel EIM Architecture Planning Requirements. One of the most important factors to determine about the database is its overall size. During the planning phase, you need to allocate space for system storage, rollback segments and containers, temporary storage space, log files, and other system files required by the relational database management system (RDBMS), as well as space for the Siebel application data and indexes. If you allocate too little space for the system, then performance will be affected and, in extreme cases, the system itself can be halted. If you allocate too much space, then it can cause inefficiency. The space needed by the database depends on the total number and types of supported users. It is recommended that you consult your vendor RDBMS technical documentation for more information on these requirements. The space required for Siebel data and indexes depends on the functionality being implemented and the amount and nature of data supporting this functionality. The process for making accurate database size calculations is a complex one involving many variables. Use the following guidelines:
|
Siebel Performance Tuning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |