KB20177: What are the different project modes and how are they used in MicroStrategy.

Project Modes
Each project in Strategy Intelligence Server can operate in one of several modes. Project modes allow for various system administration tasks to occur without interrupting Maintaining and Optimizing your System. The different modes are listed and explained below.
 
 
Loaded
A project in Loaded mode allows all job requests and executions as is expected of a fully functioning and accessible project. When a project is loaded, Intelligence Server accepts user requests from the clients for the project and submits jobs to the data warehouse for processing. The communication is open between the user, Intelligence Server, and the data warehouse.
 
 
Unloaded
A project in Unloaded mode is completely offline to users and removed from Intelligence Server memory. Nothing can be done in the project until it is loaded again.
Unloading a project can be helpful when an administrator has changed some project configuration settings which do not affect run-time execution and are to be applied to the project at a later time. The administrator can unload the project first, and then reload the project when it is time to apply the project configuration settings.
 
 
Request Idle
Request Idle mode helps to achieve a graceful shutdown of the project rather than modifying a project from Loaded mode directly to Full Idle mode. In this mode, Intelligence Server:
 

1. Stops accepting new user requests from the clients for the project.

• Completes jobs that are already being processed. If a user requested that results be sent to their History List, then the results are available in the user's inbox after the project is resumed.

Setting a project to Request Idle can be helpful to manage server load for projects on different clusters. For example, in a cluster with two nodes named Node1 and Node2, the administrator wants to redirect load temporarily to the project on Node2. The administrator must first set the project on Node1 to Request Idle. This allows existing requests to finish execution for the project on Node1, and then all new load is handled by the project on Node2.
 
 
Execution Idle
A project in Execution Idle mode is ideal for Intelligence Server maintenance because this mode restricts users in the project from running any job in Intelligence Server. In this mode, Intelligence Server:
 
 
 
 
 

1.  
   If a project is idled while Intelligence Server is in the process of fetching query results from the data warehouse for a job, that job is canceled instead of being placed in the job queue. When the project is resumed, an error message is placed in the user's History List. The user can click the message to resubmit the job request.
    
   
2. Stops executing all new and currently executing jobs and, in most cases, places them in the job queue. This includes jobs that require SQL to be submitted to the data warehouse, as well as jobs that are executed within Intelligence Server such as answering prompts.
3. Allows users to continue to request jobs, but execution is not allowed and the jobs are placed in the job queue. Jobs in the job queue are displayed as "Waiting for project" in the Job Monitor. When the project is resumed, Intelligence Server resumes executing the jobs in the job queue.

This mode allows you to perform maintenance tasks for the project. For example, you can still view the different project administration monitors, create reports, create attributes, and so on. However, tasks such as element browsing, exporting, and running reports that are not cached are not allowed.
 
 
Warehouse Execution Idle
A project in Warehouse Execution Idle mode is ideal for data warehouse maintenance because this mode restricts users in the project from running any SQL against the data warehouse. In this mode, Intelligence Server:
 
 
 
 
 
 
 

1.  
   If a project is idled while Intelligence Server is in the process of fetching query results from the data warehouse for a job, that job is canceled instead of being placed in the job queue. When the project is resumed, an error message is placed in the user's History List. The user can click the message to resubmit the job request.
    
   
2. Accepts new user requests from clients for the project but it does not submit any SQL to the data warehouse.
3. Stops any new or currently executing jobs that require SQL to be executed against the data warehouse and, in most cases, places them in the job queue. These jobs display as "Waiting for project" in the Job Monitor. When the project is resumed, Intelligence Server resumes executing the jobs in the job queue.
4. Completes any jobs that do not require SQL to be executed against the data warehouse.

This mode allows you to perform maintenance tasks on the data warehouse while users continue to access non-database dependent functionality. For example, users can run cached reports, but they cannot drill if that drilling requires additional SQL to be submitted to the data warehouse. Users can also export reports and documents in the project.
 
 
Full Idle
In this mode, Intelligence Server does not accept any new user requests and currently active requests are canceled.
 
When the project is resumed, Intelligence Server does not resubmit the canceled jobs and it places an error message in the user's History List. The user can click the message to resubmit the request.
 
This mode allows you to stop all Intelligence Server and data warehouse processing for a project. However, the project still remains in Intelligence Server memory.
 
 
Partial Idle
In this mode, Intelligence Server does not accept any new user requests and currently active requests that require SQL to be submitted to the data warehouse are queued until the project is resumed. All other currently active requests are completed.