Siebel Data Quality Administration Guide > Optimizing Siebel Data Quality Performance > Optimizing Matching Server Performance >

Database Table Considerations

The following are recommendations for achieving good performance:

  • Make sure there is sufficient space in the database tables used by the Matching Server.

    Use Table 26 and work with a database administrator to make sure there is sufficient space available for these tables.

    Table 26. Table Size Consideration
    Sizing Consideration


    These tables can include many more records than their corresponding base tables, depending on the key type used during the key generation stage, as follows:

    • Limited key type. Between two and four times more records
    • Standard key type. Up to an estimated six times more records


    After a full deduplication run, this table can contain five to six times the number of records in the three base tables combined.

    • If a Typical or Exhaustive search type is used, more records are inserted into the results table.
    • If a low match threshold is used, the matching process generates a larger number of records that are inserted into the results table.
  • For the DB2 platform, have your DBA use the REORG, REORGCHK, and RUNSTATS commands to improve performance during database maintenance.

    Access to S_PER_DEDUP_KEY, S_ORG_DEDUP_KEY, and S_PRSP_DEDUPKEY is on the DEDUP_KEY column, which is the only column of the table's _M1 index, therefore REORG uses this index. You must have current statistics for all tables associated with SDQ:


    so that you can use runstats commands to update statistics and improve performance.

  • For the DB2 platform, if performance seems degraded, run the following command on all tables associated with SDQ.

    runstats on table Siebel.Table_Name

    where Table_Name is the name of the table, for example, S_PER_DEDUP_KEY. If that command returns an error message, use this one instead:

    runstats on table Siebel.Table_Name with distribution indexes all

Siebel Data Quality Administration Guide Copyright © 2006, Oracle. All rights reserved.