Lite Optimization
Is a maintenance process similar to the BW Info Cube performance maintenance tasks of index rebuild, statistics rebuilds, and compression.
This process deletes the info cube indexes and moves records from the F to the E fact tables.
This process compresses/collapses the records with the same key
Additional zero suppression is possible (manually adjusted in process chain)
Updates the info cube statistics
There is no set recommendation as to the frequency, however it is generally recommended that these (index/statistics) tasks be executed after the load process to provide satisfactory performance for reporting and input schedule updates.
From 1508929 “There is no rule of thumb for how often to run optimizations. The need can vary depending on the characteristics of your hardware environment and your application.”
As best practice:
When new application sets and applications are created run a Full Optimization.
Lite Optimization doesn’t take the system offline, and can be scheduled during normal business activity (e.g. after a data load)
Full Optimization need the system to be offline so they should be run at down-time periods – for example after a month-end close.
Full Optimization
This process essentially rebuilds the application in its entirety. The process creates a new application and copies the data to the new application.
This process is a RESTRUCTURING of the BPC application data model
How does the system determine if a full optimization is necessary?
The algorithm looks at the size of the dimensions and the dimension members. If the dimension tables have <20% size of the fact table and as many line item dimensions are used, then the system will give a message “Optimization not required at this time”.
The full optimization logic is as follows (ref. SAP 1551154):
If the InfoCube needs restructuring – do it, then perform lite optimization
If not, perform a lite optimization
Why does the infocube technical name change with the Full Optimization?
