Data Discovery Sources
You can run profiles for data discovery on relational sources.
You can run profiles for data discovery on the following sources:
- •Oracle
- •Microsoft SQL Server
- •IBM DB2
- •Sybase
- •Teradata
Use ODBC to connect to Sybase and Teradata sources.
You can run data domain profiles on Hive and HDFS 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.
- - To view the profile results for Hadoop, you import the profile results from the Developer client with the Enterprise Discovery Profile option.
- - 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.