It is a database repository in which definitions of all MicroStrategy objects are kept. Metadata is the heart of MicroStrategy.
MicroStrategy metadata consists of project settings, MicroStrategy object definitions and data warehouse connection information.
Learn about MicroStrategy in this insightful blog now.
Firstly populate the metadata with project definition and schema objects, parameters and then make schema objects.
It allows the engine to do joins on unlike column names. If the user describe more than one expression for a given form, heterogeneous mapping will mechanically take place when tables and column names require it.
A compound attribute has its value resolute by an expression that join two or more columns in a database to make a new column.
Go through this MicroStrategy Tutorial to get a clear understanding of MicroStrategy.
An implicit attribute is a practical or same attribute that does not actually exist in the database because it is made at the application level.
It is Microstrategy way of conducting Composite Keys. To grip this case in Microstrategy we make this set of columns, containing composite keys, as joint child.
Based on similarities between attributes, hierarchies and their drilling design we can decide the drilling option.
Base formula is used to provide the formation of more complex metrics.
Smart metrics is used for calculating the compound matrices with the help of subtotal calculations for every constituent inside the compound metric.
Level metrics are modern metrics which are set to be evaluated at a particular attribute level.
Conditionality connects a filter to the metric calculation. This is not a mandatory option.
Using Object level security we can hide it.
Metric Formula Join Type is used for Compound Metrics and it determine how the various tables used in metric formula are joined.
Filter is used to limit data in a report.
View Filters are the situations that come into play before a particular result is showed to the user.
We can limit the number of elements using filter in a prompt.
Level prompts help us to identify the level of aggregation calculation of a metric.
It is used to develop conditional formatting for metric values.
Architect is the data modeling tool in MSTR.
With the help of Object Manager we can move objects across projects.
The part of the interface that allows users to recover the results of initially executed or scheduled reports.
By applying Security filters to the user we can provides row level security.
VLDB stands for Very Large Data Base Properties. It is a Microstrategy way of conducting database particular preferences while making the report SQL.
The command manager is used to save the text commands which can be executed as scripts.
Pass-through expressions let you deploy the syntactic constructs or special functions access that are not standard to MicroStrategy.
Instead of returning data from the data warehouse for a single report ,we can return sets of data from our data warehouse and save them directly to Microstrategy.
Excel, PDF, Flash, HTML are the different formats.
Controls are the objects that show the data, images, and shapes in a document.
A hyperlink interconnects text or an image in a document to a web page.
Prompts cannot be used OLAP Service Features: View Filters and Derived metrics cannot be used Consolidation and Custom Group
Take charge of your career by going through our professionally designed Microstrategy Certification Course now.
Your email address will not be published. Required fields are marked *