SUMMARY
This article describes an issue where enabling database side normalization for a partitioned Intelligent Cube does not properly use the feature and provide expected performance benefits in Strategy 10.x.
DESCRIPTION
In Strategy 10.x when setting an Intelligent Cube to be both partitioned and to use database side normalization the expected performance benefit is not seen. The same amount of memory and time is needed as when publishing a non partitioned Intelligent Cube using database normalization.
CAUSE
This issue is a known issue in Strategy 10.x. Currently database normalization and partitioning cannot be used together with Intelligent Cubes.
ACTION
Currently this issue is still being reviewed for feasibiliy by our Technology team and is not scoped for any upcoming scheduled Strategy release.
WORKAROUND
The best current workaround is to use parallel fetch alongside partitioning with Iserver side normalization. Parallel fetch can help with data transfer similar to database side normalization and still allows for the benefits of partitioning. If however database side normalization provides a bigger impact that should be used instead of partitioning.
The Strategy Internal Reference Number for the issue discussed in this article is DE49759.
