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

KB13247: What are the different options and what is their effect when selecting to Idle/resume a project in MicroStrategy Intelligence Server 9.x?


Community Admin

• Strategy


In Strategy Desktop 9.x under the Administration > System Administration > Project, if an administrator right-clicks on a loaded project, there is an option to Idle/Resume a project that has been loaded in Strategy Intelligence Server 9.x.
 
Depending on the option selected, Strategy Intelligence Server 9.x will do one of the following:
 
Request Idle
This option completes execution of all currently executing and queued jobs but rejects newly submitted jobs. This option is shown below:

ka04W000000OeWRQA0_0EM440000002Beb.jpeg

 
 
 
Execution Idle
This option cancels all currently executing jobs and places new jobs submitted after the project is in the Execution idle mode in the waiting job queue. These queued jobs are executed later after Strategy Intelligence Server 9.x resumes normal execution.
 
Strategy Intelligence Server 9.x continues to accept requests from clients for the project but does not submit any SQL to the database. The Execution Idle option is shown below:

ka04W000000OeWRQA0_0EM440000002Ben.jpeg

 
a) All jobs: All jobs are restricted from being executed by Intelligence Server. In most cases, these jobs are placed in the job queue and resubmitted when the project is allowed to resume job execution.
 
b) Warehouse jobs: Only jobs that require SQL to be submitted to the data warehouse are restricted from being executed by Intelligence Server. In most cases, these jobs are placed in the job queue and resumed when the project is allowed to resume job execution.
 
    Jobs that do not require SQL to be submitted to the data warehouse are executed as normal. For example, users can execute reports against an Intelligent Cube, run reports from a valid report cache, export to Excel, and so on. 
 
Full Idle
This option cancels execution of all executing jobs and queued jobs and rejects any newly submitted jobs. This option is shown below:

ka04W000000OeWRQA0_0EM440000002Bel.jpeg

 
For scheduled subscription jobs, if the project is put in Request Idle mode, they will be rejected and won't be resumed after the project is resumed.
 
If the project is set to Execution Idle mode, the subscription jobs will be put into job queue under some circumstances. On the all jobs level, all jobs are halted; while on the warehouse jobs level, subscriptions of reports and documents that is based on Intelligent Cube or valid cache can be executed.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017