Chapter 12. Accessing DB2 dimensional data using BusinessObjects 581
Figure 12-39 With MQTS: DB2 explain result
The Access Plan Graph of the query is simple; the MQT MQT0000000001T02
has been used to retrieve all the information. The response time of
action is shorter in this case, thanks to the MQT.
The design of DB2 Cubes and MQTs is an iterative process. The review of the
BusinessObjects Universe allows you to improve your Cube/Cube Model and the
BusinessObjects query response time gives you indications on how you should
use DB2 Optimization Advisor to create the required MQTs.
582 DB2 Cube Views: A Primer
These are the five steps as shown in Figure 12-40 when deploying DB2 Cube
Views with BusinessObjects:
1. Run BusinessObjects Universal Metadata Bridge to create Universes from
DB2 Cubes/Cube Models.
2. Redesign DB2 Cube/Cube Model after universe review.
3. Run DB2 Optimization Advisor to take care of BusinessObjects report types.
4. Create new MQTs.
5. BusinessObjects reports leverage the query optimization by MQTs.
Figure 12-40 Iterative process
12.5.1 Optimization tips
To get full advantage of the DB2 Cube Views optimization, good practices could
be as follows:
Step 1: Identify which universes and which reports need to be optimized.
BusinessObjects Auditor allows you to monitor and optimize your Business
Intelligence deployment. With Auditor, you can answer questions such as: