Table of Contents

Search

  1. Preface
  2. Introduction to Test Data Management
  3. Test Data Manager
  4. Projects
  5. Policies
  6. Data Discovery
  7. Creating a Data Subset
  8. Performing a Data Masking Operation
  9. Data Masking Techniques and Parameters
  10. Data Generation
  11. Data Generation Techniques and Parameters
  12. Working with Test Data Warehouse
  13. Analyzing Test Data with Data Coverage
  14. Plans and Workflows
  15. Monitor
  16. Reports
  17. ilmcmd
  18. tdwcmd
  19. tdwquery
  20. Data Type Reference
  21. Data Type Reference for Test Data Warehouse
  22. Glossary

Rules and Guidelines for Data Discovery Sources

Rules and Guidelines for Data Discovery Sources

Use the following rules and guidelines when you configure the data discovery sources:
  • You cannot run a profile for data discovery on nonrelational sources. However, you can use profiling in PowerCenter or Informatica Data Quality to create and run profiles and then export the results. You can import the results to the TDM repository with Test Data Manager. For information on how to run profiles in Informatica Data Quality and export them, see the Informatica
    Profile Guide
    .
  • You can import the results of profiles that use specific options in Informatica Data Quality.
    • You can view the results of profiles that use the Enterprise Discovery Profile and Profile options.
    • You can import the results of data discovery performed with mapplets created using simple regular expressions. You cannot import results if the mapplets use labeler, tokenizer, content set, or reference tables.
    • You can import data domains from the Model repository into TDM. TDM does not import the data pattern, metadata pattern, and preferred rules.
    • You can import and view domain discovery results of profiles run in the project. You can import the results of profiles created in folders within the project, but you cannot view the results in TDM.
  • A table that you import to the repository must have the same connection when you use it in a profile. If you use a different connection for the profile than you used to import the data source, you might receive unexpected results.
  • You cannot run a profile that contains two tables with the same name. For example, a project might have more than one EMPLOYEE table. Each EMPLOYEE table might have a different owner. You must create a separate profile for each EMPLOYEE table.
  • When you import source metadata of a MySQL source from the PowerCenter repository, PowerCenter converts the unique key constraints defined in the MySQL tables to primary key constraints. You see the unique key constraints defined in the MySQL tables as primary keys in the Columns tab on the
    Discover | Tables
    page.