EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB17468: What is MicroStrategy Intelligence Server 10.x behavior when two or more reports that would hit the same cache are submitted for execution simultaneously?


Community Admin

• Strategy


What is MicroStrategy Intelligence Server 10.x behavior when two or more reports that would hit the same cache are submitted for execution simultaneously?

The Strategy Intelligence Server provides functionality to allow multiple reports to hit the same cache. This can be achieved by creating multiple reports with the same base template and filter. Multiple users may also run the same report at a given time, each unique execution of a report is called a report instance. If different report executions have the same security credentials and are based on the same report or template and filter combination, and report caching is enabled, the Strategy Intelligence Server will let only one execution complete against the data warehouse. Other report jobs will appear with the status 'Waiting for cache' in the Job monitor as shown below:
 

ka04W000000OdVHQA0_0EM440000002BQD.jpeg

 
After the first report instance has finished execution, a cache for the report results will be created, and the remaining report executions waiting for the cache will retrieve the data from cache and complete execution. The cache created is shown below:
 

ka04W000000OdVHQA0_0EM440000002BQE.jpeg

 
Users should be aware that jobs pass through a parallel execution pipeline within the Intelligence Server. If multiple jobs are executed on the Intelligence Server instantaneously, it is possible for two or more jobs to simultaneously start executing against the warehouse, without appearing with the 'Waiting for cache' status.
​
Note: Report caching must be enabled for this behavior to be observed.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 21, 2017

Last Updated:

June 21, 2017