Category Archives: Administration

No projects were returned by this project source

If no projects are returned by MicroStrategy these could be reasons.

  1. Run License Manager and check that you have MicroStrategy Desktop and MicroStrategy Architect among Installed Products.
  2. You enabled anonymous authentication. The Guest user is a member of the Public group. By default, this user group does not have access to any projects in the project source. Revert back to Standard authentication, Administrator -> User Manager -> Public/Gest -> project Access. Set the access and privileges desired for the guest login.
  3. You are trying to connect to a Microsoft Access database with database authentication. Microsoft Access does not support database authentication.
  4. Similar to #2, LDAP user ID and password blank would lead to no project(s) when using LDAP authentication.

Sometimes a faulty installation is needed to be repaired.

But mostly, I have found the issue to be user not given right privileges, not connecting to right Project source or metadata corruption.

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)

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)

Keys and Levels in MicroStrategy

Table keys are the lowest level attributes in their respective hierarchies that are present in the logical table.

Fact entry levels are the lowest attribute levels at which a fact exists. The fact entry levels correspond to the lowest-level table key attributes for all the tables that define the fact.

A fact is only extended if a join does not exist between a fact table and the attribute to which the fact will extend to, i.e. the fact does not exist at the level of that attribute.

MicroStrategy SQL Generation Engine is sensitive to differences between its internal state and the states of metadata objects, there is a risk of SQL generation failures if schema modifications take place during normal user activity. In general, it is not recommended to perform schema updates during periods of normal or high usage. Schema changes should normally be reserved for periods of little to no user activity.