MSTR 9.0.1 (Release 2) and it’s New Features

MicroStrategy 9 Release 2 (9.0.1 products) is now available on the download site.

What are the new features in MSTR 9 R2 (9.0.1)

1) Jump Start Project

2)  MicroStrategy Health Center

1) JUMP-START PROJECT

                                    What is the Jump-Start Project?   

Jump-Start is a complete MicroStrategy project that comes with 7 dashboards and 30 reports and all the underlying metrics, filters, attributes, and dimensions.  All you have to do is add data and rewire.  It was designed with one purpose in mind – to help you develop a complete MicroStrategy Project FAST! 

                                     How does Jump-Start Work?  

MicroStrategy’s Jump-Start Project provides the standard building blocks of any project, attributes and facts, and uses those objects to create application objects such as metrics, filters, reports, enterprise documents, and dashboards.  Because a specific project has yet to be defined, all of these objects use generic names as placeholders.   You redefine/rewire the attributes and facts so that they work off your data tables, and due to the object oriented design of MicroStrategy, the data will be cascaded into the pre-built reports and dashboards automatically. With all this work prebuilt, the Jump-Start project delivers a complete BI project in a matter of a few hours

Manuals are available in MicroStrategy site.

2) MicroStrategy Health Center

MicroStrategy Health Center allows users to prevent, diagnose and fix problems in a MicroStrategy system.  It detects known problems and provides an immediate solution to many of them.  

Health Center can email a system administrator if it encounters a problem with the system. In cases where Health Center cannot fix a problem immediately, it enables users to bundle relevant system information, such as log files, into a diagnostic package and transmit the package to MicroStrategy Technical Support for review and troubleshooting. 

  • MicroStrategy Health Center can only operate on MicroStrategy 9.0.1.
  • By default, MicroStrategy Health Center is installed and turned off (not configured). To start configuring MicroStrategy Health Center, please see the tech note below:
    • TN32554 How to Configure a MicroStrategy Health Center System
  • If MicroStrategy Health Center is already configured, to learn more about what common tasks can be carried out, please see the tech note below:
    • TN32552 How to use MicroStrategy Health Center Console
  • For a List a Current System Checks:
    • TN32551  A List of System Checks for MicroStrategy Health Center
  • MicroStrategy is constantly extending the functionality of Health Center by developing new system checks and information collectors, and refining existing ones. To keep the Health Center System up to date:
    • TN32553 How to keep the Health Center System up to date

Source: MicroStrategy’s Technical Email

Free Reporting Suite has changed fate of MicroStrategy

I receive a lot of emails from all over the world who wish to learn MicroStrategy and some long lost friends have come asking about learning MicroStrategy. Also the curiosity of learning MicroStrategy have increased in some two quarter. This is based on my emails I receive, comments received on the blog,  my MicroStrategy forum, forum on Orkut and some other communities too. 6 months back big number of Fortune 100 companies were going down and MicroStrategy 9 seemed to have not big bang for MicroStrategy, Inc. But the FRT has simply changed the way MicroStrategy Inc ‘s future is going to take shape. Though it does mean drastic loss of revenue per license sold, but finally MicroStrategy Inc have realized they can’t continue being $$$ greedy for long. They have survived for 2 decades, but if they would have had remained same, they wouldn’t have been able to stay in BI market for long. I know the Fortune-100 companies will not let MicroStrategy Inc die as 90 out of them use MicroStrategy as the primary BI investment or only BI tool.

Coming back to fate change. I don’t see MicroStrategy Inc trying to capitalize on fresh availability of MicroStrategy professionals in job market. FRT has led to thousand of clients of seeing/trying MicroStrategy clients for the first time and realizing what were they missing for so many years. BO and Cognos are piece of crap in front of MSTR. They don’t match anything except the ease of development, but that leads to several other complexities in case of BO/Cognos too. I mean, metadata syncing.. never ever heard of that. :roll:

A bigger picture would become by Q1  2010. MicroStrategy World 2010 is due in a week and majority of sales lead would be getting closed by end of Q1 2010. I hope they are really doing good. (I do not consider myself good in doing anything other than MicroStrategy 😯 )

P.S. This is just thought that came in my mind. Blog topic doesn’t go with the blog post. :(

“Outer Join” in MicroStrategy

During the past few weeks, I was confronted with many interesting tasks of the MicroStrategy world. And once again I had to annoy me about the fact that there is no clever way to MicroStrategy, an outer join between the attributes to be generated.

In Menu Data / Data Options / Calculations / attribute – join method can be adjusted, although, as the connection is to be made between the attributes, but these settings will lead to a difficult to understand SQL, the unexpected also depending on the situation to a conclusion can lead (more) in one of the next post.

In addition to the modification of views, there is another common workaround, which is to create a dummy metric, which is defined for each combination of attributes.  This metric will be hidden in the OLAP area, or via formatting in the report. Example of such a metric would be a simple constant function Sum (0).

Such a dummy metrics produces the same result as if all the attributes of the template would be linked to a FULL OUTER JOIN.

But what if you want some attributes with a FULL OUTER JOIN, and then connect the other with LEFT OUTER JOIN?  A simple idea would be to modify the metric by means of dimensionality, namely, the LEFT OUTER JOIN attributes with the setting ignore add / None.

Great idea, but does not work!  From a no apparent reason, no metric dimensioned in MicroStrategy can be “conducting”, ie standing in a LEFT OUTER JOIN on the left side. Too bad!

The original article in German language can be read here.

Using a transformation to calculate 5 last values within one SQL query

Here is one of my recent interesting tasks:

Calculate some metrics only for the items that are in high demand. An item is “in high demand”, if its sales value were greater than the constant X in every of the last 5 months (including the current month).

Solution

First again setting of tasks:

An article A is valid in the month M as an article with large demand, if its Abverkäufe in everyone of the last 5 months (inclusive the current month) were larger a fixed constant X (e.g. was X = 100). We want to find and in a report represent as efficiently as possible all to such combination A and M (which we if necessary than a Metric filter to use later to be able).

Here my solution is using only one transformation. I see the advantage of this solution in the fact that only once the generally very large fact table one accesses.

For all examples I will use according to standard installed the project in my blog MicroStrategy Tutorial. Therefore you can my examples easily copy and try out. In addition it is possible to compare several solutions of a problem directly.

As I already betrayed, I use a transformation in my solution. Therefore a Transformations view must be defined as the first. The data source for the project „MicroStrategy Tutorial “is an ACCESS data base TUTORIAL_DATA_7200.mdb.

We put on the following View:

SELECT t1.MONTH_ID, t2.MONTH_ID AS PREV_MONTH_ID, DateDiff („m “, t2.MONTH_DATE, t1.MONTH_DATE) AS MONTH_DIFF
FROM LU_MONTH AS T1, LU_MONTH AS t2
WHERE (((DateDiff („m “, t2.MONTH_DATE, t1.MONTH_DATE)) Between 0 and 4))
ORDER BY t1.MONTH_ID, t2.MONTH_ID;

The VB-function DateDiff supplies here the number of full months, which lie between the handed over date values. The expenditure of the View looks then about in such a way:

Image 1

We designate the View „MONTH_TO_5_LAST_MONTHS “. Now the View in the Warehouse catalog is imported; subsequently, on the new logical table the following objects are defined:

Transformation “5 load Months “

Image 2

Attribute “Months Diff “

Month Diff

Month Diff

In addition the attribute form Month@ID should be extended automatically to the field MONTH_ID the new table:

Month@ID

Now we want to build a Metrik, which „a bit-map with 5 digits represents “to the form *****. Each asterisk corresponds thereby one month: the linkste asterisk refers to the month in the regarded report line, the next asterisk to the previous month (relative to the regarded report line), etc.

In place of each asterisk we want to indicate the indication „to X “, if the Abverkaufswert of the article were larger in the regarded report line in that asterisk position corresponding month 100. Otherwise we indicate in place of the asterisk the indication to O.

If thus for an article in the month the bit-map is indicated to 200804 „OXXOO , that means that this article had the Abverkaufswerte only in the months 200803 and 200802 more largely 100. According to the definition from setting of tasks such an article would not have large demand in the month 200804. “Only the combinations of the articles and months correspond to the large demand, for which the bit-map is calculated.

And here the definition of the Metriks is bit-map Sales > 100 in The load 5 Months:

Metric condition

The dimensionality and Konditionalität of the Metrik are not changed. Only the transformation „5 load Months “is assigned the Metrik.

The formula of the Metrik looks as follows:

ApplyAgg(„max(iif((#0 = 0 and #1 > 100), ‘X’, ‘O’)) & max(iif((#0 = 1 and #1 > 100), ‘X’, ‘O’)) &max(iif((#0 = 2 and #1 > 100), ‘X’, ‘O’)) & max(iif((#0 = 3 and #1 > 100), ‘X’, ‘O’)) & max(iif((#0 = 4 and #1 > 100), ‘X’, ‘O’))“; [Months Diff]@ID; [Units Sold])

Because of the function ApplyAgg one must enter the logic in VisualBasic syntax (iif for the konditionale examination and & for the Konkatenierung). Probably it would function however also without ApplyAgg function, with the MicroStrategy functions IF and Concat. Logical way should generate however MicroStrategy in this case a very similar Query.

Here is screen SHOT of a report, which uses the Metric bit-map Sales > 100 in The load 5 Months :

Final Report

The original article in German language can be read here.