Category Archives: MicroStrategy

Free full-day BI classes by MicroStrategy

MicroStrategy is imparting training about “reporting, analysis, and monitoring in an enterprise BI application” specifically designed for “business users and budget owners” in various conutires starting 16th Dec.

If you don’t have a MicroStrategy Account, click here for creation of account. You will have to use only and only official office email address for account access.

Schedule for various countries/cities is here.

Click on suitable date and follow the wizard and you are done.

Warehouse Partition Mapping Table in MicroStrategy

To add and set up a Partition Mapping Table in MicroStrategy:

Step 1: Create the Partition Mapping Table (PMT). Views are not recommended since they defeat the purpose of partitioning and the performance will be hampered instead of improved. Usually the PBTs hold the same structure as the original base fact table.

This table must be created with the following structure:

The ATTRIBUTE_ID column name must match the column name on the partitioned base tables. This column contains the values of the attributes at which the tables are partitioned. Attribute ID(s) used to define the partitioning (partition keys). In addition, the PMT must contain a column named ‘PBTNAME’ containing the names of each of the partitioned base tables.
For Example, if the partition level is at Year, this column will be named ‘Year_id’ and contain values such as: 1998, 1999 and 2000.
The PBTNAME column name cannot be changed. This column contains the names of the partitioned base tables. PBTNAME = Partitioned Base Table Name.

Step 2: Add this table to MicroStrategy using Warehouse Catalog. It will be added as a partition mapping table, the icon will change and the number of partitions will be shown in parenthesis. Also, all the corresponding partitions are removed from the list of available tables. The partitions function as a unit; they cannot be deselected individually. Update Schema.

Note: If a prefix is needed to access the PMTs, it has to be included into the mapping table when populating it in WH Catalog.

Step 3: Go to the Partition Mappings folder under Schema Objects. The PMT appears in the right window. Right-click on the table and select edit. Click on the ‘Add’ button and select the attribute that marks the level of partitioning. Update Schema.

NOTE: (1) The PBTNAME in the Partition Mapping Table (PMT) should be unique. Otherwise, double counting may occur.(2) A PMT is needed for each fact table to be partitioned. (3) A normalized partition base table (PBT) saves database space but it is not recommended if performance is a key issue. The MicroStrategy Engine always applies filters on the partitioned base table queries even if it the filter is a partitioning key.

Clustering in MicroStrategy

Clustering is a popular strategy in which two or more servers/machines are configured to provide common services in a unified manner such that they behave like a single server. Each machine in the cluster is called a node. Even though it may sound very hi-fi, Clustering is one of the simplest thing in MicroStrategy. It aims for Load balancing as well as fail-over. One can cluster Intelligence server running on differ OS. eg, AIX, UX, Solaris, RH Ent Linux provided following condition are met.

  1. All MicroStrategy Intelligence Servers MUST point to the same metadata
  2. All MicroStrategy Intelligence Servers MUST have the projects in the same state. (i.e., if Node A has Project A in a ‘Loaded’ state, then Node B must also have Project A in a ‘Loaded’ state).
  3. From each machine where I-server is installed, one should be able to browse the folders for Cache and History List. (This is aachieved by Samba on Unix Environment)

MicroStrategy Custom Groups by Sushil Muzumdar

Look at following video on YouTube.

This is crazy to see what we’ve got done from 3i on YouTube. As video is off poor quality, let me tell you what is it. Currently there is no option to create Custom Group in MicroStrategy Web. This MicroStrategy 8.1.1 Web SDK customization made it possible. But wait! let me tell you something about this. We (my employer) were the first and probably only buyer of this. 3i employee Sushil (happens to be uploader of this video too) was the man behind this request (web CG) that some (of employer’s) client were asking for long.

About this application, this is not even fully made. This guy simply disappeared when he was wanted to fix the bugs. It doesn’t provide the option to set the level (none, report, custom) for a filter based on Metric, so that option is still not exposed to clients. Person who did QA of this application (she declared everything Pass) was fired. Sushil, we are facing the heat of your half hearted application. Specially we feel bad cause my employer paid from nose for this highly unstable application. Because of this we had to almost remade this application by someone else. You specifically didn’t provide any code documentation.

This CG customization runs into a problem every now and then. Last but not least, this works only and only in 8.1.1 and up and is not forward complaint to MicroStrategy 9.0, to be released soon. I don’t know if being forward complaint was something looked at during planning phase. BTW, MicroStrategy 9.0 provides in-memory CGs. ASAIK, as per licensing condition, he can not re-sell it and he is trying to sell it. You may land in soup for this.

Migrating a 2 tier project source to a 3 tier source

Technically, you don’t really require anything to make a 2 tier, just configure it using configuration manager (your access file). 2 Tier connection is also possible for a Oracle, SQL Server, or any other database.

There are two ways one can migrate a 2 tier (access) based project to Excel.

1. Project duplicate using Project duplication wizard or Object manager.
2. Import the access database into your relational database (Using ETL)