Next Page When we run the reports created in MicroStrategy, they fetch the data from the warehouse to apply the calculations and generate a report. When multiple users request for the same report but with different range of values or different filter conditions, then the warehouse has to repeat similar calculations for each of the report and this hits the performance. To avoid this, MicroStrategy uses intelligent cubes, which is an object sitting in the middle layer between reports and the warehouse. The following diagram depicts the role of the intelligent cube. The Intelligent Cube is shared as a single in-memory copy, among the different reports created by many users.
|Published (Last):||28 November 2009|
|PDF File Size:||20.1 Mb|
|ePub File Size:||1.23 Mb|
|Price:||Free* [*Free Regsitration Required]|
Intelligent cube is a pre aggregated set of data stored in intelligent server memory and it will give very quick access to the data without hitting the data warehouse. It is very simple to create an intelligent cube, it is same like a report creation.
When we create and publish intelligent cube, it stores all the data in intelligent server memory as well as a copy in file system secondary storage area -Hard disk. View reports Intelligent Cubes Vs Cache: Cache: When you run the report then that single report result stored in a cache file and whenever if you run the same report then it looks for the cache with respect to the report objects and filter condition and then fetches data from the cache file and shows the result.
Ex: You have quarter wise report for year and respective cache file has been created when we execute the report for the first time.
New - Intelligent cube - Empty Intelligent Cube 2. Save Convert Report to Intelligent Cube: 1. Data - Intelligent cube Options - Convert to Intelligent cube 3. Save 1. View Filters are not allowed in the cube 3. Derived Metrics are not allowed in the cube Configure Intelligent cubes: 1.
Publish the intelligent cube is very simple, Run the intelligent cube 1. Publishing Intelligent cube will create a file in a physical memory a. It is not necessary that publishing intelligent cube should load the data in the memory b.
It is optional configuration 3. We can publish the intelligent cube with respect to data connection a. For each data connection, we need to publish the cube separately b. Each data connection it will create a separate file in the physical memory Load the data in the Memory 1.
Load data in the memory while publishing 2. When you run any report on top of this cube then it will load the data first in the memory and then access the data. Refresh Intelligent cube: We have two options to refresh the intelligent cube 1. It delete all the data stored in the cube file and then re run the complete cube against the DW , fetch the data and store in the file Incremental Refresh: In this case, it no need run the complete cube against the DW each time when we do cube refresh Here you need to define the incremental condition.
This would be the most common method of Incremental Refresh. Defining a report that returns that data and running in Delete mode would remove those rows from the Cube to give you a manageable size. This would probably only be used for patching data, say from an ETL error or source system fix.
If data was retroactively changed, you could update just that portion without having to reprocess the entire cube. Schedule Cube Refresh: We have schedule the cube refresh. This is normal concept of schedule and subscription 1. Time based.
MicroStrategy - Intelligent Cubes