Large OLAP hierarchies in Spotfire
When you are analyzing external cube data in Spotfire, you may encounter situations when a hierarchy filter takes a really long time to load, or even fails to load. This happens because the filter is populated in advance by reading the hierarchy outline from the cube. If the hierarchy is large (with many different levels and categories), the loading of all values at once may even cause problems for the cube data source itself.
About this task
Example: Configuring a cube hierarchy to be loaded on request
These steps describe how a cube hierarchy can be configured to be loaded on request, so that large OLAP hierarchies can be handled in Spotfire.
About this task
In this example, an embedded data connection to a Microsoft SQL Server Analysis Services cube is used as an example, but you can use the same steps to configure hierarchies from any cube data source.
Procedure
Results
Hierarchy filters loaded on request
When the connection has been configured to load values on request, the hierarchy filter will query the cube for the currently shown values only, and a new query is sent to the cube each time a new category is expanded.
About this task
Hierarchy filters from external cube sources will include an (All) check box and the setting that indicates that a category is only partially selected will be turned on by default. These settings can be switched off in the Filtering Scheme Properties dialog.