Managing Job Prioritization on MicroStrategy environment

Date: 07-09-2011
Author: Bit Software

One of the most important features to control in tuning your MicroStrategy environment is controlling Job Prioritization in the Intelligence Server. In the event that you have more concurrent jobs running than open slots on the database, queuing will occur. When a Job is in the Waiting status, that could be giving a very poor user experience. Fortunately, you do have some control to tell MicroStrategy which Jobs are more important than others. Today, I'll talk about how the Job Prioritization works, what options you have, and the Job Prioritization strategy that I use in my environments.

Job Prioritization occurs at the Database Instance and is a Governing setting for sending queries to the database. While there are Governing settings for the Intelligence Server to control concurrent jobs, those are system wide settings and are generally set very high (~100). The reason is that the Intelligence Server doesn't really have to do a lot of processing per job, at least compared to the amount the database has to do to retrieve the data.

Prioritization works by managing three slots: High, Medium and Low. By default, a job has Low priority. Jobs include not only Reports but also Prompt requests, and each Report on a Document counts as a separate job.

You can classify the priority of any given job in a number of ways, but the most direct is to setup the classification rules in the Job Prioritization Wizard. This can be found by opening the Database Instance for your Warehouse (Desktop -> Administration -> Configuration Objects -> Database Instances) and selecting the Job Prioritization tab, then clicking New. The wizard allows you to set global rules based on the type of job, the project it belongs to or the user requesting it.

by Bryan Brandow

(This article was first published on Bryan`s MicroStrategy Blog)



mai mult...