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

The Source – Tables


The first Schema Object to be created must be a MicroStrategy Table. The following is a quick reference table for this MicroStrategy Object:

This object is simply the logical representation of a table in the database (data warehouse). MicroStrategy imports into the object definition the table name, structure, columns, and data types. In addition, MicroStrategy assigns a value to the table based on the fields and Attributes mapped to it. It is important to mention that this number doesn't represent a measure of megabytes or number of rows but instead a conceptual value; this is why it is called the logical table size. This number is utilized by the MicroStrategy SQL Engine to choose which table should be used for the query when two tables are available to get the same data. MicroStrategy chooses the table with the smaller logical table size to optimize the query. Nevertheless, this number can be manipulated by the project Architect. An example of this scenario would be...