MicroStrategy 7 Administrator Guide

There are three possible priorities: high, medium and low. As the administrator,
you decide which variables are used to determine a job’s priority.
Defining job prioritizations
To define a job prioritization, you must determine which variables should be
considered in determining job priority. The possible variables are
• report cost
• group
• project
C
O
N
C
E
P
T
S
5XOHÃJob prioritizations are only used if the database instance for which they are
created represents a warehouse. You cannot apply job prioritizations to metadata
or statistics databases. In addition, job prioritizations are not applied to object or
element browsing jobs.
5HSRUWÃFRVW
Report cost is an arbitrary value you can assign to a particular report to help
determine priority. If you choose to use report cost as a priority variable, you must
define a set of priority groups based on report cost. For example:
• report cost between 0 and 400
• report cost between 401 and 800
• report cost between 801 and 1000
The set of cost groupings must cover all values from 0 to 1000. Once you
determine the cost groupings, you can set the report cost value on individual
reports.
For example, suppose you have created cost groupings as shown above, making
the first group high priority, the middle group medium priority and the last group
low priority. You notice that a particular report requires significantly more
processing time than most other reports. For this reason, you assign it a report cost
of 900. This way, the report will have a low priority based on report cost and will
be executed later when the system is not as busy.
Job prioritization 27