1. Deployment Planning Guide
  2. Database Table Planning

Database Table Planning

In most enterprise deployments, the following Siebel tables, and their corresponding indexes, are the most commonly used tables or are very large.

For example, the tables S_EVT_ACT, S_CONTACT, and S_ORG_EXT are large in all enterprise-level deployments of Siebel CRM. Separate these tables and indexes across devices.

As a general rule, put indexes in a different table space and, if possible, on different physical devices from the tables on which they are created.

For Siebel table spaces on an IBM DB2 database, use database-managed table spaces (DMS) rather than system-managed table spaces (SMS).

  • S_ACCNT_CHRCTR

  • S_ACCNT_CO_MSTR

  • S_ACCNT_POSTN

  • S_ADDR_ORG

  • S_ADDR_PER

  • S_ASSET

  • S_CALL_LST_CON

  • S_CON_CHRCTR

  • S_CON_TERR

  • S_CRSE_TSTRUN

  • S_CRSE_TSTRUN_A

  • S_CS_RUN

  • S_CS_RUN_ANSWR

  • S_CTLGCAT_PATH

  • S_CYC_CNT_ASSET

  • S_DNB_CON_MRC

  • S_DNB_ORG

  • S_DNB_ORG_SIC

  • S_DNB_UPDATE

  • S_DOCK_INIT_ITEM

  • S_DOCK_TXN_LOG

  • S_DOCK_TXN_LOGT

  • S_DOCK_TXN_SET

  • S_DOCK_TXN_SETT

  • S_ESCL_ACTN_REQ

  • S_ESCL_LOG

  • S_ESCL_REQ

  • S_EVT_ACT

  • S_EXP_ITEM

  • S_EXP_RPT

  • S_EXP_RPT_APPR

  • S_IC_CALC

  • S_IC_CALC_IT

  • S_IC_CMPNT_EARN

  • S_IC_TXN

  • S_IC_TXN_IT

  • S_IC_TXN_POSTN

  • S_INVC_ITM_DTL

  • S_INVLOC_ROLLUP

  • S_INVOICE

  • S_INVOICE_ITEM

  • S_INV_LGR_ENTRY

  • S_OPTY_POSTN

  • S_OPTY_PROD

  • S_OPTY_TERR

  • S_ORG_EXT

  • S_ORG_TERR

  • S_PARTY

  • S_PARTY_PER

  • S_PARTY_REL

  • S_PARTY_RPT_REL

  • S_POSTN_CON

  • S_PROC_REQ

  • S_PROD_BASELINE

  • S_PROD_CONSUME

  • S_PROD_SHIPMENT

  • S_PROD_TARGET

  • S_QUOTE_ITEM

  • S_SRM_REPLY

  • S_SRM_REQUEST

  • S_SRM_REQ_PARAM

  • S_SRV_REQ