Table of Contents

Search

  1. Preface
  2. Introduction to Data Validation Option
  3. Repositories
  4. XML Data Source
  5. Tests for XML Data Sources
  6. Connections
  7. Expressions
  8. Table Pairs
  9. Tests for Table Pairs
  10. Single-Table Constraints
  11. Tests for Single-Table Constraints
  12. Examples of Tests from Spreadsheets
  13. SQL Views
  14. Lookup Views
  15. Join Views
  16. Aggregate Views
  17. Business Intelligence and Reporting Tools Reports
  18. Dashboards
  19. DVOCmd Command Line Program
  20. Troubleshooting
  21. Appendix A: Datatype Reference
  22. Appendix B: Reporting Views
  23. Appendix C: Metadata Import Syntax
  24. Appendix D: Jasper Reports
  25. Appendix E: Glossary

Data Validation Option User Guide

Data Validation Option User Guide

PowerCenter Cache for a Single-Table Constraint

PowerCenter Cache for a Single-Table Constraint

You can configure the total cache memory for a single-table constraint. If you enable caching, the PowerCenter Integration Service processes the Lookup, Joiner, Aggregator, and Sorter transformations faster. The PowerCenter Integration Service creates in-memory index and data caches to temporarily store data for each transformation while processing the transformation.
If you enable caching and run a test for a single-table constraint, the PowerCenter Integration Service divides the specified cache size among all Aggregator, Joiner, Lookup, and Sorter transformations in the underlying PowerCenter session. The PowerCenter Integration Service allocates cache memory based on the transformation requirements, such as the number of rows processed, number and types of tests, and precision and scale of the table columns.
For optimal session performance, configure the cache size so that the PowerCenter Integration Service processes each transformation in memory without paging to disk. Session performance decreases when the Integration Service pages to disk. To determine the required cache size for each transformation, review the cache size specified in the session log after the session completes.

0 COMMENTS

We’d like to hear from you!