This configuration option is conceptually the simplest, and involves setting up a Data Validation Option and a dedicated PowerCenter environment. The PowerCenter environment supplies all the needed metadata to Data Validation Option and is also the execution environment.

While conceptually simple, this configuration has both advantages and disadvantages. By having a dedicated PowerCenter environment, there is no load placed on the other PowerCenter environments used by developers, and so on. Given that all metadata is coming from a single PowerCenter repository, there is no risk of metadata collision.

The following image shows the relationship between Data Validation Option and a dedicated PowerCenter environment:

However, all metadata must be imported into the PowerCenter environment directly from the sources, or exported from other PC repositories and imported into this one. Additionally, all necessary connections must be created in the PowerCenter repository. Both connections and table metadata must be kept update to date in the PowerCenter repository.

The benefit of this configuration is that only those tables and connections that are needed for testing are exposed to testers. This connection may also use different database accounts (versus using normal database connections), and allows for different security to be applied to database connections as compared to what developers have in the PowerCenter repositories.