Microstrategy Objects

MicroStrategy
Objects
MicroStrategy Objects
Configuration Objects
Configuration objects are MicroStrategy objects
which can be re used in multiple projects and they
appear in the system layer.
Ex: Database Instances, Users, Login ID's, Schedules
Public Objects
Objects that generate analytical data and are built
on other schema objects or public objects. Also
called as application objects.
Ex: Consolidation, Custom Groups, Drill Maps,
Reports, Documents, Filters, Prompts, Metrics,
Templates and Searches
Schema objects
Represent different pieces of the logical data

model, including logical data model
components such as facts, attributes, and
hierarchies.
Report designers can use these schema
objects to create application objects such as
metrics, filters, templates, and eventually
reports.
The default schema objects in the Schema
Objects folder are populated when you create a
new project.
MicroStrategy Schema Objects
Attributes
Facts
Functions and Operators
Hierarchies
Partition Mappings
Tables
Transformations
Attributes
Logical objects that relate descriptive

(non-fact) data stored in the data
warehouse to the MicroStrategy reporting
environment.
They provide context for reporting on
facts and define the level of detail at
which you want to analyze facts
Facts
Logical objects that relate

aggregatable data stored in the data
warehouse to the MicroStrategy
reporting environment.
They are usually numeric, and you
can aggregate them to different levels,
depending on your reporting needs.
Tables
Logical objects that correspond to physical
tables stored in the data warehouse that you
want to use in a MicroStrategy project.
Hierarchies
Logical objects that enable you to group
attributes to reflect their relationships or
provide convenient browsing and drilling
paths in the MicroStrategy reporting
environment.
Transformations
Schema objects you can create using
attributes in your projectare one of the many
MicroStrategy techniques used to perform time-
series analysis.
To calculate a variance or a growth
percentage such as last years revenue versus
this years revenue, it is very convenient to use
a transformation.
Transformations are often the most generic
approach and can be reused and applied to
other time-series analyses.
To use a transformation, a report designer
creates a metric and applies the transformation
to it.
Warehouse Partition Mapping
Warehouse Partition Mapping tables are
used for performance reason.
Example
For example, a fact table in the data warehouse
may have two columns: Sales and Years. If a report
is run with Sales for the Year = 1999, the query
engine will need to search through the entire table
for all the years, including 1999, to return the data.
Example(Contd...)
To improve efficiency, Partition Base Tables (PBT) can be
created to have Sales for particular years. Assuming that
there are 10 years worth of data in the database, 10
different partition base tables need to be created:-
PBT1: Sales for 1991 (Year=1991, Sales=$)
- PBT2: Sales for 1992 (Year=1992, Sales=$)
...
- PBT10: Sales for 2000A Warehouse Partition Mapping
Table (PMT) will then need to be created and will have:
Year PBTName
1991 PBT1
1992 PBT2
...
2000 PBT10
Example(Contd...)
The above PMT is going to tell the engine
which table to grab the data from for a
particular year. This means that when the
report is run for Sales for 1997, then the
query engine will first go to the Partition
Mapping Table and then find the correct
PBT corresponding to the year 1997.
Microstrategy Public Objects
Consolidations
Customs Groups
Documents
Drill Maps
Filters
Metrics
Prompts
Reports
Consolidations and custom groups
These are two special reporting features

that enable user to surpass basic reporting
functionality.
With consolidations, user can group
attribute elements to define "virtual"
attributes that enable users to analyze data
at levels that are not inherently available in
the business model.
With custom groups, users can create
reports that qualify on a row-by-row basis,
greatly enhancing the flexibility of report
design and the capabilities of report-level
qualifications.
Metric
A metric can be defined as a formula
applied on an other object (mainly facts, but
in few cases, it could be attributes of other
metrics).
A metric is an application object.
Types of Metrics
Simple Metric
Compound Metric
Conditional Metric
Transformation Metric
Smart metrics Derived Metric
Filter
Screens data in your data source to

determine whether the data should be
included in or excluded from the
calculations of the report results.
A filter is not required in a report,
although reports without filters are more
likely to return too much data to be
displayed effectively.
If a filter is added, it should make sense
with the objects already on the report.
Types of Filters
Attribute Qualification
Set Qualification
Shortcut Qualification
Prompt
It is a question the system presents

to a user when a report is executed.
How the user answers the question
determines what data is displayed on
the report when it is returned from
your data source.
Types of Prompts
Filter definition prompts

Object Prompts
Value Prompts
Thank You

Microstrategy Objects

Uploaded by

Copyright:

Available Formats

Microstrategy Objects

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Microstrategy Objects

Uploaded by

Copyright:

Available Formats

MicroStrategy

Represent different pieces of the logical data

Logical objects that relate descriptive

Logical objects that relate

These are two special reporting features

Screens data in your data source to

It is a question the system presents

Filter definition prompts

You might also like