A cache is the stored results of a report query that has already been executed. When the report is executed again, the system can quickly access the cache to display report data, rather than putting a load on the system to re-run the request to the data source.
Generally, frequently requested reports are cached because future requests for the same reports return data faster if the report has been cached. The execution time is quicker because cached reports do not need to run against the data source. In a cache, results from your data source are stored and can be used by new job requests that require the same data.
Caching is a useful strategy your administrator can use to reduce demands on your database and improve the speed of MicroStrategy’s reporting performance. However, cached data is not always the most up-to-date, because it has not been run through your data source since the cache was created.
You can get new data for a report that has been cached, by deleting the report’s cache before you execute the report. Deleting the report’s cache forces the report to be executed through your data source again, thus returning the most recent data from your data source. You must have administrative privileges to delete a report cache.
I will explain in detail in the coming sessions about the types of caches available in MicroStrategy.
Have a Good Day!!