IBM Cognos OLAB & BI
Analysis and reports based on specific cubes were running slow causing business users frustration and often complaints, which required IT to dedicated already scarce Cognos resources to satisfy these complaints.
Our analysis clearly indicated that the root of the problem were granularity level of the cubes, which were designed at transactional level to satisfy the needs of diverse user users significantly different by business function, causing cubes over-sizing and .exponential growth.
Our consultants modified cube design to remove transactional data from the cubes, designed and developed OLAP-Transactional drill-through reports to preserve familiar interface and existing and additional functionality, providing for both Business Unit Management and Operation Management reporting needs (sourced from the same cubes).
Reports performance was significantly improved, reducing load time to acceptable 15 sec, drill-down time to 5 sec. Most important results of this engagement were satisfied business users.
Another benefit – Cognos developers were relieved from maintenance and bug-fixing tasks and assigned to long-standing new development and requests, which previously were understaffed.
Cubes based reports were running slowly, although in Analysis Studio cubes performance was acceptable.
We have determined that MDX queries in the report where inefficient, another cause of slow performance was sheer number of similar calculations in the reports.
Our consultants recommended embedding common calculation routine into ETL. After this move was successfully implemented, reports MDX were redesigned according to IBM Cognos best practice recommendations.
Reports performance was significantly improved. The controversy between IT and various user groups (one group was mostly using Analysis, another - reports) was resolved to mutual satisfaction.