Siebel Server Sync Guide > Configuring Siebel Server Sync >
Populating DB_LAST_UPD Columns
If your Siebel implementation uses an Oracle or DB2 UDB database, then SSSE performance optimization requires that you place data in the DB_LAST_UPD column of each of the Siebel tables listed in Table 12. These columns were added to the listed tables specifically for use by SSSE. When SSSE makes queries related to these new columns, Oracle and DB2 UDB database optimizer performance improves if the columns contain data.
Table 13. Database Tables and Indexes that Affect SSSE Performance
|
|
S_ACT_CONTACT |
S_ACT_CONTACT_M1(DB_LAST_UPD,ACTIVITY_ID) |
S_ACT_EMP |
S_ACT_EMP_M5(DB_LAST_UPD,ACTIVITY_ID) |
S_ADDR_ORG |
S_ADDR_ORG_M7(DB_LAST_UPD,ROW_ID) |
S_ADDR_PER |
S_ADDR_PER_M6(DB_LAST_UPD,ROW_ID) |
S_CONTACT |
S_CONTACT_M23(DB_LAST_UPD,PAR_ROW_ID) |
S_CONTACT_BU |
S_CONTACT_BU_M3(DB_LAST_UPD,CONTACT_ID) |
S_CONTACT_INFO |
S_CONTACT_INFO_M1(DB_LAST_UPD, SYNC_FLG,TARGET_PER_ID) |
S_EVT_ACT |
S_EVT_ACT_M12(DB_LAST_UPD,ROW_ID |
S_OPTY |
S_OPTY_M10(DB_LAST_UPD,ROW_ID) |
S_ORG_EXT |
S_ORG_EXT_M23(DB_LAST_UPD,PAR_ROW_ID) |
S_PARTY |
S_PARTY_M5(DB_LAST_UPD,ROW_ID) |
S_POSTN |
S_POSTN_M4(DB_LAST_UPD,PAR_ROW_ID) |
S_POSTN_CON |
S_POSTN_CON_M4(DB_LAST_UPD,CON_ID) |
S_PROJ |
S_PROJ_M9(DB_LAST_UPD,ROW_ID) |
S_SRV_REQ |
S_SRV_REQ_M12(DB_LAST_UPD,ROW_ID) |
S_USER |
S_USER_M3(DB_LAST_UPD,ROW_ID) |
The following procedure describes how to populate these columns with the recommended data. This is a task in Process of Configuring the Database for Optimum SSSE Performance. NOTE: It is recommended that you perform this task if your Siebel implementations uses Oracle or DB2 UDB databases. This task is not required if your Siebel implementation uses other database types.
To populate DB_LAST_UPD columns with data
- For each Siebel table that is listed in Table 12, use one of the following methods to place data in the DB_LAST_UPD column of at least some rows:
- Run a database script to copy the value of the LAST_UPD system field into the DB_LAST_UPD field of the same record, then update your database statistics.
- If you are working in a Test environment where contact, calendar, and to do records are being modified as part of testing, enable database triggers for a time period that is long enough to capture some changes in all of the tables listed in Table 12 (for example, perhaps one week), and then update your database statistics.
- After you have used a script or database triggers to populate the DB_LAST_UPD columns with data, update your database statistics and then modify your database optimizer so that it is forced to consider the DB_LAST_UPD indexes.
NOTE: It is not possible to force a Microsoft SQL Server database optimizer to consider DB_LAST_UPD indexes.
|