Preface
Part 1: Introduction
Part 2: Configuring Hub Console Tools
- Configuring Access to Hub Console Tools
- Implementing Custom Buttons in Hub Console Tools
Part 3: Building the Data Model
Part 4: Configuring the Data Flow
Part 5: Executing Informatica MDM Hub Processes
- Using Batch Jobs
- User Exits
Part 6: Configuring Application Access
Appendix A: MDM Hub Properties
Appendix B: Viewing Configuration Details
Appendix C: Row-level Locking
Appendix D: MDM Hub Logging
Appendix E: Table Partitioning
- Support for Table Partitioning
Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
Appendix G: Glossary
- Glossary of Terms

Configuration Guide

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

Back Next

Mapping the Primary Key

To identify a record in the source system, the MDM Hub requires a unique key, called a primary key. If the source system contains a column with unique keys, map that column from the landing table to the PKEY_SRC_OBJECT column in the staging table. If the source system does not contain unique keys, you can create unique keys by concatenating the values from multiple columns.

Map Columns Between a Landing Table and Staging Tables

Using a Single Column as the Primary Key

Using Multiple Columns as the Primary Key

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal