I-server

Compatibility Issue (older Desktop clients against 921m I-Server)

MicroStrategy has been growing rapidly in the last few years and it’s easy to get carried away with the new versions & all these new features & overlooking how our environments are setup & the impact it might cause if not setup correctly.

Using MicroStrategy Scheduler

Scheduling Reports based on time and event

Reports can be schedule based on time or event using MicroStrategy scheduler.

Event based Scheduling: Lets assume we have a status table (name: load_status) in our warehouse which indicates an event of a fact table data load. We wanted to execute a few reports based on the event (when it turns '1').

Command manager script

SQL Engine & Query Engine

Differences between SQL Engine and Query Engine

SQL engine is a software component in the I-server which communicates with the metadata to generate the SQL. When a report is executed, the SQL engine interacts with the metadata to get the definitions of all the objects used in the report, to construct the SQL.

Any intermediate tables created in the SQL, generated by SQL engine will have tables name with around six alpha-numeric characters like "ZZMD00".

Project Source Creation/Modification (3-tier & 2-tier)

Project Source is the highest level object in MicroStrategy and is used to connect the client with I-server/metadata.

Connecting MSTR desktop to an existing I-server (3-tier) OR an existing metadata (2-tier)

Creating a new project source
Modifying an existing project source

Creating a new Project source:

All you need to know is the I-server name for 3-tier, DSN info of the metadata for 2-tier and login details. Once you have this information follow the below steps.

Scheduling (and alerting) an automatic re-start of I-server

Most of you might be familiar with this. I am describing a simple and easy way to schedule an automated I-server re-start (and alerting before the re-start) using command manager and Narrowcast service.

Lets assume we wanted to restart the I-server every thursday at about 8pm EST. A simple way of doing this is as described below.

Step 1: Create a command manager script with a .scp extension. Save the file as "i_server_restart.scp" and the file contains the following code-