Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Specifying the Primary Key Columns for Hard Delete Detection

When you use a function to create a primary key from multiple source columns, the hard delete detection process identifies the source columns by looking at the inputs to the function. The hard delete detection process runs on all the source columns that are inputs to the function.

If all the inputs to the function contribute to the primary key, you can skip this procedure.

If the inputs to the function include source columns that are not used in the primary key, create a list of the column names that contribute to the primary key. Add the list of columns to the C_REPOS_EXT_HARD_DEL_DETECT repository table. The hard delete detection process runs on the columns in the list.

Identify the columns in the landing table that the MDM Hub uses to create the primary key. Create a comma-separated list of the column names.

In an SQL tool, open the C_REPOS_EXT_HARD_DEL_DETECT repository table that you created when you configured hard delete detection.

If you did not add the HDD_LANDING_PKEY_COLUMNS column when you created the repository table, add the column. Set the column type to VARCHAR, and enter a length that can contain the comma-separated list of column names.

Add the comma-separated list of column names to the column.

When the stage job runs, a validation process verifies the list of column names. The validation process ignores spaces, removes duplicate column names, and verifies that the column names match the column names in the landing table.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Specifying the Primary Key Columns for Hard Delete Detection

Specifying the Primary Key Columns for Hard Delete Detection