Performance Tuning Guide > Tuning Siebel Remote for Performance > Tuning Siebel Remote Server Components >

Increasing Throughput for the Database Extract Component

You can increase throughput by running multiple concurrent instances of the Database Extract component. Each instance of the Database Extract component requires a temporary table. This table is called S_DOCK_INITM_N where N equals the value of the parameter TS Table Number (alias TSTableNum). TS Table Number specifies the number of the temporary table that serves the Database Extract component. For example, if TS Table Number equals 1, then temporary table 1 (S_DOCK_INITM_1) serves the instance of the Database Extract component that is currently executing.

By default, 48 temporary tables are available for use. If you require additional tables, you create them using Siebel Tools.

The recommended number of temporary tables to use depends on the database platform in use. For example:

• Microsoft SQL Server and IBM DB2 Universal Database

  Use one temporary table for each instance of the Database Extract component that you execute. For example, if you execute 11 instances of the Database Extract component, then use 11 temporary tables.

• Oracle Enterprise Server

  The number of temporary tables that you use depends on the size of the shared pool that this database server can access. If the size of the shared pool is less than 300 MB, it is recommended that you use one temporary table and execute one instance of the Database Extract component. If the size of the shared pool is greater than 600 MB, then using one temporary table for each instance of the Database Extract component may increase throughput.

For more information about the Database Extract component, see Siebel Remote and Replication Manager Administration Guide. For more information about performance issues for the Database Extract component, see Troubleshooting Steps 15 on Siebel SupportWeb.