Improving report and cube performance against the data warehouse by using an attribute form caching cube
The data fetch time is often too high for reports and cubes that are executed against the data warehouse as most of the data transfer time (for example, network bandwidth) is spent in fetching text columns that are non-ID attribute forms.
To reduce data transfer time used for fetching non-ID attribute forms, you can use an attribute form caching Intelligent cube. Cache the attribute forms using this cube. When there is requirement to fetch non-ID attribute forms, the attribute form caching cube is used instead of database.
To learn more about attribute form caching cubes, see KB484994.
To use this functionality in Workstation, see Improve Report and Cube Performance Against the Data Warehouse by Using an Attribute Form Caching Cube.
- Your metadata must be upgraded to MicroStrategy 2021 or above to populate the new cube template.
- You must enable dynamic sourcing at the project level to access the attribute form caching cube.
To create an attribute form caching cube
In MicroStrategy Developer, select the Empty Attribute Form Caching Intelligent Cube template when creating a new Intelligent cube.
By default, there is a system hierarchy on the cube.
You can remove the system hierarchy and add your own attributes into the template and include specific attribute forms for caching.
To use an attribute form caching cube
To use an attribute form caching cube, you must enable dynamic sourcing at the project level.
If multiple attribute form caching cubes are available, only the latest published cube is used.
- In MicroStrategy Developer, go to Project Configuration > Intelligent Cubes > Enable Dynamic Sourcing.
Select Enable Dynamic Sourcing and Make Intelligent Cubes available for dynamic sourcing by default.
When executing a normal report or publishing an Intelligent cube that includes the cached attribute forms, the message, "This object dynamically sources attribute base form(s) from the following Intelligent Cube(s):xxx" appears in the SQL view. Only the ID form of the cached attributes are selected in the SQL statement.