Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Determining Whether Records Already Exist

Determining Whether Records Already Exist

During the load process,
Informatica MDM Hub
first checks to see whether the record has the same primary key as an existing record from the same source system. It compares each record in the staging table with records in the target table to determine whether it already exists in the target table.
What occurs next depends on the results of this comparison. 
Load Operation
Description
load insert
If a record in the staging table does not already exist in the target table, then
Informatica MDM Hub
inserts
that new record in the target table.
load update
If a record in the staging table already exists in the target table, then
Informatica MDM Hub
takes the appropriate action. A load update occurs if the target base object gets updated with data in a record from the staging table. The load process updates a record only if it has changed since the record was last supplied by the source system.
Load updates are governed by current
Informatica MDM Hub
configuration settings and characteristics of the data in each record in the staging table. For example, if Force Update is enabled, the records will be updated regardless of whether they have already been loaded.
During the load process, load updates are executed first, followed by load inserts.

0 COMMENTS

We’d like to hear from you!