Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Preparing for Implementation on the DB2 Host >

Estimating the Number of Database Objects You Need

The number of objects created in the Siebel Schema depends on which Siebel product line you purchase. This consequently determines how much space you must allocate, as illustrated in Table 8. It is up to you to determine which of the objects shipped might actually be required for your deployment, based on your business needs.

CAUTION:  You cannot drop unused tables; doing so would cause Siebel Systems to discontinue technical support of your deployment. If you need to drop unused, non-unique Siebel indexes on z/Series, contact Siebel Technical Support for assistance.

Siebel eBusiness Applications ships all table space and index schema definitions with the DEFINE NO option as the default. The DB2 DEFINE option specifies when the underlying data sets for a table space or index are created physically. Because the Siebel default is DEFINE NO, this means that no data sets are created until data is actually inserted into the table space.

NOTE:  DEFINE NO is only applicable to DB2-managed (STOGROUP) data sets and is ignored for user-managed (VCAT) data sets and for LOB table spaces.

Table 8.  Number of Siebel Database Objects by Product Line
Database Objects
Approximate Number of Objects
 
Horizontal
Siebel Industry Applications
Databases containing Siebel tables
18
31
Segmented table spaces containing Siebel tables
150, if grouped, and up to 2,095 if 1 table per table space
254, if grouped, or 2,997 if 1 table per table space
Tables
2,095
2,997
Indexes
10,836
20,727


 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003