The different types of components used in Micro Strategy .
Source
systems
Source
system refers to any system or file that captures or holds data of interest.
This data is eventually analyzed in report format to determine answers to
business-related questions.
The source system is the originating
point of the data. For example, if you use your ATM card to conduct a
transaction, the ATM is the point of transaction. It is the place where the
data is gathered. In this example, the ATM gathers the information about how
many dollars or Rupees you deposited or withdrew from your account. The data is
then written to a source system that is the large database behind the ATMs.
Deposits, withdrawals, sales transactions, inventory depletion, or
replenishment are referred to as transaction processing. The source system
records the transaction. Transaction processing data is usually stored in
databases or mainframes for storage retrieval.
Project
Source
Project
Source is the highest level object in Micro Strategy and is used to connect the
client with I-server/metadata.
- A project source is the pointer towards a Micro Strategy metadata or a Micro Strategy Intelligence server.
- One Project Source can have one or more than one projects.
- Project Source should be connected to Metadata.
- Project should be connected to Data Mart or Warehouse from where data is actually residing for analysis.
Project
Project generally is the intersection point of the Data
Warehouse, metadata repository and user community. Project consists of objects
like attributes, facts, reports, template, filter, consolidation etc.
Multiple Project Connectivity and
Layout.
Metadata
The database
repository where definitions of all Micro Strategy objects are stored. Metadata
could be hosted on most databases. In simple words, Metadata could be
considered as the heart of Micro Strategy environment.
Once
you have a data warehouse populated with all the information your business
needs to succeed, how do you retrieve the information from the database
correctly and in the least amount of time?
The
metadata contains information that facilitates the transfer of data between the
data warehouse and the Micro Strategy application. It stores the object
definitions and the information about the data warehouse, including its
structure. Micro Strategy uses the metadata to translate user requests into SQL
queries and to translate the SQL queries back into Micro Strategy objects, such
as reports.
Metadata
is a relational database with a predefined structure that consists of 23 empty
tables known as metadata shell. You can store any number of projects within the
same metadata. Micro Strategy metadata
contains data warehouse connection information, project settings and micro
strategy object definitions.
The
three types of objects that are stored in the metadata are
·
Application Objects
·
Configuration Objects
·
Schema Objects
Application
objects
The
report designer creates the application objects necessary to run reports.
Application objects, which are developed in Micro Strategy Desktop and Web, are
the building blocks for reports and documents. These application objects
include reports, report templates, filters, metrics, prompts, drill map, custom
group and consolidation.
Configuration
objects
Administrative
and connectivity-related objects, also called configuration objects, are
managed in Micro Strategy Server Administrator by an administrator role.
Examples of configuration objects include users, groups, server definitions,
and so on.
Schema
objects
Schema
objects are created usually by a project designer. Schema objects relate the
information in the logical data model and physical warehouse schema to the Micro
Strategy environment. These objects are developed in Micro Strategy Architect,
which can be accessed from Micro Strategy Desktop. The schema objects are Facts, attributes, and
hierarchies, transformation and so on.
Comments
Microstrategy Training
Microstrategy Online Training