Showing posts with label Engine. Show all posts
Showing posts with label Engine. Show all posts

Monday, May 26, 2008

MicroStrategy Business Objects Cognos comparision

Single Metadata – Object definition is stored in a database (called metadata), How easy is changes to be integrated made from one interface to another.

64 Bit support – 32 bit system can’t address more than 4 GB of system space. All non-Windows OS are available in 64 bit for ages. Windows also got it in June 2005, but BI vendor should be able to support 64 bit OS.

Scalability – Any calculation performed in database is the best and fast and let very small load on the BI architecture. But not all BI vendors let it happen.

Reusable Objects – Make once use zillion times.

Objects Version Control – Ability to have different version of same (schema) objects.

WYSIWYG – Look and feel of what you created and finally how it looks.

Security – Object, User security.

Personalization – Single report but show different output to different users.

Manual fine-tuning SQL – Easily making changes to generated SQL.

Ease of SQL Generation – Make Schema object and system and forget about the right SQL generation.

MS Office integration – Run report directly from Word, Excel or Powerpoint.

(There is some bug with HTML parser on Blogger.com. Please scroll down for the comparison table. Do write into your comments. I'd update/add more information accordingly)
































































































































MicroStrategyBusiness ObjectsCognos
Single MetadataYesNoNo
64 Bit supportVery GoodGoodGood
ScalabilityExcellentGoodVery Good
Reusable bjectsExcellentGoodGood
Objects Version ControlVery BadExcellentVery Good
WYSIWYGVery GoodVery GoodVery Good
SecurityVery GoodGoodVery Good
PersonalizationVery GoodGoodBad
Manual fine-tuning SQLGoodExcellentExcellent
Ease of SQL generationExcellentVery GoodVery Good
MS Office integrationVery GoodBadGood
Learning CurveBadVery GoodVery Good
Number of Clients100004200023000
Number of Employees2000NA3500
Cost of License$$$$$$$$$$
Support Cost$$$$$$$$$$$
Average Pay (USD)##830007800079000
Job SecurityGoodExcellentVery Good
Cost of License$$$$$$$$$$
Support Cost$$$$$$$$$$$

## - indeed.com

Saturday, May 24, 2008

MicroStrategy Intelligence Server query flow

The main components of MicroStrategy Intelligence Server are:
  1. Intelligence server bus
  2. Intelligent Cubes server
  3. Communication layers for the metadata and data warehouse
  4. SQL Generation Engine
  5. Query Engine
  6. Analytical Engine

The query flow below describes the primary functions of each component.

MicroStrategy Intelligence Server query flow

  1. The MicroStrategy Intelligence Server receives a report request from any interface.
  2. The request is passed to the Intelligence Server bus, which coordinates all the tasks necessary to execute the report.
  3. 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.
  4. If no valid cache exists for the report, the Intelligence Server bus obtains the report definition and application objects from the metadata.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.