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

Rules and Guidelines for Aggregate Views

Rules and Guidelines for Aggregate Views

Certain rules and guidelines apply when you create an aggregate view.
Consider the following rules and guidelines when you create an aggregate view:
  • Use sorted input to decrease the use of aggregate caches. Sorted input reduces the amount of data cached during the session and improves session performance.
  • Limit the number of input/output columns to reduce the amount of data the aggregate view stores in the data cache.
  • Filter the data before aggregating it.
  • If you create a column in the aggregate view, verify that the datatype, precision, and scale match the PowerCenter datatype, precision, and scale shown in the
    Column Definitions
    area. By default, the scale is 0.
  • You can either include single level functions, for example,
    SUM(QUANTITY)
    , or nested functions, for example,
    MAX(COUNT(ITEM))
    , in the output columns of an aggregate view. However, you cannot include both single level and nested functions in an aggregate view.