The most common setup is to have a one-to-one relationship between a Data Validation Option repository and a PowerCenter repository. For example, if a PowerCenter environment has development, test, and production repositories, then defining parallel development, test, and production Data Validation Option repositories makes sense.

This eliminates issues of metadata collision from multiple PowerCenter repositories. Also, any changes to table definitions or connections made in the PowerCenter environment can be imported directly into the Data Validation Option repository.

Additionally, this allows a simple user workflow with Data Validation Option across repositories, similar to that of PowerCenter. For example, a user can export or import metadata as needed across environments. Data Validation Option jobs will add load to each PowerCenter Integration Service in this setup.

The following image shows a typical one-to-one relationship where each Data Validation Option environment is associated with a single PowerCenter environment: