Microstrategy Training

WHY MICROSTRATEGY

Proven Success in the Market High Performance &Availability Integrated Server Architecture Supports Data Mining Ease of Use Cost Effective Capable of Complex Analysis Scalable in terms of Users as well as database Open Architecture Very good e CRM tools with a solid Foundation of BI tools Compatible with almost all different databases best with SMP.MPP Personalization in all levels Caching is well utilized at all levels Some Metadata properties can be modified

1 Million people use Microstrategy Every Day to take better business decisions.

20 out of Top 30 Global retailers use Microstrategy . Mcdonald’s,metroAG,JCPenny,Target 12 out of Top 20 Commercial Banks (Barclays ,Wells Fargo,AMEX)

4 out of Top 6 Global Mail Delivery Services (FedEx ,United Postal Service)

10 out of Top 10 Global Telecommunications ( at&t Telestra,verizon.vodaphone,O2)

8 out of Top 10 Manufacturing Companies (Honda, Toshiba,ABB)

5 out of 7 Online Information Sites (Yahoo, face book, ebay,paypal)

12 out of the top 15 U.S. Federal Government cabinet-level departments

ARCHITECTURE

Departmental Deployment Scenario

100 Web Users

MicroStrategy Desktop

MicroStrategy Architect

MicroStrategy Web MicroStrategy Office

2 Users

1 User

10 Microsoft Office Users

MicroStrategy Intelligence ServerMicroStrategy OLAP ServicesMicroStrategy Report Services

MicroStrategy Narrowcast Server

100 Email, File/Print Server Users

Mid-Size Enterprise Deployment Scenario

1000 Web Users



MicroStrategy Web MicroStrategy Office

20 Users

50 Microsoft® Office Users


2000 Email, File/Print Server Users

MicroStrategy Administrator 5 Users


5 Users

Enterprise Deployment Scenario


5000 Web Users



MicroStrategy Office

250 Microsoft Office Users


10,000 Email, File/Print Server Users

MicroStrategy Administrator 5 Users

10000 Portal Users

Portal Server MicroStrategy Web

50 Users

5 Users

Microstrategy Base Products

Microstrategy Desktop : Enables all the functionality for Report Design and Development

Microstrategy Intelligent Server : means for implementing virtually all Microstrategy system capabilities

Microstrategy Web :Includes all the functionality useful for report display and manipulation

Microstrategy Desktop

Source Systems

DataWarehouse

MicroStrategy Applications

MicroStrategy Administrator



MicroStrategy Web


MicroStrategy BI Developer Kit

MicroStrategy Report Services


MicroStrategy OLAP Services

Query Engine

Analytical Engine

SQL Engine

Microstrategy Intelligent Server

Components like Administration Database Connectivity Job Processing Security Caching Scheduling Clustering Web Administration

Microstrategy Web

Can create reports, templates but not filters and hence Agent is required.

Enables end User’s to create their own style of Reports and Dashboards .

Customization using HTML or Java is supported.

Microstrategy Narrowcast Server

Can be used as any of the following, Output to Email, Telephone, Pager, WAP, Fax, Voice Mail,

Mobile Phone Personalized Information Proactive Customer contact One to One Marketing Active Information portal

Narrowcast Server Contd.. Narrowcast Server Console has 4 components

Services Schedules Subscriptions Styles

Same governing options as in Server

Microstrategy Desktop’s Functionality

Create/Upgrade/Delete Project Data warehouse Browsing Project Schema modification Attribute and fact creation System-Wide Searching Create/Delete/Modify Objects View the properties of the objects Run Reports Rename objects Specify Desktop Preferences

OBJECTS

Schema Objects Application Objects Configuration Objects

Schema Objects Attributes Facts Hierarchies Tables Partition Mapping Functions and Operators Transformations

Application Objects Filters Metrics Reports Drill maps Prompts Templates Search Objects Auto styles Documents Custom GroupsConsolidations

Configaration Objects

System Administration Project,Cluster Nodes,Scheduled maintenance

System Monitors Jobs,user connections,database conn,cache

Configuration Managers DB Instances,Schedules,Security Roles, Subscriptions

Delivery Mangers Transmitters,Devices,Contact

Connection Modes for a Project Source

Direct Mode - 2 Tier connection mode connects the project to the metadata via an ODBC

Server Mode - 3 Tier connection mode connects the project to the metadata via the Intelligent Server

Project Source Manager

Create a new Project Source Modify Existing Project Source Delete Existing Project Source Is connected to Metadata

Confidential & Proprietary

OLTP vs. OLAP

•Aligned by Application

•Typically Not Integrated

•Recent or Current Data

•Transactions (read/write/update)

•Fairly Consistent

•Aligned by Dimension

•Must Be Integrated

•Historical Data

•Analysis (read-only)*

•Spiked or Uneven

OLTP OLAP

Alignment:

Integration:

History:

Data Access:

Usage:

WarehouseChallenges

Batch

Maintenance

Tuning

Confidential & Proprietary 32

Basic Business Intelligence Architecture

ETL

MicroStrategyMetadata

Source SystemsData

Warehouse

MicroStrategy Applications

MicroStrategy Administrator



MicroStrategy Web


MicroStrategy BI Developer Kit

MicroStrategy Report Services


MicroStrategy OLAP Services

Query Engine

Analytical Engine

SQL Engine

33

ROLAP Architecture of Microstrategy

MicrostrategyMetadata

Data Warehouse/ Data Mart

Intelligence Server


34

Core of Microstrategy BI Platform

•SQL Engine and Query Engine – Work together to generate and send optimized SQL to the RDBMS

•Analytical Engine – Adds analytical power to greatly extend the capability of the system beyond what the RDBMS provides. (Also responsible for MOLAP functionality)

•Server Components – Responsible for all aspects of report generation, element retrieval, object retrieval and so on.


35

2 – Tier Architecture(Direct Mode)

ODBCto Metadata

ODBCto DW



Desktop


36

3 – Tier Architecture(Server Mode)

ODBCto Metadata

ODBCto DW



DesktopMicrostrategy

Intelligent Server


37

Multi – Tier Architecture(Server Mode)

ODBCto Metadata

ODBCto DW



Microstrategy Desktop

MicrostrategyIntelligent Server

LDAPServer

Web Server

Web Browser


38

Multiple Project Connectivity and Layout

Project 1

Project 2

Metadata

Intelligence Server

(MD DSN + Login)

Project Source

Project 1 Project 2

WH Database Instance

WH Database Instance

WH DSN

WH Login

WH DSN

WH Login

WH Database WH Database

WH Database Connection

WH Database Connection


39

The Microstrategy Desktop


INSTALLATION OF MICROSTRATEGY

40

Dependent Platforms:

•WINDOWS, UNIX/LINUX.

Requirements Of Microstrategy Web:

•Three-tier archeitecture.

•Microsoft Internet Information Services 5.0 or higher.


Procedure for installation of Microstrategy:

41

•Choosing typical installation method or custom installation method.

•Selection of path for installation.

•Selecting the components to be installed.

•Configuring of Microstrategy installation.


42

Steps for Project Creation and Configuration

•Create metadata database

•Establish connections to the metadata database and the data warehouse

•Create the project using the Project Creation Assistant

•Configure additional schema-level settings


Path to navigate Configuration wizard

43Confidential & Proprietary

Select Metadata Repository & Statistics tables & click Next


2 tier Project Source Creation


Select an Access database for metadata & click next


The configuration wizard automatically select the path for the script optimized to the database


Once the path are given click finish


Click Ok to the metadata configuration message


Once the configuration is successful we will get the message


3 tier Project Source CreationUncheck 2 tier project source creation options


Browse the access file for metadata & click next


The configuration wizard automatically select the path for the script


Once the path are shown click finish


Select Setup Micro strategy Intelligence server & click next


Select the DSN to connect to the metadata, if we want to select a new DSN select the new tab


We can give user name & password to connect to the metadata repository


We can create an new server definition in this wizard


It will prompt a message for confirmation to use this server default


We have to provide the port number that has to used by intelligence server


Once the wizard is completed click finish


It will prompt an message to stop IS for the process to begin. Click OK


Once the server definition is successfully created it will ask to start the server


Micro strategy server manager window will indicate whether the service is started or stopped


It will take a few minutes to start the service


Once IS configuration is done select project source & click next


Name the project source & click next. Note that Intelligent server is select default


Select the system in which Intelligence server is installed using the browse button


Select the location of IS to which we want to connect & also specify the default port number


We can provide username & password either windows or anonymous or standard authentication to enter into the project source


Once the project source configuration has been completed Finish the wizard & exit from it


While entering into the project source it will ask for username & password


Incase if there is no projects in project source it will return this warning message


PROJECT CREATION


Right-click the Project source and Choose Create New Project option


Click on the option Create Project and Click OK.


Specify the project Name and mention The project sourceTo be used. Click OK


Give login Id and Password and Click OK.


Click the option select tables from Warehouse Catalog to Fetch tables from Warehouse and Click OK.Choose from the existing data Base instance or Create a new Instance mentioning the Database.


Welcome Page for the Database Instance wizard as shown below


Specify the instance name and select the required Database type


Select the DSN and give the database login and password. Click Next


Summary Screen for the Database Instance wizard as shown below


Click ok


After creating the instance the warehouse window opens


Select the required fact and lookup tables from the warehouse


89

Types of Microstrategy Objects

•Application or User Objects – Reports and report related objects built using desktop (viz.templates,filters,metrics and so on)

•Configuration Objects – Administrative and connectivity-related definitions(viz. Database Instances, Cache monitor and so on)

•Schema Objects – Abstractions that relate application objects to physical data warehouse structures(viz. attributes, facts,hierarchies,transformations)



MicroStrategy ObjectsMicroStrategy Objects

Schema objects are used to create user objects.

User objects are used to create reports and documents.

User Objects

• Templates• Filters• Metrics• Custom Groups• Consolidations• Prompts• Searches

• Attributes• Facts• Hierarchies• Transformations• Partitions

Schema Objects

Reports&

Documents

91

•Before reports are created and viewed through desktop, the metadata will have to populated with some basic schema definitions using the MicroStrategy architect.

•The schema objects are

• Attributes

• Facts

• Hierarchies

• Transformation

• Partition Mappings

MICROSTRATEGY ARCHITECT


ATTRIBUTES

Attributes are groups of related data, such as in table columns.

The attribute acts like a column header, and the data that appears in the following table are elements.

Elements define and make up the attribute.

93

ATTRIBUTES


94

ATTRIBUTES - PROPERTIES

• element: unique value (a row) of an attribute

• form: identifier or descriptor of an attribute such as an abbreviation or URL

• expression: criterion defining what an attribute form does with columns, such as combining columns

• relationship: allows interaction of data and shows how data is related within a project


Attribute roles

Attribute roles are used when a lookup table is used for more than one attribute. For example, state can refer to the location of a vendor and of a store. To see both roles on the same report, you must treat them as different attributes. That is, they must have different attribute names. If any attribute must play multiple roles, an attribute must be created in the logical model for each of the roles.

To create unique attributes, you can use either

• automatic attribute role recognition, where you create multiple attributes on the same table and allow MicroStrategy to automatically detect the multiple roles

• explicit table aliasing, where you create multiple logical tables pointing to the same physical table and define different attributes in each



Steps to turn on automatic role recognition

•In the Database Instance Manager, right-click your database instance and choose VLDB Properties.

•Expand the Query Optimizations folder.

•Select Engine Attribute Role Options.

Note: If the Engine Attribute Role Options is not visible in the Query Optimizations folder, select Show Advanced Settings from the Tools menu.

•Clear the Use default inherited value check box. If it is selected, the Engine Attribute Role Options are not available for selection.

•Select the Enable Engine Attribute Role Feature option.

• Click Save and Close.


Attribute role creation by explicit table aliasing

On the MicroStrategy Desktop, navigate to the Tables folder under the Schema Objects folder.

•Right-click the table to alias and select Create Table Alias. This option copies the table into the schema.

•Type the table alias, or the new name for the table.

•When creating the new attributes, select the appropriate table for each attribute. For example, two aliases were created on the physical table LU_State for vendor state (LU_State_Vendor) and store state (LU_State_Store). In this step, you would select the LU_State_Store table for the data source for the Store State attribute. Then you would select the LU_State_Vendor table for the Vendor State data source. For detailed instructions on creating attributes,


Column Alias

FACTS

Facts are objects which relate numeric data values from the data warehouse to the

MicroStrategy Desktop reporting environment.

100

FACTS - TYPES

Simple factsA simple fact is made up of one or more fact expressions.

With a simple fact definition, you can define a fact as a column, constant, or simple expression.

Implicit factsAn implicit fact is a virtual or constant fact that does not

physically exist in the database because it is created at the application level.

Derived factsA derived fact has its value determined by an expression

that combines two or more columns in a database to create a new column.


101

FACTS – Definition example


102

FACTS – LEVEL EXTENSIONS

• You can use level extensions to change a fact level, which is a set of attributes that represent the lowest level of detail at which the fact exists in the warehouse.

• Level extensions define how facts can be extended, lowered, or disallowed to other facts across the schema.


103


Before any facts can be resolved, the level extension must be defined, in case it is needed by a report.

Resolution methods:

• Table relation• Fact relation• Cross-product• Degradation• Disallow the fact level


104


Table relationDefines a join on tables. When you create a join between a

lookup or fact table, you are creating a table relation to extend a fact.

Fact relationFact extensions can be defined by fact relation instead of table

relation. With a fact relation, the table join is possible on any table that contains the fact.

Cross productYou can use a cross product join when a join does not exist, and

where you need to force a fact to relate to an attribute by extending the fact. The cross product join allows a single fact value to relate to all elements of an unrelated attribute.


105


Degradationwhen facts exist at a higher level than the report display level,

you must specify how the Engine degrades the data to the lower level. When you lower the level at which a fact is reported, you are using degradation.

DisallowA disallow is like a lock, which you use to prevent a fact from

being reported at a specific level. For example, you can select an attribute or set of attributes at which level you do not want the fact reported.


Functions and Operators

Functions are the basis for many MicroStrategyobjects. They are used to create Attribute form expressions Consolidation expressions Custom group expressions Fact expressions Filters Metric expressions Subtotals Transformations


Five types of functions

Single-value functionsE.g. Abs, Cos, Round, Truncate,ApplySimple and so on. Group-value functionsE.g. Avg, Count, Sum, ApplyAgg, and so on. OLAP functionsE.g. Rank, RunningSum, ApplyOLAP, and so on. Logical functionsE.g. And, Or, Not, and ApplyLogic. Comparison functionsE.g. Between, Like, >,<, ApplyComparison, and so on.


OLAP Functions

ApplySimple() used to define attribute and metric

Accepts facts, attributes, and metrics as input.

Using an attribute:

Example 1ApplySimple ("Datediff (YY, #0,getdate ())", [BIRTH_DATE])

Example 2ApplySimple ("Months_between(sysdate,#0)",[CURRENT_DT])


Using a compound metric

Example 3ApplySimple ("Greatest (#0, #1, #2),

Metric_1,Metric_2,Metric_3)

Example 4ApplySimple (" CASE WHEN #0 between 0 and 100000

THEN 'Low' WHEN #0 between 100001 and 200000 THEN 'Med' ELSE 'High' END ", Sum (Revenue){~})


ApplyAgg() function used to define simple metrics or factsAccepts facts, attributes, and metrics as input.Example ApplyAgg ("sum (case when #1 in (‘received’) then 0 else #0

end)", [monetary_based_fact], tag_attribute) {~+})

ApplyOLAP() function used to define compound metricsAccepts only metrics as input.ExampleApplyOLAP ("RunningSlope (#0, #1)", [Metric 1], [Metric 2])


AppplyComparison() function used to define custom filters

Accepts facts, attributes, and metrics as input.

Example 1ApplyComparison ("#0 between #1 and #2",?

[Value Prompt Date], [Order Date]@ID, [Ship Date]@ID)

Example 2ApplyComparison ("#0>#1", Store@ID, Month@ID)

111


ApplyLogic() function used to define custom filters

Accepts logic (Boolean) values as input.

Example

ApplyLogic ("#0 and #1", Year@ID>2003, Month@ID>200301)


HIERARCHIES

Hierarchies are groupings of attributes which can be displayed, ordered or unordered, to reflect their relationships to other attributes.

114

HIERARCHIES - TYPES

• User Hierarchy : This is unordered, and you can easily change its design to include additional attributes, or limit the user access.

• System hierarchy : This is ordered, and it is created automatically when you create new projects.


115

HIERARCHIES - EXAMPLE

Time Hierarchy:


116

HIERARCHIES - DRILLING

• Drilling is a function in MicroStrategy Desktop reports that allows you to browse lower levels of attributes along pre-defined criteria.

• When you create hierarchies you can specify what level attributes are included in drilling.

• Depending on the level of the attributes are included in the drilling specification, reports that use the hierarchy allow the user to drill down to lower levels of detail.


Tables

Importing of tables


Importing of Tables


On Desktop, right-click anywhere in the right panel, select New and then Logical Table.

The Table Editor is displayed with the Physical View tab selected by default.

In the SQL Statement panel, type in your SQL statement (you can drag and drop columns from the Object Browser to insert into the statement).

Click Add to map columns returned by the SQL statement.Type in the column name under Column Object. This creates a new column.Alternatively, you can also drag and drop columns from the Object Browser to the Column Object cell. By doing this, you map an existing column to the logical view.

Select a Data Type for the column by using the drop-down list.

Modify the Precision and Scale of the column, if applicable.

Use the Remove, Move Up, or Move Down options for the columns, if needed.Save and Close the logical table.From the schema menu, select Update Schema to ensure that the new logical table is loaded into the schema.

Right click & select Table alias to create an alias name for a table

TRANSFORMATIONS

A transformation is a group of member attributes that share the same kind of analysis on time. Multiple member attributes can define a transformation.

129

TRANSFORMATIONS

• Transformations are used to compare values at different times.

For example, you want to compare sales for this month against sales for the previous month, the same month in the previous year, and so on.

Another example is the comparison of year-to-date data against daily sales data.

The simple metric tallies daily sales. The transformation metric calculates a rolling total of sales on a daily basis.


130

TRANSFORMATIONS - TYPES

• Expression - based transformations – You implement these transformations using a mathematical formula in Microstrategy Architect.

• Table - based transformations – These transformations are based on a transformation – or relate –table in the warehouse.


131

TRANSFORMATIONS - TYPES

• Expression-based transformations:You define these transformations using a mathematical expression. A transformation expression typically includes an attribute ID column, a mathematical operator, and a constant. For example, you might create a Last Quarter or Last Month transformation using QUARTER_ID – 1 or MONTH_ID-1.

• Table – Based Transformations:These transformations use a table in the warehouse to define the transformations from one time period to another.


132

TRANSFORMATIONS – EXAMPLE TABLES

Month-to-Date

Month_id Last_Month

199902 199901

199903 199902

199904 199903

Day_id MTD

3/1/99 3/1/99

3/2/99 3/1/99

3/2/99 3/2/99

3/3/99 3/1/99

3/3/99 3/2/99

3/3/99 3/3/99Day_id Last_Month

3/9/99 2/9/99

3/10/99 2/10/99

3/11/99 2/11/99

3/12/99 2/12/99


Microstrategy Training

Documents

Transcript of Microstrategy Training