Any update on how to integrate Microstrategy with DB2 workload management with DB2 10.5 BLU?


I found this document in which you tested the integration between the DB2 Workload Management and Microstrategy, it's really interesting.

I am interested in DB2 BLU that's using MSTR as fronted.... are you aware of any document who describe the integration between DB2 BLU and MSTR with example and testing done in a lab ?


Thanks for the interest in that (old!) paper :)

While dated, the essentials of this paper still hold true in DB2 and MicroStrategy today and the same approach can be used in DB2 10.5 as was used in DB2 9.5.

The key effort was to separate out the light-weight GUI-related queries from any concurrency controls on the heavier queries run in the main report bodies so that the direct user experience wasn't impacted while ensuring that the system did not become overloaded due to the heavy report work.

The interesting thing is that the default DB2 workload management configuration changed in DB2 10.5 such that it may no longer be necessary to do the explicit identification and assignment outlined in the paper. As of DB2 10.5, the default configuration now contains 2 service classes and a work action set to assign work to different places based on estimated cost. This configuration is active by default when one creates a database using the DB2_WORKLOAD=ANALYTICS setting or manually activates it.

This means that a DB2 10.5 database will emulate much of the same effect as the DB2 9.5 configuration recommended for MicroStrategy by imposing concurrency limits on the more costly items while letting the less impactful ones proceed. While this has not been tested explicitly with Microstrategy, it may provide the needed separation without additional changes.

Here is a diagram of what the default configuration looks like and you can find details about it in our documentation:


I hope this helps.

Recent Stories
Things to consider when considering Db2 Native Encryption

An old Db2 Easter Egg: Setting the default isolation value for dynamic SQL

Interpreting total_extended_latch_wait_time