Abstract
Supported Versions
Data Validation Option Best Practices
General Architecture
Data Validation Option and PowerCenter Configuration
- Setting Up Data Validation Option and PowerCenter Configuration
Architecture Configuration
- PowerCenter Repository Setup
Data Validation Option Client
- Data Validation Client Overview
Naming Conventions
- Suggested Naming Conventions
User Management
Performance
- Data Validation Option Performance in PowerCenter Environment
- Performance Testing
  - Methodology and Metrics Calculations

Data Validation Option Best Practices

Back Next

Execution PowerCenter Integration Service

When the target repository is added, a PowerCenter Integration Service is associated with it. The PowerCenter Integration Service will run all Data Validation Option jobs sent to the target repository. If the PowerCenter Integration Service also runs other jobs, for example, ETL jobs executed by developers, then the load on that service will increase with the new Data Validation Option jobs. In most cases, this is not a problem, but if the PowerCenter Integration Service is already running at capacity on the hardware, then additional CPU or memory resources will be needed, or a different PowerCenter Integration Service will need to be selected.

Rename Saved Search

Table of Contents

Data Validation Option Best Practices

Data Validation Option Best Practices

Execution PowerCenter Integration Service

Execution PowerCenter Integration Service