My First MicroStrategy Product Limitation! - Projects with Partition Mapping not generating Optimized Report SQL

Hi All,

Is been a while since I have updated the blog! But this time its about my first MicroStrategy Product Limitation!

For some reason MicroStrategy Projects until v9.5.0 implemented with Partition Mapping do not generate optimized report SQL’s on certain reporting scenarios.
In one of our project environments we have projects implemented with and without Partition Mapping feature. We use Partition Mapping feature basically to overcome split DWH architecture.

Please refer the link for info. The issue was reproducible in v9.4.1 and v9.5.0 project environments. The attached document is reproduced from Customer Analysis Module.

It would be great if we could get a resolution for this! Happy Exploration.

Multi-Tenant MicroStrategy Project Implementation.

Hi All,

Today we are going to discuss about an implementation which I had lived for a few years. Its nothing but setting up Multi-Tenant Architecture in MicroStrategy.

Project Scenario:

Say you are based out of  a product based software services company and you have multiple customers of the same business domain. And you have a dedicated business datawarehouse for each customer and also indeed you have one MicroStrategy project for each customer as well!

And it so happens that there is a customer who keeps asking for lots of requirements... very innovative and so on! However the same kind of requirements aren't even being thought about by other customers.

In such cases your BI Projects aren't been well utilized by your customers or the customers are not well advised on how to use the product that effectively.

Or else few of the customers are asking for the same project functionality as your premier customer has asked for!

In this case you might end up deploying the same project objects for multiple customers since multiple customers use their own MicroStrategy project! Which could be quite cumbersome in administrative effort and project management.

Proposed Solution:

One of the best and easiest proposed solution is to have a single project and make it hit multiple datawarehouses based on the customer's login! Something like if Customer A logs in and runs the reports the reports hit the Customer A's datawarehouse and if Customer B logs in and runs the reports the reports hit the Customer B's datawarehouse and so on...

Implementation Details:

Now what we do now is to have one single project and make the project hit multiple datawarehouse databases based on user's login.

MicroStrategy has a unique feature called Connection mapping where you can easily create a single project and and make it hit multiple datawarehouse databases.

To know more about this you can check out the below technical note from MicroStrategy.

TN20740: What is Connection Mapping and how is it configured in MicroStrategy Desktop 8.x

TN45331: Is there any hard limit on the amount of connection mappings to be implemented in MicroStrategy 9.x?

If you are in need to make a report in a single project to hit multiple database instances then you might need to choose freeform SQL approach.

TN39932: Is it possible to map different reports within the same 9.2.1 project to data warehouses of different types using connection mapping?