Table of Contents

Search

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

Enterprise Data Manager Guide

Enterprise Data Manager Guide

Step 1. Discover Table Relationships

Step 1. Discover Table Relationships

If you are not familiar with the data model of the source database, or if you do not want to maintain constraints manually, tools can help you analyze and discover table relationships in source databases. Use the tools to discover unique keys, primary keys, and foreign keys.
The following tools help you discover table relationships:
Discovery from ERwin data models
You can export files from ERwin data models of source databases. You discover relationships from the exported file. Use ERwin data models to identify unique, primary, and foreign key constraints. All of the information for the table discovery is in the exported file. You do not need to connect to the source database or the ERwin data model.
Discovery from Informatica Data Quality
You can connect to Data Quality to generate profiles for source databases. You discover relationships from the generated profiles. Use Data Quality to identify unique, primary, and foreign key constraints. A connection to the source database and Data Quality is required. If you retired the source database, you can connect to the Data Vault.
Discovery from Informatica Data Quality Profile Results
You can export profile results that are generated from Informatica Developer for source databases. You discover relationships from the exported profile results. Use the profile results to identify unique, primary, and foreign key constraints. A connection to the source database and Data Quality is required. If you retired the source database, you can connect to the Data Vault.
Discovery from CSV files
You can maintain data models of source databases in CSV files. You discover relationships from the CSV file. Use CSV files to identify primary and foreign key constraints. All of the information for the table discovery is in the CSV file. You do not need a connection to the source database.
The table relationship discovery process is driven from the source table metadata in the ILM repository. You initiate the discovery from the application version or from the application module levels of the source in the ILM repository. You choose the tables that you want to discover relationships for. When you discover table relationships at the application version level, you can discover relationships for tables across all schemas in the application version. When you discover table relationships from the application module level, you can discover relationships for tables within the schema.
When you discover table relationships, the ILM engine stores the suggested unique keys and table relationships in a profiling suggestion table in the ILM repository. All of the tools store the suggestions in the same table. If you discover table relationships multiple times or if you use multiple discovery tools, the system appends the suggestions to the profiling suggestion table. Because the tools store the results in the same table, use one tool to discover relationships from a schema. If you use multiple tools for the same schema, you might have difficulty interpreting the results.
After you view the suggestions and import the suggestions to create constraints, the ILM engine creates constraints for the corresponding table metadata in the ILM repository.
Although the discovery process identifies primary keys, when you import the suggested table relationships, the ILM engine creates the discovered primary keys as unique keys to avoid a potential database conflict. A conflict can occur if the table already contains a primary key.

0 COMMENTS

We’d like to hear from you!