Designing an OLAP Cube for performance and scalability
(Doc ID 985550.1)
Last updated on OCTOBER 22, 2019
Applies to:Oracle OLAP - Version 10.2.0.4 and later
Information in this document applies to any platform.
Designing an OLAP cube logically and physically well is required for optimal performance - this note details how you can do this.
You must define the dimensions, levels and hierarchies properly and the measures for each cube. You must also physically design the cube properly.
This note covers how to design and store the cube optimally, using Analytic Workspace Manager (AWM), and covers areas such as compression, partitioning strategy and what levels to aggregate for optimal build and query performance, which need to be balanced for build window and user expectations.
Underlying relational design is not covered in this note. Also not covered in detail in this note, but which should also be considered are hardware configuration, database instance tuning, design of Materialized Views, and other special design tips mentioned.
This note is for the developer or DW architect who is tasked with designing OLAP cubes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document