Performance problems can occur when slicing an OLAP report in the SAS web clients and using a non-default hierarchy. This is because the code required to generate such a query requires a reaggregation of the data. Unlike the default hierarchy, slicing on even the default member of the non-default hierarchy requires an explicit request:

...other MDX statements...
WHERE ([SomeDimension].[My SecondHierarchy].defaultmember)

In order to generalize the logic for these types of requests, the query layer will create an aggregate of the values required. This reaggregation of the data is what will slow down the performance of your query.

If you know you are using specific member(s) for filtering purposes, you can create a custom data item that contains only the member(s). By placing this in your report instead of the data item provided by the map, you can improve the performance of the query.

Applying the latest hot fixes available to your environment might also help improve the performance in some cases.

Operating System and Release Information

A fix for this issue for Business Intelligence Query and Reporting 9.1.3 is available at: