MicroStrategy 7 Administrator Guide

C
O
N
C
E
P
T
S
5. The Object Server checks to see if there is a valid cache for the requested
object definition. If there is, it returns the object definition. Otherwise, it calls on
the Metadata Server to load the object definition from the metadata database. Then
it saves the object definition in its cache and returns the definition to the
Resolution Server.
6. Once it has all the necessary objects loaded, the Resolution Server returns the
job to the Job Executor. The Job Executor sends the job to the next step in the job’s
task list, SQL generation. The SQL Engine generates the SQL and passes the job
back to the Job Executor.
7. The Job Executor passes the job to the Query Engine, which submits the SQL
to the warehouse.
8. The Query Engine opens a connection to the warehouse and submits the SQL.
After the SQL is executed and data is returned the Query Engine passes the job
back to the Job Executor.
9. If the task list indicates that additional analytical processing or crosstabbing
is required, the Job Executor passes the job to the Analytical Engine, which
performs any additional calculations, crosstabs the data, and returns the job to the
Job Executor.
10. The Job Executor passes the job to the Result Sender which sends the
complete report results to the client and returns the job back to the Job Executor.
The Job Executor officially closes the job and the process ends.
Report execution with caching
If you have server caching turned on, a few additional steps are added to the basic
report execution:
Reply message
Job request
Client
Network Dispatcher
Result Sender
2a 10
Job Executor
Steps 3-9
22 Chapter 3 Job Processing