Book Image

MicroStrategy Quick Start Guide

By : Fernando Carlos Rivero Esqueda
Book Image

MicroStrategy Quick Start Guide

By: Fernando Carlos Rivero Esqueda

Overview of this book

MicroStrategy is an enterprise business intelligence application. It turns data into reports for making and executing key organization decisions. This book shows you how to implement Business Intelligence (BI) with MicroStrategy. It takes you from setting up and configuring MicroStrategy to security and administration. The book starts by detailing the different components of the MicroStrategy platform, and the key concepts of Metadata and Project Source. You will then install and configure MicroStrategy and lay down the foundations for building MicroStrategy BI solutions. By learning about objects and different object types, you will develop a strong understanding of the MicroStrategy Schema and Public Objects. With these MicroStrategy objects, you will enhance and scale your BI and Analytics solutions. Finally, you will learn about the administration, security, and monitoring of your BI solution.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Foreword
Contributors
Preface
Index

Grouping business context – Hierarchies


MicroStrategy Hierarchies are Schema Objects made of Attributes, which serve two main purposes:

  • Help to visualize and understand the relationships between the Attributes
  • Define paths for users to drill (drill maps and drill paths)

The following is a quick reference table for this MicroStrategy Object:

If you navigate to the Data Explorer, you will find the first Hierarchy that is created by default once the first Attribute is saved into the Project—System Hierarchy, as shown in the next screenshot:

System Hierarchy

The System Hierarchy will show all the Attributes in the project with their relationships and their Attribute elements. The Attribute elements are simply the data inside the lookup tables. It is important to note that the Attribute elements are not Objects but data instead.

The Architect can define user Hierarchies and make them available for final users as drill paths to perform data discovery and further analysis on Reports. In the next exercise...