Table of Contents

Search

  1. Preface
  2. Introduction
  3. Working with Enterprise Data Manager
  4. Enterprise Data Manager
  5. ILM Repository Constraints
  6. Partition Exchange Purging
  7. APIs
  8. Smart Partitioning
  9. Salesforce Accelerator
  10. SAP Application Retirement Entities
  11. Import Formats for Constraints
  12. Glossary

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Discovery from Informatica Data Quality Profile Results

Discovery from Informatica Data Quality Profile Results

You can use Data Quality profile results to discover relationships between tables in source databases. Import the profile results to identify primary and foreign key constraints. Then, use the suggested relationships to create unique and referential constraint types for the table metadata in the ILM repository.
You can import profile results if you have the Data Discovery option.
The Enterprise Data Manager can discover table relationships from profile results that you export from Data Quality. You export profile results from the Informatica Developer to an XML file. The exported XML file includes references to the profile job in Data Quality, such as the profile definition, function definition, and the profile fields. The exported XML file does not contain all of the profiling results. The profiling results remain in the profiling warehouse. A connection to Data Quality is required to obtain the profiling results. Note that the Enterprise Data Manager imports the profile results, not the profile model.
The ILM engine uses the imported source metadata in the ILM repository to drive the import of the profile results. You initiate the discovery from the application version or from the application module levels of the source metadata. When you discover relationships at the application version level, the discovery occurs across all schemas in the application version. When you discover from the application module level, then the discovery occurs for that schema only.
If you retired the application, you may need to define constraints for imported source metadata after you retired and decommissioned the source database. You want to use the constraints to create entities for data discovery. You can generate profiles for the Data Vault instead of the source database.
When you discover relationships from Data Quality profile results, you initiate the discovery from the source metadata that you originally imported from the source database. You do not have to import metadata from the Data Vault.

0 COMMENTS

We’d like to hear from you!