Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Step 5. Define Foreign Keys

Step 5. Define Foreign Keys

Select the suggested table relationships that you want to use as foreign keys.
  1. In the
    View
    Constraints
    view of Enterprise Data Manager, right-click the schema that you ran the profiling job on and select
    View Suggested Table Relationships
    .
    A window appears that shows the suggested table relationships.
  2. Select the relationships that you want to define as foreign keys. You want to choose relationships that have a high inclusion percentage.
    In this example, the TICKET table is the driving table and the TICKET_NUMBER column is the primary key for the TICKET table. Therefore, the relationships that have the parent table as TICKET and the parent column as TICKET_NUMBER are selected. The following image shows the suggested table relationships with the relationships selected:
    The relationships with TICKET as the parent table and TICKET_NUMBER as the parent column are selected.
  3. Click
    Submit
    .
    A window appears that confirms Enterprise Data Manager created the table relationships successfully. Click
    OK
    to close the window.
  4. In the Enterprise Data Manager entity tree, select a table that you included in a foreign key relationship. In the right pane, select the Constraints tab.
    The Constraints tab displays a list of table relationships.
  5. In the Constraints tab, select the foreign key relationship that you created. Foreign keys have the Referential relationship type.
    In the lower right pane, you can view the relationship details, such as the child and parent table columns. The following image shows the foreign key relationship details between the TICKET and TICKET_COUPON tables:
    The relationship name is PROF_TICKET_COUPON_SAVE1, the type is Referential, and the constraint is enabled.
  6. You can create as many foreign key relationships as required. The foreign keys define the entity that you use to archive data.

0 COMMENTS

We’d like to hear from you!