Applying an Update Strategy

• Design a custom process to detect new and modified records.

• The process should be designed to load only changed data.

• If data is loaded without an incremental process, the previously loaded data will be updated again.

• Example logic in preconfigured SIL mappings:

1. A mapping looks up destination tables based on INTEGRATION_IDand DATASOURCE_NUM_ID.

2. If the combination exists, ROW_WIDis returned and the record is updated.

3. If the combination does not exist, lookup returns NULL and a record is inserted.

For loading new fact and dimension tables, design a custom process on the source side to detect the new and modified records. The SDE process should be designed to load only the changed data (new and modified). If the data is loaded without the incrementalprocess, the data that was previouslyloaded will be erroneously updated again.

For example, the logic in the preconfiguredSIL mappings looks up the destination tables based on the INTEGRATION_IDand DATASOURCE_NUM_IDand returns the ROW_WIDif the combination exists, in which case it updates the record. If the lookup returns NULL, it inserts the record instead. In some cases, last update date(s) stored in target tables are also compared in addition to the columns specified above to determine insert or update. Look at the similar mappings in the preconfiguredfolder for more details.