Another configuration between PowerCenter and Data Validation Option is to have a many-to-one relationship, with Data Validation Option having a dedicated PowerCenter execution environment.

The following image illustrates this configuration:

In this scenario, there is no need to migrate Data Validation Option metadata across Data Validation Option repositories. Also, the dedicated PowerCenter environment for executing Data Validation Option jobs means there is no additional load placed on the regular development, test, and staging PowerCenter environments used for ETL. But, care must be taken when importing metadata from the multiple PowerCenter repositories to avoid metadata collision and to ensure that all metadata is kept updated from across all associated PowerCenter repositories. Also, note that connections from all associated PowerCenter repositories will be imported so there may be a very large number of connections to choose from for the Data Validation Option user.

Folders (or users) can be used in the Data Validation Option environment to separate the work (table pairs, single tables, views, and so on) associated with each of the development, test, and staging PowerCenter repositories.

For example, unit testing associated with development, regression testing associated with QA, integration testing associated with staging, and so on.