The relative locations of dimensions in an outline can affect performance times :
Indeed, although they contain the same dimensions, the outline examples below :
are different. See meeting_the_needs_of_both_calculation_and_retrieval at the end of the article.
The structure defined in the Essbase - Outline (Database Outline) determines how data is stored in the database.
To optimize attribute calculation and retrieval performance, consider the following design tips :
To optimize attribute calculation and retrieval performance, consider the following :
To maximize attribute retrieval performance, use any of the following techniques:
Use the following topics to understand performance optimization basics.
To optimize query performance, use the following guidelines when you design an outline:
The outline below is designed for optimum query performance:
To optimize Essbase - Calculations performance, order the sparse dimensions in the outline by their number of members, starting with the dimension that contains the fewest.
See Designing for Calculation Performance.
The outline in the Figure below is designed for optimum calculation performance:
To determine the best outline sequence for a situation, prioritize the data retrieval requirements of the users against the time needed to run calculations on the database. How often do you expect to update and recalculate the database? What is the nature of user queries? What is the expected volume of user queries?
A possible workaround is initially to position the dimensions in the outline to optimize calculation. After you run the calculations, you can manually resequence the dimensions to optimize retrieval. When you save the outline after you reposition its dimensions, choose to restructure the database by index only. Before you run calculations again, resequence the dimensions in the outline to optimize calculation.