Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Deployment Planning Guide > Data Integrity and Capacity Planning > Sizing the Database for a Siebel DeploymentAs with most client-server applications, the overall performance of Siebel Business Applications is largely dependent on the I/O performance of the database server. To promote optimal I/O performance, you must arrange the tables and indexes in the database across available disk devices in a way that evenly distributes the I/O load. The mechanism for distributing database objects varies by RDBMS, depending on the way storage space is allocated. Most databases can force a given object to be created on a specific disk. To verify which RDBMS products, versions, and patch levels are supported, see My Oracle Support Certifications. In your planning, you must allocate space for multiple purposes, including system storage space, undo or rollback space, temporary table space, and space for logs and system files, as well as space for Siebel data and indexes. If you allocate too little space for your system storage, then you reduce performance. If you allocate too much space, then you waste disk space. The space the RDBMS needs varies primarily based on the total number and types of users supported, as well as the transaction mix and rate. Consult the RDBMS vendor's documentation for more information about these requirements. The space required for Siebel data and indexes varies depending on what Siebel Business Applications functionality you implement and the amount and nature of data supporting that functionality. NOTE: The Siebel Servers in a Siebel Enterprise Server can connect to only one database. For example, you cannot configure both an Oracle Database and an IBM DB2 database for use by the same Siebel Enterprise Server. To determine the size of the database required for a Siebel deployment
|
![]() |
![]() ![]() |
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |