Bookshelf v7.7: Database Table Planning

In most implementations, the Siebel tables listed in Table 13 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 eBusiness Applications. These tables and indexes should be separated across devices. As a general rule, indexes should be in a different tablespace and, if possible, on different physical devices from the tables on which they are created.

Siebel tablespaces on DB2 UDB should be database-managed tablespaces (DMS) rather than system-managed tablespaces (SMS).

Table 13. Frequently Used and Largest Tables, Enterprise Customers
Table Names	Table Names	Table Names
`S_ACCNT_CHRCTR`	`S_DOCK_TXN_LOGT`	`S_OPTY_POSTN`
`S_ACCNT_CO_MSTR`	`S_DOCK_TXN_SET`	`S_OPTY_PROD`
`S_ACCNT_POSTN`	`S_DOCK_TXN_SETT`	`S_OPTY_TERR`
`S_ADDR_ORG`	`S_ESCL_ACTN_REQ`	`S_OPTY_POSTN`
`S_ADDR_PER`	`S_ESCL_LOG`	`S_ORG_EXT`
`S_ASSET`	`S_ESCL_REQ`	`S_ORG_TERR`
`S_CALL_LST_CON`	`S_EVT_ACT`	`S_PARTY`
`S_CON_CHRCTR`	`S_EXP_ITEM`	`S_PARTY_PER`
`S_CON_TERR`	`S_EXP_RPT`	`S_PARTY_REL`
`S_ACCNT_CHRCTR`	`S_EXP_RPT_APPR`	`S_PARTY_RPT_REL`
`S_CRSE_TSTRUN`	`S_IC_CALC`	`S_POSTN_CON`
`S_CRSE_TSTRUN_A`	`S_IC_CALC_IT`	`S_PROC_REQ`
`S_CS_RUN`	`S_IC_CMPNT_EARN`	`S_PROD_BASELINE`
`S_CS_RUN_ANSWR`	`S_IC_TXN`	`S_PROD_CONSUME`
`S_CTLGCAT_PATH`	`S_IC_TXN_IT`	`S_PROD_SHIPMENT`
`S_CYC_CNT_ASSET`	`S_IC_TXN_POSTN`	`S_PROD_TARGET`
`S_DNB_CON_MRC`	`S_INVC_ITM_DTL`	`S_QUOTE_ITEM`
`S_DNB_ORG`	`S_INVLOC_ROLLUP`	`S_SRM_REPLY`
`S_DNB_ORG_SIC`	`S_INVOICE`	`S_SRM_REQUEST`
`S_DNB_UPDATE`	`S_INVOICE_ITEM`	`S_SRM_REQ_PARAM`
`S_DOCK_INIT_ITEM`	`S_INV_LGR_ENTRY`	`S_SRV_REQ`
`S_DOCK_TXN_LOG`