- Intelligence server bus
- Intelligent Cubes server
- Communication layers for the metadata and data warehouse
- SQL Generation Engine
- Query Engine
- Analytical Engine
The query flow below describes the primary functions of each component.
MicroStrategy Intelligence Server query flow
- The MicroStrategy Intelligence Server receives a report request from any interface.
- The request is passed to the Intelligence Server bus, which coordinates all the tasks necessary to execute the report.
- Intelligence Server first checks the cache to see whether the report results are already there. The report results will already be in cache if another user or a schedule previously ran the report. If a cache exists, Intelligence Server skips directly to step 9.
- If no valid cache exists for the report, the Intelligence Server bus obtains the report definition and application objects from the metadata.
- The bus sends this information to the SQL Generation Engine. The SQL Generation Engine creates the optimized SQL, specific to the database being used. The SQL passes are then returned to the bus.
- The bus sends the SQL to the Query Engine. The Query Engine runs the SQL against the data warehouse and the report results are returned to the bus.
- The Intelligence Server bus invokes the Analytical Engine. Additional calculations are performed as necessary (when the calculation is unavailable in the database being used), and the Analytical Engine formats the results. The results are returned to the Intelligence Server bus.
- Depending on the analytical complexity of the report, the results might be passed back to the SQL Generation Engine for further processing by the database. Only MicroStrategy can provide this collaborative analysis with the database, resulting in forms of queries that can only be solved by MicroStrategy. In this case, steps 4–6 are repeated until the final report results are obtained. Finally, the formatted results are returned to the client communication layer.
- The Intelligence Server passes the formatted results back to the client.
I had this article for around 2+ years in my archives. Most probably this is an internal MicroStrategy document. If you are © owner and want me to pull this down, please post a comment. There is a link to post comment. I come to know about any comment on blog as soon as it happens. If you can help me with the origin/source of this document, please help me. This is the first post on this blog which is not straight from heart, but hope I don't deviate from it.
Hi Ashish. Thanks for the IS architecture.I am very new to MSTR.Was previously working with Oracle BI and Cognos. Your blog really helps me a lot.
ReplyDeleteCan you please tell us how and why Microstrategy is different and best from the other products?
ReplyDeleteI've answered your query as another post.
ReplyDelete