Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Data Integrity and Capacity Planning > Database Table PlanningIn most implementations, the Siebel tables listed in Table 8 and their corresponding indexes are either the most commonly used, or they can be large in some enterprise deployments. For example, the tables S_EVT_ACT, S_CONTACT, and S_ORG_EXT are large in all enterprise-level deployments of Siebel Business Applications. These tables and indexes should be separated across devices. As a general rule, indexes should be in a different table space and, if possible, on different physical devices from the tables on which they are created. Siebel table spaces on an IBM DB2 database should be database-managed table spaces (DMS) rather than system-managed table spaces (SMS). |
Siebel Deployment Planning Guide | Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |