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

Hard Delete Detection Overview

Hard Delete Detection Overview

Source systems that populate base objects are continually updated, and records might be hard-deleted from these source systems. Hard-deleted records are records that are removed from the source system. The
MDM Hub
can detect the records that are hard-deleted in source systems, and it can reflect the change in the associated base objects.
The
MDM Hub
in the Oracle and Microsoft SQL Server environments can detect records that are hard-deleted in source systems.
The
MDM Hub
stage job compares all the records in the latest source system file against all the records in the previous landing table. The
MDM Hub
detects the records that are missing in the latest source system and flags them as hard deletes for a full load. The
MDM Hub
then reinserts the column values for the deleted records into the landing table along with a delete flag and optionally the end date. Finally the
MDM Hub
updates the associated base object.
The
MDM Hub
does not detect the records that are missing in the latest source system file for incremental or transactional load. You must create a hard delete detection table in the repository table to configure hard deletes. When the
MDM Hub
detects hard deletes, it inserts the number of records flagged as deleted, into the job metric table. You implement hard delete detection as Java user exits that are part of the stage process.

0 COMMENTS

We’d like to hear from you!