Project Design Guide

Version: 8.1.1
Document Number: 09330811

Fourth Edition, September 2007, version 8.1.1
To ensure that you are using the documentation that corresponds to the software you are licensed to use, compare this version number with the software version shown in “About MicroStrategy...” in the Help menu of your software. Document number: 09330811 Copyright © 2007 by MicroStrategy Incorporated. All rights reserved. If you have not executed a written or electronic agreement with MicroStrategy or any authorized MicroStrategy distributor, the following terms apply: This software and documentation are the proprietary and confidential information of MicroStrategy Incorporated and may not be provided to any other person. Copyright © 2001-2007 by MicroStrategy Incorporated. All rights reserved. THIS SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS” AND WITHOUT EXPRESS OR LIMITED WARRANTY OF ANY KIND BY EITHER MICROSTRATEGY INCORPORATED OR ANYONE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, GOOD TITLE AND NONINFRINGMENT, QUALITY OR ACCURACY. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE AND DOCUMENTATION IS WITH YOU. SHOULD THE SOFTWARE OR DOCUMENTATION PROVE DEFECTIVE, YOU (AND NOT MICROSTRATEGY, INC. OR ANYONE ELSE WHO HAS BEEN INVOLVED WITH THE CREATION, PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE OR DOCUMENTATION) ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION. SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. In no event will MicroStrategy, Inc. or any other person involved with the creation, production, or distribution of the Software be liable to you on account of any claim for damage, including any lost profits, lost savings, or other special, incidental, consequential, or exemplary damages, including but not limited to any damages assessed against or paid by you to any third party, arising from the use, inability to use, quality, or performance of such Software and Documentation, even if MicroStrategy, Inc. or any such other person or entity has been advised of the possibility of such damages, or for the claim by any other party. In addition, MicroStrategy, Inc. or any other person involved in the creation, production, or distribution of the Software shall not be liable for any claim by you or any other party for damages arising from the use, inability to use, quality, or performance of such Software and Documentation, based upon principles of contract warranty, negligence, strict liability for the negligence of indemnity or contribution, the failure of any remedy to achieve its essential purpose, or otherwise. The entire liability of MicroStrategy, Inc. and your exclusive remedy shall not exceed, at the option of MicroStrategy, Inc., either a full refund of the price paid, or replacement of the Software. No oral or written information given out expands the liability of MicroStrategy, Inc. beyond that specified in the above limitation of liability. Some states do not allow the limitation or exclusion of liability for incidental or consequential damages, so the above limitation may not apply to you. The information contained in this manual (the Documentation) and the Software are copyrighted and all rights are reserved by MicroStrategy, Inc. MicroStrategy, Inc. reserves the right to make periodic modifications to the Software or the Documentation without obligation to notify any person or entity of such revision. Copying, duplicating, selling, or otherwise distributing any part of the Software or Documentation without prior written consent of an authorized representative of MicroStrategy, Inc. are prohibited. U.S. Government Restricted Rights. It is acknowledged that the Software and Documentation were developed at private expense, that no part is public domain, and that the Software and Documentation are Commercial Computer Software provided with RESTRICTED RIGHTS under Federal Acquisition Regulations and agency supplements to them. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFAR 252.227-7013 et. seq. or subparagraphs (c)(1) and (2) of the Commercial Computer Software—Restricted Rights at FAR 52.227-19, as applicable. Contractor is MicroStrategy, Inc., 1861 International Drive, McLean, Virginia 22102. Rights are reserved under copyright laws of the United States with respect to unpublished portions of the Software. The following are either trademarks or registered trademarks of MicroStrategy Incorporated in the United States and certain other countries:
MicroStrategy, MicroStrategy 6, MicroStrategy 7, MicroStrategy 7i, MicroStrategy 7i Evaluation Edition, MicroStrategy 7i Olap Services, MicroStrategy 8, MicroStrategy Evaluation Edition, MicroStrategy Administrator, MicroStrategy Agent, MicroStrategy Architect, MicroStrategy BI Developer Kit, MicroStrategy Broadcast Server, MicroStrategy Broadcaster, MicroStrategy Broadcaster Server, MicroStrategy Business Intelligence Platform, MicroStrategy Consulting, MicroStrategy CRM Applications, MicroStrategy Customer Analyzer, MicroStrategy Desktop, MicroStrategy Desktop Analyst, MicroStrategy Desktop Designer, MicroStrategy eCRM 7, MicroStrategy Education, MicroStrategy eTrainer, MicroStrategy Executive, MicroStrategy Infocenter, MicroStrategy Intelligence Server, MicroStrategy Intelligence Server Universal Edition, MicroStrategy MDX Adapter, MicroStrategy Narrowcast Server, MicroStrategy Objects, MicroStrategy OLAP Provider, MicroStrategy SDK, MicroStrategy Support, MicroStrategy Telecaster, MicroStrategy Transactor, MicroStrategy Web, MicroStrategy Web Business Analyzer, MicroStrategy World, Alarm, Alarm.com, Alert.com, Angel, Angel.com, Application Development and Sophisticated Analysis, Best In Business Intelligence, Centralized Application Management, Changing The Way Government Looks At Information, DSSArchitect, DSS Broadcaster, DSS Broadcaster Server, DSS Office, DSSServer, DSS Subscriber, DSS Telecaster, DSSWeb, eBroadcaster, eCaster, eStrategy, eTelecaster, Information Like Water, Insight Is Everything, Intelligence Through Every Phone, Your Telephone Just Got Smarter, Intelligence To Every Decision Maker, Intelligent E-Business, IWAPU, Personal Intelligence Network, Personalized Intelligence Portal, Query Tone, Quickstrike, Rapid Application Development, Strategy.com, Telepath, Telepath Intelligence, Telepath Intelligence (and Design), MicroStrategy Intelligent Cubes, The E-Business Intelligence Platform, The Foundation For Intelligent E-Business, The Integrated Business Intelligence Platform Built For The Enterprise, The Intelligence Company, The Platform For Intelligent E-Business, The Power Of Intelligent eBusiness, The Power Of Intelligent E-Business, The Scalable Business Intelligence Platform Built For The Internet, Industrial-Strength Business Intelligence, Office Intelligence, MicroStrategy Office, MicroStrategy Report Services, MicroStrategy Web MMT, MicroStrategy Web Services, Pixel Perfect, MicroStrategy Mobile and MicroStrategy Integrity Manager are all registered trademarks or trademarks of MicroStrategy Incorporated. All other products are trademarks of their respective holders. Specifications subject to change without notice. MicroStrategy is not responsible for errors or omissions. MicroStrategy makes no warranties or commitments concerning the availability of future products or versions that may be planned or under development. Patent Information This product is patented. One or more of the following patents may apply to the product sold herein: U.S. Patent Nos. 6,154,766, 6,173,310, 6,260,050, 6,263,051, 6,269,393, 6,279,033, 6,501,832, 6,567,796, 6,587,547, 6,606,596, 6,658,093, 6,658,432, 6,662,195, 6,671,715, 6,691,100, 6,694,316, 6,697,808, 6,704,723, 6,707,889, 6,741,980, 6,765,997, 6,768,788, 6,772,137, 6,788,768, 6,792,086, 6,798,867, 6,801,910, 6,820,073, 6,829,334, 6,836,537, 6,850,603, 6,859,798, 6,873,693, 6,885,734, 6,888,929, 6,895,084, 6,940,953, 6,964,012, 6,977,992, 6,996,568, 6,996,569, 7,003,512, 7,010,518, 7,016,480, 7,020,251, 7,039,165, 7,082,422, 7,113,993, 7,127,403, 7,174,349, 7,194,457, 7,197,461, 7,228,303, 7,260,577, 7,266,181 and 7,272,212. Other patent applications are pending.

Various MicroStrategy products contain the copyrighted technology of third parties. This product may contain one or more of the following copyrighted technologies: Graph Generation Engine Copyright © 1998-2007. Three D Graphics, Inc. All rights reserved. Actuate® Formula One. Copyright © 1993-2007 Actuate Corporation. All rights reserved. XML parser Copyright © 2003-2007 Microsoft Corporation. All rights reserved. Xalan XSLT processor. Copyright © 1999-2007. The Apache Software Foundation. All rights reserved. Xerces XML parser. Copyright © 1999-2007. The Apache Software Foundation. All rights reserved. FOP XSL formatting objects. Copyright © 2004-2007. The Apache Software Foundation. All rights reserved. Portions of Intelligence Server memory management Copyright 1991-2006 Compuware Corporation. All rights reserved. International Components for Unicode Copyright © 1999-2007 Compaq Computer Corporation Copyright © 1999-2007 Hewlett-Packard Company Copyright © 1999-2007 IBM Corporation Copyright © 1999-2007 Hummingbird Communications Ltd. Copyright © 1999-2007 Silicon Graphics, Inc. Copyright © 1999-2007 Sun Microsystems, Inc. Copyright © 1999-2007 The Open Group All rights reserved. Real Player and RealJukebox are included under license from Real Networks, Inc. Copyright © 1999-2007. All rights reserved.

CONTENTS
Description of Guide ................................................................ xiii About this book .............................................................................xv How to find business scenarios and examples .......................xv Prerequisites .......................................................................... xvi Who should use this guide..................................................... xvi Resources.................................................................................... xvi Documentation....................................................................... xvi Education ............................................................................. xxiii Consulting ............................................................................ xxiii International support ............................................................ xxiii Technical Support ................................................................. xxv Feedback .................................................................................... xxx

1. BI Architecture and the MicroStrategy Platform

Introduction.................................................................................. 1 Business intelligence architecture ................................................. 2 Source systems for data collection .......................................... 3 Extraction, transformation, and loading process...................... 4 Data warehouse for data storage and relational design .......... 5 The MicroStrategy platform ........................................................... 7 MicroStrategy metadata........................................................... 8 MicroStrategy Intelligence Server .......................................... 11 MicroStrategy Desktop........................................................... 11 MicroStrategy Web and Web Universal ................................. 13 MicroStrategy project ............................................................. 14 The project design process.......................................................... 15

© 2007 MicroStrategy, Inc.

v

Contents

Project Design Guide

2. The Logical Data Model

Introduction................................................................................ 17 Facts: Business data and measurements.................................... 21 Attributes: Context for your levels of data.................................... 22 Attribute elements: Data level values..................................... 23 Attribute relationships ............................................................ 24 Hierarchies: Data relationship organization ................................. 25 Sample data model...................................................................... 26 Building a logical data model ....................................................... 26 User requirements ................................................................. 27 Existing source systems ........................................................ 28 Converting source data to analytical data.............................. 28 Logical data modeling conventions.............................................. 33 Unique identifiers ................................................................... 34 Cardinalities and ratios .......................................................... 35 Attribute forms ....................................................................... 36

3. Warehouse Structure for Your Logical Data Model

Introduction................................................................................ 39 Columns: Data identifiers and values .......................................... 41 Tables: Physical groupings of related data.................................. 41 Uniquely identifying data in tables with key structures........... 42 Lookup tables: Attribute storage ............................................ 43 Relate tables: A unique case for relating attributes ............... 45 Fact tables: Fact data and levels of aggregation ................... 46 Homogeneous versus heterogeneous column naming.......... 49 Schema types: Data retrieval performance versus redundant storage......................................................................................... 51 Highly normalized schema: Minimal storage space............... 52 Moderately normalized schema: Balanced storage space and query performance.......................................................... 54 Highly denormalized schema: Enhanced query performance........................................................................... 56 Design trade-offs ......................................................................... 59 Schema type comparisons .......................................................... 60

4. Creating and Configuring a Project

Introduction................................................................................ 63 Project connectivity components ................................................. 64 MicroStrategy metadata......................................................... 64 Metadata shell ....................................................................... 65 Project source ........................................................................ 65

vi

© 2007 MicroStrategy, Inc.

Project Design Guide

Contents

Database instance ................................................................. 67 Project.................................................................................... 67 Summary of project connectivity ............................................ 68 Creating a project ........................................................................ 68 Creating the metadata repository ................................................ 71 Connecting to the metadata repository and data source ............. 71 Connecting to the metadata repository .................................. 72 Connecting to a data source .................................................. 72 Creating the project ..................................................................... 73 Creating a test or prototype project using Project Builder...... 74 Creating a production project using Project Creation Assistant ................................................................................ 75 Creating facts and attributes........................................................ 82 Configuring additional schema-level settings .............................. 83 Deploying your project and creating reports ................................ 84

5. The Building Blocks of Introduction................................................................................ 85 Business Data: Facts Creating facts............................................................................... 87 Simultaneously creating multiple, simple facts ...................... 88 Creating and modifying simple and advanced facts .............. 91 The structure of facts ................................................................... 96 How facts are defined ................................................................. 97 Mapping physical columns to facts: Fact expressions ........... 98 Fact column names and data types: Column aliases ................ 105 Modifying the levels at which facts are reported: Level extensions.................................................................................. 107 Defining a join on fact tables using table relations............... 110 Defining a join on fact tables using fact relations................. 114 Forcing facts to relate to attributes: Using cross product joins ........................................................................ 116 Lowering the level of fact data: Fact degradations .............. 118 Disallowing the reporting of a fact at a certain level............. 122

6. The Context of Your Business Data: Attributes

Introduction.............................................................................. 125 Creating attributes ..................................................................... 129 Simultaneously creating multiple attributes.......................... 129 Adding and modifying attributes .......................................... 134 Unique sets of attribute information: Attribute elements ............ 140

© 2007 MicroStrategy, Inc.

vii

Contents

Project Design Guide

Column data descriptions and identifiers: Attribute forms ......... 143 Attribute form properties ...................................................... 146 Attribute form expressions ................................................... 147 Modifying attribute data types: Column aliases ................... 156 Attribute forms versus separate attributes ........................... 158 Attribute relationships ................................................................ 159 Viewing and editing the parents and children of attributes .............................................................................. 161 Supporting many-to-many and joint child relationships ....... 163 Attributes that use the same lookup table: Attribute roles ......... 175 Specifying attribute roles ..................................................... 177 Attributes with more than one ID column: Compound attributes .................................................................................... 183 Example: Creating compound attributes.............................. 184 Collections of attribute forms: Form groups............................... 186 Supporting compound attributes .......................................... 187 Displaying and organizing related forms.............................. 188 Using attributes to browse and report on data........................... 189 Setting how attribute forms are displayed by default ........... 191

7. Creating Hierarchies to Organize and Browse Attributes

Introduction.............................................................................. 193 Creating user hierarchies........................................................... 194 Types of hierarchies .................................................................. 196 System hierarchy: Project schema definition ....................... 197 User hierarchies: Logical business relationships ................. 197 Hierarchy organization............................................................... 198 Hierarchy structure............................................................... 199 Viewing hierarchies: Hierarchy Viewer ................................ 200 Configuring hierarchy display options........................................ 200 Controlling the display of attribute elements ........................ 201 Filtering attributes in a hierarchy.......................................... 203 Entry point............................................................................ 205 Hierarchy browsing .............................................................. 206 Using the Hierarchy Viewer and Table Viewer .......................... 211 Using the Hierarchy Viewer ................................................. 211 Using the Table Viewer........................................................ 213

8. Optimizing and Maintaining Your Project viii

Introduction.............................................................................. 215 Updating your MicroStrategy project schema............................ 216

© 2007 MicroStrategy, Inc.

Project Design Guide

Contents

Data warehouse and project interaction: Warehouse Catalog ...................................................................................... 218 What should I know before I use the Warehouse Catalog? .............................................................................. 219 Accessing the Warehouse Catalog...................................... 219 Adding and removing tables for a project ............................ 220 Managing warehouse and project tables ............................. 221 Modifying data warehouse connection and operation defaults ................................................................................ 226 Customizing catalog SQL statements.................................. 233 Troubleshooting table and column messages ..................... 239 Using summary tables to store data: Aggregate tables ............. 241 When to use aggregate tables............................................. 242 Determining the frequency of queries at a specific level...... 246 Considering any related parent-child relationships .............. 246 Compression ratio................................................................ 247 Creating aggregate tables ................................................... 248 The size of tables in a project: Logical table size................. 249 Dividing tables to increase performance: Partition mapping...... 250 Server versus application partitioning .................................. 250 Metadata partition mapping ................................................. 251 Warehouse partition mapping .............................................. 254 Metadata versus warehouse partition mapping ................... 255

9. Creating Transformations to Define Time-Based and Other Comparisons

Introduction.............................................................................. 257 Creating transformations ........................................................... 258 Expression-based versus table-based transformations ....... 259 Building a table-based transformation ................................. 260 Building an expression-based transformation...................... 261 Transformation components ...................................................... 263 Transformation metrics and joint child attributes ....................... 265

A. MicroStrategy Tutorial Introduction.............................................................................. 267 What is the MicroStrategy Tutorial?........................................... 267 MicroStrategy Tutorial data model............................................. 271 Geography hierarchy ........................................................... 272 Products hierarchy ............................................................... 274 Customers hierarchy............................................................ 276 Time hierarchy ..................................................................... 277 Promotions hierarchy ........................................................... 278

© 2007 MicroStrategy, Inc.

ix

......................................................................................................................................... 280 Geography schema ................................ 340 Configuring the XMLA Provider ..................................................................................... 317 Relating objects from Analysis Services 2005 to MicroStrategy.......... 334 Connecting to Analysis Services 2000 servers............................................ 330 Connecting to Essbase servers ... 298 Relating objects from SAP BW to MicroStrategy .................... 334 Configuring the XMLA Provider .......... 311 Relating objects from Essbase to MicroStrategy ............................. 338 Connecting to Analysis Services 2005 servers............ 285 Time schema .... 291 MicroStrategy integration with OLAP cube sources .................................................................................................................. 341 Integrating OLAP cubes into MicroStrategy........................................................................ 297 Understanding the SAP BW terminology ...... 343 Importing OLAP cubes.............. 349 Creating metrics from OLAP cube data with MDX and compound metric techniques .............................. 284 Customers schema ........................ 288 Miscellaneous fact tables.................... 328 Connecting to SAP BW servers on UNIX and Linux............................................................. 359 x © 2007 MicroStrategy................................Contents Project Design Guide MicroStrategy Tutorial schema .......................................... 311 Relating objects from Analysis Services 2000 to MicroStrategy.................. 292 Understanding MicroStrategy architecture.... 294 Authentication ........................ ............................. 327 Connecting to SAP BW servers on Windows ....... 283 Products schema ....................... 286 Promotions schema ........................................................................................................................................................................... Inc......................................... 337 Configuring the XMLA Provider ......................... Connecting to OLAP Cube Sources Introduction... 287 Inventory fact tables........................................................... 322 Connecting to SAP BW servers................. 308 SAP BW structures .......................................................................................................................................................................... 302 Supporting SAP BW variables ................................................................................................................. 344 Mapping OLAP cubes .................................. 288 B............................. 287 Sales fact tables ...........................

........................... 373 Using SQL for logical views .............. 403 Index .................................. 376 Business case 1: Distinct attribute lookup table.......................................................................................... 378 Business case 4: One-to-many transformation tables ....................... 399 Big Decimal............................................................................................... 401 Glossary ............................. 389 Business case 5: Outer joins between attribute lookup tables........................... 369 Logical tables........................................................................................................Project Design Guide Contents C......................................................................... Logical Tables Introduction............... 400 Using the Big Decimal data type........................................... 398 Data type and format type compatibility.............................................. 395 Mapping of external data types to MicroStrategy data types............................ Data Types Introduction......................................... 376 Business case 2: Attribute form expression across multiple tables ............. 395 MicroStrategy data types .... 390 D............................... xi ........................... 375 Logical view examples............................................................................................................................ 397 Format types............................... 377 Business case 3: Slowly changing dimensions... 371 Creating logical tables .............................................................................. 370 How should I use logical tables? ......................................... Inc........ 427 © 2007 MicroStrategy..........................................................................

Inc.Contents Project Design Guide xii © 2007 MicroStrategy. .

creating. The Logical Data Model. describes components of the physical warehouse schema such as columns and tables and explores how you can map components from the logical data model to components in the database to form the physical warehouse schema. explores logical data modeling and how it can help you identify the different elements within your business data and plan your project. Inc. provides a brief introduction to business intelligence architecture and some of the main components within the MicroStrategy platform. • • • © 2007 MicroStrategy. Chapter 4. xiii . Chapter 3. BI Architecture and the MicroStrategy Platform. and modifying a project in MicroStrategy and covers a wide range of project-related topics.PREFACE Description of Guide The MicroStrategy Project Design Guide provides comprehensive information on planning. Chapter 2. Creating and Configuring a Project. describes the major components involved in project creation and guides you through the process of creating a project in MicroStrategy. Warehouse Structure for Your Logical Data Model. including the following: • Chapter 1.

Optimizing and Maintaining Your Project. This chapter also covers all the steps necessary to create facts for your project. which you may or may not require depending on your specific needs: • Appendix A. the different types of logical tables. and explains how you can create user hierarchies to help organize and enhance your project. provides a conceptual look at the structure of attributes and explores different types of attributes and how they relate to your business data. The Context of Your Business Data: Attributes. provides information about connecting to an OLAP Cube source such as SAP® BW. discusses the different types of transformations in MicroStrategy and describes how you can create transformations in your project. Chapter 6.Preface Project Design Guide • Chapter 5. provides information on the MicroStrategy Tutorial project. Logical Tables. • • • • The appendixes contain the following additional reference information. • • xiv © 2007 MicroStrategy. . Chapter 8. Appendix C. The Building Blocks of Business Data: Facts. This chapter also covers all the steps necessary to create attributes for your project. Creating Transformations to Define Time-Based and Other Comparisons. Chapter 7. Chapter 9. discusses logical tables. Creating Hierarchies to Organize and Browse Attributes. and a set of demonstration applications designed to illustrate the features of the MicroStrategy platform. discusses the different types of hierarchies in MicroStrategy. Appendix B. Inc. or Hyperion® Essbase® for use within MicroStrategy. describes methods you can implement to better optimize and maintain your project for both the short and long term. describes the structure of facts and explores different types of facts and how they relate to your business data. which includes a metadata and warehouse. Connecting to OLAP Cube Sources. Microsoft® Analysis Services. MicroStrategy Tutorial. and how to create logical tables and views in MicroStrategy.

Project Design Guide Preface • Appendix D. How to find business scenarios and examples Within this guide. each from a different business area. which are a set of sample analytics. The following sections provide the location of additional examples. and describe the user roles the information in this book was designed for. Each module comes with a sample data model and a collection of packaged reports that allow dozens of analytical variations. many of the concepts discussed are accompanied by business scenarios or other descriptive examples. human resources. list prerequisites for using this book. and project. Detailed examples of advanced reporting functionality can be found in the MicroStrategy Advanced Reporting Guide. Data Types. see the MicroStrategy Tutorial. The Analytics Modules are part of a product bundle called the MicroStrategy Business Intelligence Developer Kit (BIDK). Business scenarios can be found in the Analytics Modules. For examples of reporting functionality. Inc. Example analysis includes such business areas as financial reporting. which is MicroStrategy’s sample warehouse. About this book xv . metadata. © 2007 MicroStrategy. About this book This book is divided into chapters that begin with a brief overview of the chapter’s content. Information about the MicroStrategy Tutorial can be found in the MicroStrategy Basic Reporting Guide. and customer analysis. provides information about the different data types in MicroStrategy.

and modify a MicroStrategy project using the MicroStrategy platform. as described below. these two information sources provide different types of information. create. Inc.Preface Project Design Guide Prerequisites Before working with this document. In short. the following business intelligence application users should read this guide: • • Project Designers Database Administrators Resources Documentation MicroStrategy provides both manuals and online help. . Manuals: MicroStrategy manuals provide • • • introductory information concepts checklists xvi Resources © 2007 MicroStrategy. you should be familiar with: • • the information provided in the MicroStrategy Installation and Configuration Guide the nature and structure of the data you want to use for your business intelligence application Who should use this guide This document is designed for all users who require an understanding of how to design.

Manuals for Query. configuring.com. Resources xvii .Project Design Guide Preface • • examples high-level procedures to get started Online help: MicroStrategy online help provides • • detailed steps to perform procedures descriptions of each option on every software screen Manuals The following manuals are available from your CD-ROM or the machine where MicroStrategy was installed. Inc. The procedure to access them is below. you can download it from www. © 2007 MicroStrategy. • MicroStrategy Quick Start Guide Overview of the installation and evaluation process.adobe.0 or higher is required to view these documents. and HP platforms. and Analysis Products • MicroStrategy Installation and Configuration Guide Information to install and configure MicroStrategy products on Windows. and using the MicroStrategy Evaluation Edition of the software. UNIX. MicroStrategy Overview • Introduction to MicroStrategy: Evaluation Guide Instructions for installing. Adobe Acrobat Reader 4. as well as basic maintenance guidelines. Linux. If you do not have Acrobat Reader installed on your computer. • MicroStrategy Upgrade Guide Instructions to upgrade existing MicroStrategy products. Reporting. and additional resources.

Freeform SQL reports. filters. • MicroStrategy Basic Reporting Guide Instructions to get started with MicroStrategy Desktop and MicroStrategy Web. deploy. hierarchies. filters. metrics. and perform other business tasks with MicroStrategy reports and documents on a mobile device. building on information in the Basic Reporting Guide. transformations. • MicroStrategy Report Services Document Creation Guide Instructions to design and create Report Services documents. Query Builder reports. attributes. Word. OLAP Cube reports. and troubleshoot a MicroStrategy business intelligence system. Data Mining Services. building on information in the Basic Reporting Guide and Advanced Reporting Guide. metrics. tune. • MicroStrategy Mobile User Guide Instructions for using MicroStrategy Mobile to view and analyze data. • MicroStrategy Project Design Guide Information to create and modify MicroStrategy projects. Topics include reports. Inc. • MicroStrategy Advanced Reporting Guide Instructions for advanced topics in the MicroStrategy system. consolidations. PowerPoint®. advanced schemas. • MicroStrategy Office User Guide Instructions for using MicroStrategy Office to work with MicroStrategy reports and documents in Microsoft® Excel. format. and understand facts. maintain. Includes the basics for creating reports. to analyze. and project optimization. and prompts. and Outlook. custom groups. and distribute business data. . and prompts. and how to analyze data in a report.Preface Project Design Guide • MicroStrategy System Administration Guide Concepts and high-level steps to implement. Covers installation and configuration of MicroStrategy Mobile and how a designer working in MicroStrategy xviii Resources © 2007 MicroStrategy.

filters. • MicroStrategy Functions Reference Function syntax and formula components. maintain. configure. • MicroStrategy Narrowcast Server Upgrade Guide Instructions to upgrade an existing Narrowcast Server. Manuals for Information Delivery and Alerting Products • MicroStrategy Narrowcast Server Getting Started Guide Instructions to work with the tutorial to learn Narrowcast Server interfaces and features.Project Design Guide Preface Desktop or MicroStrategy Web can create effective reports and documents for use with MicroStrategy Mobile. instructions to use functions in metrics. • MicroStrategy Web Services Administration Guide Concepts and tasks to install. tune. attribute forms. and troubleshoot Narrowcast Server. • MicroStrategy Narrowcast Server Application Designer Guide Fundamentals of designing Narrowcast Server applications. and troubleshoot MicroStrategy Web Services. © 2007 MicroStrategy. • MicroStrategy Narrowcast Server Installation and Configuration Guide Information to install and configure Narrowcast Server. Inc. • MicroStrategy Narrowcast Server System Administrator Guide Concepts and high-level steps to implement. tune. Resources xix . examples of functions in business scenarios.

and the Narrowcast Server SPI. • Narrowcast Server SDK Guide Instructions to customize Narrowcast Server functionality. . choose Programs. 2 Click the link for the desired manual. integrate Narrowcast Server with other systems.Preface Project Design Guide Manuals for Analytics Modules • • • • • • Business Intelligence Developer Kit (BIDK) Installation and Porting Guide Customer Analysis Module Reference Sales Force Analysis Module Reference Financial Reporting Analysis Module Reference Sales and Distribution Analysis Module Reference Human Resources Analysis Module Reference Software Development Kits • MicroStrategy Developer Library (MSDL) Information to understand the MicroStrategy SDK. object models. then Product Manuals. code samples. including details about architecture. Inc. and embed Narrowcast Server functionality within other applications. To access installed online documentation 1 From the Windows Start menu. and so on. customization scenarios. xx Resources © 2007 MicroStrategy. Documents the Narrowcast Server Delivery Engine and Subscription Portal APIs. which is sold as part of the MicroStrategy SDK. MicroStrategy. • MicroStrategy Web SDK The Web SDK is available in the MicroStrategy Developer Library. A Web page opens with a list of available manuals in PDF format.

If bookmarks are not visible on the left side of an Acrobat (PDF) document. When you select one of these guides. Select Open this file from its current location. F1 key: Press F1 to see context-sensitive help addressing the function or task you are currently performing. Resources xxi . Inc. and click OK. Help menu: Select Contents and Index to see the main table of contents for the help system.Project Design Guide Preface 3 Some documentation is provided in HTML help format. the File Download dialog box opens. click the Bookmarks and Page from the View menu. Online help MicroStrategy provides several ways to access online help: • • • Help button: Use the Help button at the bottom of most software screens to see context-sensitive help. © 2007 MicroStrategy.

dialog boxes. Type bold Indicates • button names. these should be read before continuing. indicates variable information to be replaced by the user Example: The aggregation level is the level of calculation for the metric. italic • new terms defined within the text and in the glossary • names of other product manuals • when part of a command syntax. check boxes. The following table lists these conventions. UPPERCASE • keyboard command key (such as ENTER) • shortcut key (such as CTRL+V) Example: To bold the selected text. Example: Type cmdmgr -f scriptfile.Preface Project Design Guide Documentation standards MicroStrategy online help and PDF manuals (available both online and in printed format) provides standards to help you identify concepts and procedures. + A keyboard command that calls for the use of more than one key (for example. options. SHIFT+F1) A note icon indicates helpful information for specific situations. xxii Resources © 2007 MicroStrategy. lists.scp and press ENTER. A warning icon alerts you to important information such as potential security risks. press CTRL+B. Example: Type copy c:\filename d:\foldername\filename Courier font • • • • • • calculations code samples registry keys path and file names URLs messages displayed in the screen Example: Sum(revenue)/number of months. and menus that are the focus of actions or part of a list of such GUI elements and their definitions • text to be entered by the user Example: Click Select Warehouse. . Inc.

For a detailed description of consulting offerings. Resources xxiii . currency symbols. performance and tuning. It also includes the availability of translated interfaces and documentation. Support for a locale typically includes native database and operating system support. Inc. decimal formats.microstrategy. visit www.com/Education.com/Consulting. visit www. project and testing strategies and recommendations. support for date formats. The level of support is defined in terms of the components of a MicroStrategy business intelligence environment. and more. strategic planning. International support MicroStrategy supports several locales.microstrategy. Offerings include complex security architecture designs. collectively known as a configuration: • • • • • warehouse. For a detailed description of education offerings and course curriculums.Project Design Guide Preface Education MicroStrategy Education Services provides a comprehensive curriculum and highly skilled education consultants. Consulting MicroStrategy Consulting Services provides proven methods for delivering leading-edge technology solutions. and statistics databases MicroStrategy Intelligence Server MicroStrategy Web server MicroStrategy Desktop client Web browser © 2007 MicroStrategy. A MicroStrategy business intelligence environment consists of the following components. and more. metadata. Many customers and partners from over 800 different organizations have benefited from MicroStrategy instruction.

Repair or maintenance installation on a system on which MicroStrategy application has been installed before All subsequent executions of the installation routine are displayed in the language that you selected the first time you installed the product on the system. Installation Fresh installation on a system in which MicroStrategy application has never been installed before Result The MicroStrategy Installation Wizard prompts you to select the language from the drop-down list. translated versions of the online help files and product documentation are available in several of the above languages. Portuguese (Brazilian). Upgrading an earlier installation from version 7. The user language in the product interface is the language that you select during installation. . the Online Help is displayed in the same language that the user selects in the language prompt of the installation routine. Italian.3 is the language of display of the installation routine and the user language of the product interface.Preface Project Design Guide MicroStrategy is certified in homogeneous configurations (where all the components lie in the same locale) in the following languages: English (US). Korean. Japanese. Spanish. The user language in the product interface is also the language that you selected the first time you installed the product on the system. German.2. A translated user interface is available in each of the above languages. Please contact MicroStrategy Technical Support for more details.2. MicroStrategy also provides limited support for heterogeneous configurations (where some of the components may lie in different locales). Inc. In addition. Once the product is installed.3 The user language preference that was set previously in version 7. The following table lists the language selection possibilities for different installation cases. French. Chinese (simplified) and Swedish. xxiv Resources © 2007 MicroStrategy.

2 or earlier. online help. Paths to access each are described above. are displayed in the language that you selected during the upgrade installation. Technical Support If you have questions about a specific MicroStrategy product.asp © 2007 MicroStrategy. the installation Online Help is displayed in English only.1. Note: Even if you select a language from the language prompt in the installation routine. the MicroStrategy Installation Wizard prompts you to select the language from the drop-down list.2.Project Design Guide Preface Installation Upgrading an earlier installation from version 7. During installation. Inc. Resources xxv . The installation routine is displayed in the selected language. you should: 1 Consult the product guides. Besides. unless overridden by the command line parameter. 2 Consult the MicroStrategy Knowledge Base online at http://www.x Result The MicroStrategy Installation Wizard prompts you to select the language from the drop-down list. Completely uninstalling all the MicroStrategy products and installing the same version or a newer version If you uninstall all the products and install either the same version or a higher version again.com/support/ k_base/index.microstrategy. including 7. the user language of the product interface language remains the same as the one set in the product interface before running the upgrade installation. all subsequent executions of the installation routine for maintenance or for upgrade. and release notes. readme files. However. it has no effect on the default language of the product interfaces.

com/Support/ Expiration. xxvi Resources © 2007 MicroStrategy. the Support Liaison may follow the steps below to ensure that issues are resolved quickly: 1 Verify that the issue is with MicroStrategy software and not a third party software. Inc. MicroStrategy Technical Support may be contacted by your company’s Support Liaison. 3 If the resources listed in the steps above do not provide you with a solution.com/ Support/Policies. .microstrategy. review the Policies and Procedures document posted at http://www. Your company may request to change their Support Liaisons two times per year with prior written notice to MicroStrategy Technical Support. A Support Liaison is a person whom your company has designated as a point-of-contact with MicroStrategy’s support personnel. Ensure issues are resolved quickly Before logging a case with MicroStrategy Technical Support. To ensure the most effective and productive relationship with MicroStrategy Technical Support. All customer inquiries and case communications must come through these named individuals. Your company may designate two employees to serve as their Support Liaisons. contact MicroStrategy Technical Support directly. 4 Minimize the complexity of the system or project object definition to isolate the cause.microstrategy.Preface Project Design Guide A technical administrator in your organization may be able to help you resolve your issues immediately. 2 Verify that the system is using a currently supported version of MicroStrategy software by checking the Product Support Expiration Schedule at http://www.asp. 3 Attempt to reproduce the issue and determine whether it occurs consistently. Refer to the terms of your purchase agreement to determine the type of support available to you.

microstrategy. Monday-Friday except holidays Europe. Inc.M.Project Design Guide Preface 5 Determine whether the issue occurs on a local machine or on multiple machines in the customer environment.–7:00 P.M. Monday-Friday except holidays • Mainland Europe: 9:00 A.M. send e-mail or fax.com Web: https://support. Eastern Time (1400–0000 GMT).M. the Middle East.com Fax: (703) 842–8709 Phone: (703) 848–8700 Hours: 9:00 A. when. Resources xxvii .com. 6 Discuss the issue with other users by posting a question about the issue on the MicroStrategy Customer Forum at https://forums.com Fax: +44 (0) 208 396 0001 The European Technical Support Centre is closed on certain public holidays. they can leave a voicemail message. These holidays reflect the national public holidays in each country.M. or log a case using the Online Support Interface. CET. and Africa (EMEA) © 2007 MicroStrategy.microstrategy. If your Support Liaison is unable to reach MicroStrategy Technical Support by phone during the hours of operation. Monday–Friday except holidays E-mail: eurosupp@microstrategy.–6:00 P. and how to contact MicroStrategy Technical Support. North America E-mail: support@microstrategy.M.com Web: https://support.–6:00 P. GMT.microstrategy. Phone: • United Kingdom: +44 (0) 208 396 0085 • Benelux: +31 20 346 9210 • Finland: +35 8 9 6937 9620 • France: +33 1 41 91 86 49 • Germany: +49 69 95096206 • Ireland: +35 3 1242 1522 • Italy: +39 02696 33 456 • Spain: +34 91 406 90 10 • International distributors: +44 (0) 208 396 0080 Hours: • United Kingdom: 9:00 A. The table on the following page shows where.

S. Although not a requirement. Required information when calling When contacting MicroStrategy Technical Support. Australia.com Web: https://support. The individual Technical Support Centers are closed on certain public holidays. BST (Sao Paulo).com Fax: +81 3 5456 5464 Phone: • Korea: +82 2 560 6565 • Singapore (supporting Singapore. China.M. Pakistan.–6:00 P. and all other Asia Pacific countries not listed in this section): +81 3 3511 6720 Hours: 9:00 A. Malaysia.–7:00 P. and Latin America. India.Preface Project Design Guide Asia Pacific E-mail: apsupport@microstrategy. In North America. please provide the following information: • xxviii Resources Personal information: © 2007 MicroStrategy.8969 • Japan (supporting Japan.M. . or that assume that the designated Support Liaison has a security level that permits them to fully manipulate the MicroStrategy projects and has access to potentially sensitive project data such as security filter definitions. During the course of troubleshooting and researching issues. these holidays reflect the national public holidays in each country. Monday–Friday except holidays Latin America Support Liaisons should contact the Technical Support Center from which they obtained their MicroStrategy software licenses or the Technical Support Center to which they have been designated. national holidays. This can eliminate security conflicts and improve case resolution time.com Fax: +55 11 3044 4088 Phone: LATAM (except Argentina): +55 11 3054 1010 Argentina: 0 800 444 MSTR Hours: 9:00 A. JST (Tokyo).6303. Hong Kong. Inc.M.com Web: https://support. MicroStrategy Technical Support personnel may make recommendations that require administrative privileges on the MicroStrategy projects. Monday-Friday except holidays E-mail: latamsupport@microstrategy. we recommend you designate Support Liaisons who have permissions to be MicroStrategy project administrators.microstrategy.M. In Europe.microstrategy. Asia Pacific. these holidays reflect many U. and Sri Lanka): +65. Taiwan. New Zealand.

and steps taken to troubleshoot the case thus far • Business/system impact If this is the Support Liaison’s first call. including MicroStrategy software product(s) and versions Full description of the case including symptoms. Inc. e-mail addresses) • Case details: Configuration information. Resources • • xxix . error messages(s). and be ready to provide it when inquiring about an existing case software version and product registration numbers of the MicroStrategy software products you are using case description: What causes the condition to occur? Does the condition occur sporadically or each time a certain action is performed? Does the condition occur on all machines or just on one? © 2007 MicroStrategy.Project Design Guide Preface Name (first and last) Company and customer site (if different from company) Contact information (phone and fax numbers. they should also be prepared to provide the following: • • • • street address phone number fax number e-mail address To help the Technical Support representative work to resolve the problem promptly and effectively. be prepared to provide the following additional information: • case number: Please keep a record of the number assigned to each case logged with MicroStrategy Technical Support.

Inc. Feedback Please send any comments or suggestions about user documentation for MicroStrategy products to: xxx Feedback © 2007 MicroStrategy. and so on) network protocol used ODBC driver manufacturer and version database gateway software version (for MicroStrategy Web-related problems) browser manufacturer and version (for MicroStrategy Web-related problems) Web server manufacturer and version If the issue requires additional investigation or testing. RAM. not all items listed below may be necessary): computer hardware specifications (processor speed. or a software upgrade)? If there was an error message. the Support Liaison and the MicroStrategy Technical Support representative should agree on certain action items to be performed. a major database load. what was its exact wording? What steps have you taken to isolate and resolve the issue? What were the results? • system configuration (the information needed depends on the nature of the problem. The Support Liaison should perform any agreed-upon actions before contacting MicroStrategy Technical Support again regarding the issue. If the Technical Support representative is responsible for an action item. .Preface Project Design Guide When did the condition first occur? What events took place immediately prior to the first occurrence of the condition (for example. The Support Liaison may call MicroStrategy Technical Support at any time to inquire about the status of the issue. a database move. disk space.

Inc. Your feedback is important to us as we prepare for future releases.com Send suggestions for product enhancements to: support@microstrategy.Project Design Guide Preface documentationfeedback@microstrategy.com When you provide feedback to us. © 2007 MicroStrategy. please include the name and version of the products you are currently using. Feedback xxxi .

Preface Project Design Guide xxxii Feedback © 2007 MicroStrategy. Inc. .

it is important to understand how business intelligence systems work and. specifically. An optimum business intelligence application: • • • Gives users access to data at various levels of detail Allows users to request information and have it delivered to them accurately and quickly Provides a foundation for the proactive delivery of information to system subscribers © 2007 MicroStrategy.1 1. Inc. Business intelligence (BI) systems facilitate the analysis of volumes of complex data by providing the ability to view data from multiple perspectives. 1 . how the MicroStrategy platform interacts with your business data to provide a wide range of functionality. BI ARCHITECTURE AND THE MICROSTRATEGY PLATFORM Introduction Before planning and creating a project in MicroStrategy.

and other data sources. Excel files. as well as some of the components within the MicroStrategy platform that allow you to create and analyze your business intelligence. and loading (ETL) process A data warehouse—typically an online analytical processing (OLAP) system A business intelligence platform such as MicroStrategy • • • The diagram above illustrates the common setup for standardizing data from source systems and transferring that data into MicroStrategy. transformation. For more information on how MicroStrategy can access your data sources. Microsoft Analysis Services. SAP BW. Inc. MicroStrategy can also access data from text files. but other systems or files that capture or hold data of interest are also possible An extraction.1 BI Architecture and the MicroStrategy Platform Project Design Guide This chapter introduces you to the basic architecture of BI systems. see Data warehouse for data storage and relational design. page 5. . Business intelligence architecture A BI architecture has the following components: • A source system—typically an online transaction processing (OLTP) system. 2 Business intelligence architecture © 2007 MicroStrategy. Hyperion Essbase.

including health care. by business activities and workflow. insertions. This processing is relied upon daily by nearly every industry. as the system records huge volumes of data every day. page 5. see Data warehouse for data storage and relational design. Data history is limited to recent or current data. A source system is usually the most significant site of online transaction processing (OLTP). telecommunications. a different source system—another file on the server—keeps track of each customer’s contact information. and order processing.Project Design Guide BI Architecture and the MicroStrategy Platform 1 Source systems for data collection Source systems refer to any system or file that captures or holds data of interest. website usage. An average bank offers several services such as account activity updates and loan disbursement. OLTP systems are databases or mainframes that store real-time processing data and have the following characteristics: • Data access is optimized for frequent reading and writing. and many others. © 2007 MicroStrategy. and therefore has many source systems to support these services. Meanwhile. suppose one source system—a database file on the bank’s server—keeps track of deposits and withdrawals as they occur. inventory. e-commerce. manufacturing. Transactional processing involves the simple recording of transactions and other business data such as sales. For example. For more information on data warehouse design. • • • Recall the example of a bank that relies on several source systems to store data related to the many services the bank offers. This is in contrast to data warehouses which are often designed for reading data for analysis with a minimum number of updates. Business intelligence architecture 3 . or deletions. deposits. A bank is an example of a business with many source systems. Data formats are not necessarily uniform across systems. that is. Data is aligned by application. An example of data that benefits from this type of optimization is the number of credit card transactions that an OLTP system might record in a single day. Inc. Each of these business services has a different and specific workflow.

Transformation procedures can include converting data types and names. and loading (ETL) process represents all the steps necessary to move data from different source systems to an integrated data warehouse. and money market account information. loan status. transformation. Since 4 Business intelligence architecture © 2007 MicroStrategy. The ETL process consolidates data so it can be stored in a data warehouse. eliminating unwanted data. you can withdraw or deposit money as well as check on balances. Extraction. account balances. This is because the operational systems supporting these two services are designed to perform specific tasks. and loading process The extraction. and loading (ETL) process. This process can be explained with the example of a bank that wants to consolidate a variety of information about a particular customer. the customer information stored in each of these different systems must be consolidated. 3 The data is loaded into the data warehouse. loan status. to get a money order. 2 The data is transformed and prepared to be loaded into the data warehouse. Each of these different sets of data is likely gathered by different source systems. you must enter the bank and perform the transaction with a bank teller. and these two services require different operational systems. including the customer's ATM activity. . This consolidation is achieved using the extraction.1 BI Architecture and the MicroStrategy Platform Project Design Guide At an automated teller machine (ATM). and account balances. and similar processes to standardize the format and structure of data. Inc. transformation. filling in incomplete data. The ETL process involves the following steps: 1 Data is gathered from various source systems. transformation. such as a customer's ATM activity. correcting typographical errors. However. If a bank wants to see a unified view of a particular customer.

and then loads the data into the data warehouse. It enables its users to leverage the competitive advantage that the business intelligence provides. The source systems described above. Business intelligence architecture 5 . Analytical processing involves activities such as choosing to see sales data by month and selecting the applicable metric to calculate sales trends. a language developed specifically to interact with RDBMS software. and OLAP cubes. percent-to-total contributions. updated. In combination with MicroStrategy tools and products. trend reporting. In this case. the data that comes from one system may be inconsistent with the data that comes from another system. Inc. whereas data warehouses are usually designed and optimized for analytical processing. Data is rarely inserted. the data warehouse also provides the foundation for a robust online analytical processing (OLAP) system. MicroStrategy does not require that data be stored in a relational database. Data warehouse for data storage and relational design A well-designed and robust data warehouse is the source of data for the decision support system or business intelligence system. Data warehouses are usually based on relational databases or some form of relational database management system (RDBMS) platform. The most common action is the selection of data for analysis. This is in contrast to most © 2007 MicroStrategy. see Storing and analyzing data with alternative data sources. are generally designed and optimized for transactional processing. Excel files. These relational databases can be queried directly with Structured Query Language (SQL). However.Project Design Guide BI Architecture and the MicroStrategy Platform 1 each source system can have its own naming conventions. For more information on accessing data stored in alternative data sources. Most data warehouses have the following characteristics: • Data access is typically read-only. the ETL process extracts the data from the different banking source systems. such as OLTP systems. and profit analysis. page 6. You can integrate different types of data sources with MicroStrategy such as text files. growth patterns. transforms it until it is standardized and consistent. or deleted.

The structure of data in a data warehouse and how it relates to your MicroStrategy environment can be defined and understood through a logical data model and physical warehouse schema. which are referred to as 6 Business intelligence architecture © 2007 MicroStrategy. • • Data is aligned by business subjects. For more information on source systems. see Source systems for data collection. Inc. Defining a project’s logical data model and physical warehouse schema are important steps in preparing your data for a MicroStrategy project. or storage location which stores data that is to be used in MicroStrategy for query. page 4. and loading process. transformation. A data warehouse is populated with data from the existing operational systems using an ETL process. Warehouse Structure for Your Logical Data Model. Data history extends long-term. and Hyperion Essbase. see Chapter 2. and analysis. The following are different data source alternatives which MicroStrategy can integrate with: • OLAP cube sources: In MicroStrategy you can integrate with sets of data from SAP BW. usually two to five years. Microsoft Analysis Services. The Logical Data Model and Chapter 3. A data warehouse can be thought of as one type of data source. which are a common type of data warehouse.1 BI Architecture and the MicroStrategy Platform Project Design Guide OLTP source systems which must be able to handle frequent updates as data is gathered. reporting. A data source is any file. as explained in Extraction. MicroStrategy can also integrate with a number of alternative data sources. . and loading process. Data formats are uniformly integrated using an ETL process (see Extraction. page 4). page 3. For more information on the steps of the project design process. system. and refers specifically to using a database as your data source. transformation. • • Storing and analyzing data with alternative data sources Along with integrating with relational databases.

analyze. As with OLAP cube sources described above. • Text files and Excel files: With MicroStrategy’s Freeform SQL and Query Builder features. page 11—an analytical server optimized for enterprise querying. The MicroStrategy platform A business intelligence platform offers a complete set of tools for the creation. MicroStrategy can integrate with these data sources while simultaneously accessing a relational database effectively. page 13—a highly interactive user environment and a low-maintenance interface for reporting and analysis • • • © 2007 MicroStrategy.Project Design Guide BI Architecture and the MicroStrategy Platform 1 OLAP cube sources. MicroStrategy can report against these alternative data sources while concurrently accessing a relational database to integrate all of your data into one cohesive project. and OLAP analysis MicroStrategy Desktop. and report on data stored in text files and Excel files. Some of the main components of the MicroStrategy platform include: • MicroStrategy metadata. page 8—a repository that stores MicroStrategy object definitions and information about the data warehouse MicroStrategy Intelligence Server. you can query. Inc. Windows-based environment providing a complete range of analytical functions designed to facilitate the deployment of reports MicroStrategy Web and Web Universal. deployment. reporting. Connecting to OLAP Cube Sources. page 11—an advanced. see Appendix B. For more information on using text files and Excel files with the Freeform SQL and Query Builder features. For more information on connecting to and integrating OLAP cube sources in MicroStrategy. support. see the MicroStrategy Advanced Reporting Guide. The MicroStrategy platform 7 . and maintenance of business intelligence applications.

Inc. MicroStrategy metadata MicroStrategy metadata is a repository that stores MicroStrategy object definitions and information about your data warehouse. see the MicroStrategy System Administration Guide. To learn how to administer and tune the MicroStrategy platform. .1 BI Architecture and the MicroStrategy Platform Project Design Guide • MicroStrategy project. The sections that follow provide a brief overview of each of these components. For more detailed information about these and the other components that make up the MicroStrategy platform. which together provide a flexible reporting environment The MicroStrategy platform components work together to provide an analysis and reporting environment to your user community. page 14—where you build and store all schema objects and information you need to create application objects such as reports in the MicroStrategy environment. as shown in the following diagram. refer to the MicroStrategy Installation and Configuration Guide. The information is stored in a proprietary 8 The MicroStrategy platform © 2007 MicroStrategy.

Facts are used to create metrics. The metadata maps MicroStrategy objects—which are used to build reports and analyze data—to your data warehouse structures and data. and so on. groups. attributes. and columns. but are created by a project architect or administrator to configure and govern the platform. • © 2007 MicroStrategy. views.Project Design Guide BI Architecture and the MicroStrategy Platform 1 format within a relational database. configuration objects are created and maintained with the managers in MicroStrategy Desktop within the Administration icon. In general. and so on. These schema objects are often created and managed by a MicroStrategy architect: Facts relate numeric data values from the data warehouse to the MicroStrategy reporting environment. and project administration. which are analytical calculations that are displayed on a report. Facts are discussed in more detail in Chapter 5. As a general rule. The number of units sold is one example of a fact. reports. The MicroStrategy platform 9 . • Configuration objects—Objects that provide important information or governing parameters for connectivity. You can build and manipulate several fundamentally different kinds of objects in MicroStrategy. and other objects which are stored in the Schema Objects folder in MicroStrategy Desktop’s folder list. Inc. For more information about creating and administering configuration objects. metrics. facts. these objects. These objects are not used directly for reporting. Examples include database instances. The Building Blocks of Business Data: Facts. are all created and stored in the metadata repository. which are described below. such as tables. see the MicroStrategy System Administration Guide. users. user privileges. Schema objects—Objects that are created in the application to correspond to database objects. Schema objects include facts. attributes. hierarchies. and hierarchies are three essential pieces to any business intelligence application. report creation in MicroStrategy is achieved through using various types of objects which represent your data as report building blocks. The metadata also stores the definitions of all objects created with MicroStrategy Desktop and Web such as templates. Facts.

see MicroStrategy Web and Web Universal. Inc. The Context of Your Business Data: Attributes. In the example of regional sales in the Southeast. page 13. filters. MicroStrategy metadata also facilitates the retrieval of data from the data warehouse when using MicroStrategy applications.1 BI Architecture and the MicroStrategy Platform Project Design Guide Attributes represent the business context in which fact data is relevant. Application objects include reports. custom groups. One of the most common examples of a hierarchy is a time hierarchy which includes attributes such as Year. Month. Application objects are created using schema objects as building blocks. Attributes are used to define the level at which you want to view the numeric data on a report. These groupings can help users make logical connections between attributes when reporting and analyzing data. documents. • Application objects—Objects used to provide analysis of and insight into relevant data. Southeast represents the attribute or context of the sales data. and prompts. It converts user requests into SQL queries and 10 The MicroStrategy platform © 2007 MicroStrategy. All application objects can be created and maintained in MicroStrategy Desktop. Creating Hierarchies to Organize and Browse Attributes. The metadata enables the sharing of objects across MicroStrategy applications by providing a central repository for all object definitions. MicroStrategy Intelligence Server evaluates the most efficient data retrieval scenario to provide excellent query performance. metrics. Reports and documents can also be created and managed in MicroStrategy Web. and so on. Hierarchies are groupings of attributes so that they can be displayed to reflect their relationships to other attributes. . Hierarchies are discussed in more detail in Chapter 7. Quarter. Information on creating application objects is in the MicroStrategy Basic Reporting Guide and MicroStrategy Advanced Reporting Guide. For more information about MicroStrategy Web. Attributes are discussed in more detail in Chapter 6. templates.

Project Design Guide BI Architecture and the MicroStrategy Platform 1 translates the results of those SQL queries back into MicroStrategy objects such as reports and documents which can be easily analyzed and understood. refer to the MicroStrategy System Administration Guide. You can also add and define your own functions. The MicroStrategy platform 11 . and OLAP analysis. See the MicroStrategy Functions Reference for details about these functions. MicroStrategy Intelligence Server MicroStrategy Intelligence Server is an analytical server optimized for enterprise querying. Windows-based environment providing a complete range of analytical functionality designed to facilitate the deployment of reports. Inc. MicroStrategy Desktop provides the project designer functionality essential to creating both schema and application objects necessary to serve the user communities of both MicroStrategy Desktop and Web. © 2007 MicroStrategy. refer to the MicroStrategy Installation and Configuration Guide. reporting. MicroStrategy Desktop MicroStrategy Desktop is an advanced. The important functions of MicroStrategy Intelligence Server are: • • • • Sharing objects Sharing data Managing the sharing of data and objects in a controlled and secure environment Protecting the information in the metadata MicroStrategy Intelligence Server also provides a library of over 150 different sophisticated mathematical and statistical functions. For information on how to install and configure MicroStrategy Intelligence Server. For a detailed description of MicroStrategy Intelligence Server functionality and tuning recommendations.

For example. Projects are discussed in Chapter 4. Tables in MicroStrategy are references to tables in your data warehouse. hierarchies. Application objects such as reports are used to analyze and provide insight into the relevant data. Facts. Creating and Configuring a Project. For information about the various components that comprise MicroStrategy Desktop. Schema objects allow application objects to interact with the data warehouse to access the data for analysis. filters. One of the other functions of MicroStrategy Desktop is to create projects. Inc. without making any alterations to the database. The following examples highlight some ways in which Desktop allows you to model your business intelligence applications: • Every report or query can automatically benefit from the tables you include in an application. report designers and analysts can deploy them through different interfaces. before application objects are created. The change automatically takes effect in the application. and MicroStrategy Office. graphical interface. schema objects must first exist. MicroStrategy Web. including MicroStrategy Desktop. thus providing access to your data. Desktop is where you can manage application objects such as reports. which are in turn used to design reports. attributes. 12 The MicroStrategy platform © 2007 MicroStrategy. • After reports have been created. This modification is necessary if you have new requirements that require you to add or remove new levels of data in a hierarchy. Desktop provides the ability to modify one aspect of the application without affecting the others. refer to the MicroStrategy Installation and Configuration Guide. and other schema objects are the building blocks for application objects such as reports and documents. It provides a unified environment for creating and maintaining business intelligence projects. facts are used to create metrics. However. and metrics. . You can change the structure of a business hierarchy by re-ordering it.1 BI Architecture and the MicroStrategy Platform Project Design Guide Desktop enables you to model applications using an intuitive. If you need to change how to view your business information or how the data is modeled.

Project Design Guide BI Architecture and the MicroStrategy Platform 1 For more information about creating application objects such as reports in MicroStrategy Desktop. IBM AIX®. are discussed in Project connectivity components. industry-leading analysis. analyze. see the MicroStrategy Installation and Configuration Guide. Oracle®. page 64. Inc. Additional MicroStrategy definitions. quick deployment. The MicroStrategy platform 13 . MicroStrategy Web and Web Universal MicroStrategy Web provides users with a highly interactive environment and a low-maintenance interface for reporting and analysis. © 2007 MicroStrategy. MicroStrategy Web provides ad-hoc querying. For more information about deploying MicroStrategy Web. Sun ONE®. Using the Web interface. making it easy for users to make informed business decisions. and HP-UX Application servers such as BEA WebLogic™. Red Hat® Linux®. For information on advanced Desktop functionality. and Apache Tomcat All web servers and browsers supported by MicroStrategy Web MicroStrategy Intelligence Server must be running for users to retrieve information from your data warehouse using MicroStrategy Web products. refer to the MicroStrategy Basic Reporting Guide. users can access. and share data through any web browser on many operating systems. including many project-related terms. MicroStrategy Web Universal is a version of MicroStrategy Web that provides the added benefits of also working with: • • • Operating systems such as Sun Solaris™. see the MicroStrategy Advanced Reporting Guide. IBM WebSphere®. and rapid customization potential.

A project can contain many types of objects. Reporting objects include metrics. Report objects are covered in the MicroStrategy Basic Reporting Guide and the MicroStrategy Advanced Reporting Guide. and so on. and therefore the set of data available to be analyzed. access control.1 BI Architecture and the MicroStrategy Platform Project Design Guide MicroStrategy project A project is where you build and store all schema objects and information you need to create application objects such as reports in the MicroStrategy environment. Defines the security scheme for the user community that accesses these objects. security roles. Projects are often used to separate data from a data warehouse into smaller sections of related data that fit user requirements. . Contains all reporting objects used to create reports and analyze the data. For example. Security objects include security filters. Conceptually. metrics. reports. privileges. inventory. a project the environment in which all related reporting is done. prompts. Security and other project-level administrative features are discussed in the MicroStrategy System Administration Guide. Contains all schema objects used to interpret the data in those tables. hierarchies. A project also represents the intersection of a data source. • • A project can contain any number of reports in addition to a number of other objects that support simple and advanced reporting requirements. and so on. including application objects such as filters. projects appear one level below project sources in the Folder List. metadata repository. A project: • • Determines the set of data warehouse tables to be used. and 14 The MicroStrategy platform © 2007 MicroStrategy. sales distribution. and user community. In MicroStrategy Desktop. and reports that you can create using schema objects such as attributes and facts. Schema objects are discussed in later chapters in this guide. Schema objects include facts. you may have a project source separated into four different projects with analysis areas such as human resources. filters. and so on. attributes. which together provide a flexible reporting environment. Inc.

Project Design Guide BI Architecture and the MicroStrategy Platform 1 customer satisfaction. © 2007 MicroStrategy. The project design process When you create a project in MicroStrategy Desktop. • The procedures associated with these concepts are explained in Creating the project. In the project. Inc. you can then create schema objects based on the columns and tables in the warehouse. The project design process 15 . The project’s warehouse location is specified by associating it with the appropriate database instance. page 73. This allows all of your users in the human resources department to use the human resources project and they do not have to look through inventory data that they are not interested in. one of the connections you create is between the project and your data warehouse. Some key concepts to understand before you begin creating a project are as follows: • A project is created within a specified metadata repository. determined by the project source through which you create the project.

new user requirements and project enhancements require modification to the initial project design. Designing a project is very rarely a single. which are each covered in the following chapters: Notice that the project design process includes a feedback loop. Inc. 16 The project design process © 2007 MicroStrategy. . linear process.1 BI Architecture and the MicroStrategy Platform Project Design Guide The diagram below shows this high-level view of data modeling. As projects are deployed and tested. and project creation. schema design and implementation. It is important to keep this in mind as you design your project and plan for the next phase of development.

2 2. a simple logical data model for a retail company can organize all necessary © 2007 MicroStrategy. 17 . You need to know where you are going and how to get there. and can also help you decide what you intend to learn from the data. A logical data model is similar in concept to using a map and an itinerary when going on a trip. A logical data model is a logical arrangement of data as experienced by the general user or business analyst. providing a way of organizing data so it can be analyzed from different business perspectives. THE LOGICAL DATA MODEL Conceptualizing your business model and the data on which to report Introduction Devising a model of your business data can help you analyze the structure of the data. You also need a plan that is visible and laid out correctly. This chapter describes one of the major components of data modeling: the logical data model. The logical data model graphically depicts the flow and structure of data in a business environment. For example. Inc. This is different from the physical data model or warehouse schema. how its various parts interact. which arranges data for efficient database use.

2 The Logical Data Model Project Design Guide facts by store. but the blueprint remains the same. a logical data model may or may not have any explicitly defined dimensions. While a multidimensional data model must have at least one dimension. logical data modeling is similar to multidimensional data modeling. Logical data models are independent of a physical data storage device. The scope and complexity of a logical data model depends on the requirements of the reporting needs of the user community and the availability of source data. As the MicroStrategy platform does not require you to define dimensions explicitly. the word logical is a more accurate term than multidimensional. the more complex the logical data model becomes. If you are familiar with multidimensional data modeling. and you do not need to start over completely. The more sophisticated and complex the reporting requirements and source data. Inc. 18 © 2007 MicroStrategy. The reason that a logical data model must be independent of technology is because technology is changing so rapidly. . This is the key concept of the logical data model. What occurs under the logical data model can change with need or with technology. product. which are three common business perspectives typically associated with a retail business. and time.

characteristics. conceptual.Project Design Guide The Logical Data Model 2 The logical data modeling process produces a diagram similar to the one shown in the following diagram: A logical data model represents the definition. This process can help you think about the various elements that compose your company’s business data and how those elements relate to one another. 19 . Inc. © 2007 MicroStrategy. and relationships of data in a technical. or business environment.

. as shown in the following diagram: This chapter provides conceptual information about logical data models. page 22 Hierarchies: Data relationship organization. page 25 20 © 2007 MicroStrategy.2 The Logical Data Model Project Design Guide Devising a logical data model for your business intelligence environment allows you to then consider various ways to physically store the business data in the data warehouse. the elements that exist within them. This is usually one of the first steps in designing a project. page 21 Attributes: Context for your levels of data. and also general instructions and guidelines for creating these models. Inc. A logical data model is a graphic representation of the following concepts: • • • Facts: Business data and measurements.

To those familiar with SQL.EMP_ID) WHERE a22.ORDER_AMT) EMP_NAME FROM ORDER_FACT a21 JOIN LU_EMPLOYEE a22 ON (a21. Sales. data.EMP_ID = a22.CALL_CTR_ID in (5. Inventory. Facts are the building blocks used to create business measurements or metrics from which to derive insight into your data. In a data warehouse. Inc. and Account Balance are some examples of facts you can use as business measurements. 9.Project Design Guide The Logical Data Model 2 Facts: Business data and measurements One of the first things you do when you create a logical data model is to determine the facts. Conceptually. The rest of data modeling consists mostly of providing context for the data that facts provide access to. 12) © 2007 MicroStrategy. They can come from different source systems and they can have different levels of detail. facts are schema objects that relate data values (typically numeric data) from the data warehouse to the MicroStrategy reporting environment. you can think of facts as business measurements. In MicroStrategy. Facts: Business data and measurements 21 . facts generally represent the numeric columns in database tables on which you perform SQL aggregations. or variables that are typically numeric and suitable for aggregation. while you capture stock and inventory data in another system and track it weekly. Facts allow you to access data stored in a data warehouse and they form the basis for the majority of users’ analysis and report requirements. you can capture sales data in one system and track it daily. facts exist as columns within the fact tables. For example. the ORDER_AMT column in the warehouse may correspond to the Order Amount fact in the MicroStrategy environment: SELECT sum(a21. in the following SQL statement. such as SUM and AVG. For example.

000. Fore a more complete discussion about facts. the attributes must be identified. if your sales data is stored at the day level. which are business calculations often built using facts. regional.ORDER_AMT) represents a metric. To those familiar with SQL. such as national. or a single store Attributes provide context and levels for convenient summarization and qualification of your data to help answer the type of questions listed above. These columns are used to qualify and group fact data. For example.2 The Logical Data Model Project Design Guide In addition. while ORDER_AMT is the fact. local. a Month attribute allows you to see the same sales data summarized at the month level. If you were informed that your company had sales of $10. attributes generally represent the non-numeric and non-aggregatable columns in database tables. The Building Blocks of Business Data: Facts. To make the sales figure meaningful. Metrics are discussed in detail in the MicroStrategy Basic Reporting Guide. refer to Chapter 5. They are used to answer business questions about facts at varying levels of detail. you would need to know more about the source of that sales figure such as: • • • • A time frame for the sales Who and how many people contributed to the sales total What products were sold from which departments The scope of the sale. Inc. Attributes allow you to answer questions about a fact and provide a context for reporting and analyzing those facts. 22 Attributes: Context for your levels of data © 2007 MicroStrategy. Attributes: Context for your levels of data After the facts are determined. . sum(a21. you can gather little useful information. For example. consider the sales figures of your company.

a Customer attribute allows you to see sales data at the customer level and you can qualify on the elements of the Customer attribute to see sales data for groups such as customers with last names beginning with the letter h. the MONTH_ID column in the warehouse maps to the Month attribute in the MicroStrategy environment: SELECT a11. For a complete discussion about attributes. Inc.MONTH_ID MONTH_ID. © 2007 MicroStrategy.MONTH_ID = a12.MONTH_ID) WHERE a11.MONTH_ID Attribute forms contain additional descriptive information about a given attribute and are discussed in terms of the logical data model in Attribute forms. Attribute elements: Data level values Attribute elements are the unique values or contents of an attribute. The Context of Your Business Data: Attributes.200203) GROUP BY al1. page 36. attributes are used to build the report and the attribute elements are displayed in rows or columns on the executed report. For example.TOT_DOLLAR_SALES) DLRSALES FROM MNTH_CATEGORY_SLS a11 join LU_MONTH a12 on (a11. For example. 2005 and 2006 are elements of the Year attribute while New York and London are elements of the City attribute. Attributes: Context for your levels of data 23 . On a report.Project Design Guide The Logical Data Model 2 For example. in the following SQL statement. max(a12. sum(a11. refer to Chapter 6. Attribute elements also allow you to qualify on data to retrieve specific results.MONTH_DESC) MONTH_DESC.200202.MONTH_ID in (200201.

By recognizing and understanding the elements of an attribute. Attribute relationships. there is no interaction between data. The relationships give meaning to the data by providing logical associations of attributes based on business rules.2 The Logical Data Model Project Design Guide The following diagram shows some examples of attributes and attribute elements. A child must always have a parent and a parent can have multiple children. . The parent attribute is at a 24 Attributes: Context for your levels of data © 2007 MicroStrategy. are essential to the logical data model. they are necessary in understanding attribute relationships. Attribute relationships Building an effective project in MicroStrategy requires you. which are associations between attributes that specify how attributes are connected. you can better design your data model and project. Every direct relationship between attributes has two parts—a parent and a child. and therefore no logical structure. as well as how each of them relates to the other attributes. Inc. Without relationships. as the project designer. Although attribute elements are not included in the logical data model. Attribute elements are discussed in more detail in Unique sets of attribute information: Attribute elements. page 140. to have a solid understanding of all the attributes in the project.

Project Design Guide The Logical Data Model 2 higher logical level than the child is. One year has many quarters and both attributes are in the Time hierarchy. and Day to form the Time hierarchy. Attributes in one hierarchy are not directly related to attributes in another hierarchy. Year and Quarter are attributes that are usually directly related to each other. © 2007 MicroStrategy. Usually the best design for a hierarchy is to organize or group attributes into logical business areas. which represent the level at which a fact is stored. For example. Month. Therefore. Year and Customer are attributes that are usually not in the same hierarchy and are not directly related to each other. if you want to create a report that shows information about customer purchases in a particular year. and hierarchies are related and form a complete logical data model is shown in the section Sample data model. page 26 below. attributes. the fact is a customer purchase. Attributes are either related or unrelated to each other. Year and Customer are related through a fact. For example. Year is the parent attribute and Quarter is the child. Inc. along with more detailed information about attribute relationships. in a relationship between Year and Quarter. A graphical example of how facts. page 159. Hierarchies: Data relationship organization 25 . In this case. Examples of related and unrelated attributes. In a logical data model. are discussed in Attribute relationships. hierarchies contain attributes that are directly related to each other. you can group the attributes Year. They are identified by multiple attributes. Hierarchies: Data relationship organization Hierarchies in a logical data model are ordered groupings of attributes arranged to reflect their relationship with other attributes. It is the existence of a fact that ties the Time hierarchy to the Customer hierarchy. there must be some way to determine how these two attributes are related. However. For example. facts exist at the intersection of hierarchies.

Sample data model When all of the components are placed in a single diagram—facts. refer to Chapter 7. Some of the things to consider when creating a logical data model are • • • User requirements Existing source systems Converting source data to analytical data 26 Sample data model © 2007 MicroStrategy. attributes. and hierarchies—a logical data model begins to take shape. The following diagram is an example of a logical data model: Building a logical data model The first thing you must do before creating a logical data model is study the factors that influence your design.2 The Logical Data Model Project Design Guide For a complete discussion about hierarchies. relationships. . Inc. Creating Hierarchies to Organize and Browse Attributes.

However. you can derive additional data not found in the source systems. © 2007 MicroStrategy. Your user community can consist of people with vastly different requirements. In some cases. In some cases. Building a logical data model 27 . User requirements are an important part of the initial project design process. to satisfy user requirements. Lower-level managers are typically more interested in data about their particular areas of responsibility. additional user requirements can be encountered after deploying a project as users encounter areas for enhancement. These managers may want reports about their specific region or store over short-and long-terms. Sometimes. Developing such a model involves the following: • • • Identification of user requirements Design of solutions Evaluation of those solutions Logical data modeling is a reiterative process. lack of data in the source systems can limit user requirements.Project Design Guide The Logical Data Model 2 User requirements The primary goal of logical data modeling is to meet the needs of your users’ reporting requirements. as explained in Existing source systems. For example. page 28. you must consider all the potential users and how to accommodate their varied requirements. new user requirements may require you to modify the logical data model to better support the type of analysis and the retrieval of data that users demand. Inc. When creating the logical data model. where additional questions and concerns arise with each draft of the logical data model. company executives are typically interested in overall trends and may want reports showing data aggregated across the company and over a long period of time.

this does not mean that it should not be included in the logical data model. most logical models begin with an examination of the source data once existing systems are developed and 28 Building a logical data model © 2007 MicroStrategy. In this case.2 The Logical Data Model Project Design Guide Existing source systems Understanding what data is available is an important step in creating a logical data model. Although some data may not exist in a source system. although data is stored at a daily level in the source system. Additionally. and relationships. You must determine what facts and attributes in the existing data are necessary for supporting the decision support requirements of your user community. While a review of your data is initially helpful in identifying components of your logical data model. Existing data is usually abundant. everything you find in the source data does not necessarily need to be included in the logical data model. Converting source data to analytical data If there are no existing systems and you are just beginning your data warehousing initiative. . an insurance company’s transactional system records data by customer and city. However. State and region do not appear in the existing source data and so you need to extract them from another source. Conversely. users also want to see data at the monthly or yearly level. attributes. but a substantial portion of the work in creating a suitable logical data model involves determining what additional components are required to satisfy the needs of the user community. but the business analysts want to see data for different states or regions. consisting of a large number of facts and attributes. For example. The existing data should suggest a number of facts. you can build the logical data model based heavily on current user requirements. Inc. you may not find all the facts and attributes to meet your needs within the data itself. User requirements should drive the decision on what to include and what to exclude. you can plan additional attributes to provide the levels at which you intend to analyze the facts in your data model.

page 30 Step 3: Determine attribute relationships. A product inventory fact. however. Building a logical data model 29 . can be © 2007 MicroStrategy. most OLTP systems have an entity relationship diagram (ERD). for a particular item. A logical data model is similar in concept to an ERD. the steps to create a logical data model are as follows: • • • • Step 1: Identify the facts. make a list of all data that can be represented as facts in MicroStrategy. sales facts are often stored at the store. in retail models. on a particular day. sales and profit figures. determine the business level at which each fact is recorded. Step 1: Identify the facts Using your existing data. page 31 Step 4: Define hierarchies. item. The source data usually has some sort of documented physical structure. After you have all the facts listed. page 32 The details in these steps are related to using an existing source system. for example. or day level. page 29 Step 2: Identify the attributes. Whether you start from nothing or have an existing source system to use.Project Design Guide The Logical Data Model 2 implemented. However. Remember that facts can be calculated and are usually numeric and aggregatable. For example. Inc. An ERD provides a graphical representation of the physical structure of the data in the source system. meaning that a sale takes place in a particular store. For example. in this guide the logical data model also takes into account how your data can be integrated into MicroStrategy to develop a business intelligence solution. which lets you easily recognize tables and columns and the data stored in those columns.

30 Building a logical data model © 2007 MicroStrategy. page 30). Inc. Step 2: Identify the attributes Uncover attributes by considering the levels at which you would like to view the facts on your reports. your users are interested in analyzing data at more than just at the day level.2 The Logical Data Model Project Design Guide stored at the region. This information may only be apparent to you after you deploy your project and you determine that a high percentage of your users are viewing sales data at the yearly level. These business levels become the attributes in your logical data model (see Step 2: Identify the attributes. or week level. To improve performance and meet the requirements of the majority of your users. you can include an aggregate table that stores sales data at the year level (see Using summary tables to store data: Aggregate tables. . item. Start by looking at the levels at which each fact is recorded and build from there. page 241). They also want to view their data at the year. and week levels. month. but such considerations should be taken into account during your initial project design initiative. in the existing data there may be fact data recorded only at the day level. For example. This analysis requires MicroStrategy to aggregate the sales data from the day level to the year level. However. This practice is sometimes a reaction to user requirements established after project deployment. You can then design a Year attribute for your project.

Only include facts and attributes that can serve your user community. and for every month. Year has a one-to-many relationship to Month. Additionally. Inc. you should determine the type of relationship. for every year. For example. and Month has a one-to-many relationship to Day. From the reverse perspective the same relationship specifies that. Building a logical data model 31 . Logical data modeling is an iterative process. if necessary. It is usually unnecessary to bring all data from the source system into the analytical environment. for a number of dates (in a © 2007 MicroStrategy. you can always add more attributes and facts later. several dates exist. This one-to-many relationship specifies that. and so on. Primary Competitor. Step 3: Determine attribute relationships Once you have identified your data to be defined as attributes in MicroStrategy. These attributes are all related to the Opportunity attribute because they all answer questions about opportunity information. For example.Project Design Guide The Logical Data Model 2 Be careful not to include more facts and attributes than necessary. several months exist. you must then determine which attributes are related to each other. Opportunity Open Date. in the Sales Force Analysis Module of the MicroStrategy BIDK opportunity information is stored with an Opportunity attribute which is directly related to the attributes Opportunity Close Date. in the diagram below.

Jan 2006. only one month exists (in a form such as Dec 2005). In the context of a logical data model.2 The Logical Data Model Project Design Guide form such as 12/01/2005). only one year exists. Consider the Year to Month attribute relationship type of one-to-many. Jan. think of hierarchies as logical arrangements of attributes into business areas. You can 32 Building a logical data model © 2007 MicroStrategy. If you have documentation for the existing data. Attribute relationships are discussed in detail in Attribute relationships. page 24. If you define the attribute Month as simply the month name (Dec. This example may not accurately define how you store time information. Step 4: Define hierarchies Hierarchies provide a structure for your data and can help your users easily and intuitively browse for related attributes and include them in a report. you can organize all time-related attributes into the Time hierarchy. For example. such as an ERD. . and so on) and not directly connected to a year (Dec 2005. and so on) then the relationship would become many-to-many. and for a number of months. Inc. it is likely that the documentation provides some additional details about the nature of the data and any inherent relationships.

Inc. and make for a more robust logical data model. in which case you may have one big hierarchy. Logical data modeling conventions 33 . Again. Depending on the complexity of your data and the nature of your business.Project Design Guide The Logical Data Model 2 have a Customer hierarchy containing all attributes related to your customers and a Supplier hierarchy for all attributes related to supplier data. Logical data modeling conventions There are numerous logical data modeling conventions you can use to enhance your logical data model. you may have very few hierarchies or you may have many. It is possible that all the data is directly related. help with system maintenance. the requirements of your user community should help you determine what hierarchies are necessary. These include: • • • Unique identifiers Cardinalities and ratios Attribute forms These logical modeling conventions can provide cues for system optimization opportunities. Although the user community is the ultimate beneficiary of a © 2007 MicroStrategy.

Each convention adds more information about the data to the logical data model. and advanced report designers.2 The Logical Data Model Project Design Guide well-optimized and maintained system. Unique identifiers An additional modeling convention is to add unique identifiers for each attribute and fact. Some attributes rely on more than 34 Logical data modeling conventions © 2007 MicroStrategy. Remember that facts are usually identified by multiple attributes and therefore will have multiple unique identifiers. administrators. when applicable. Unique identifiers denote the key that maps an attribute to its source data in the source system. This additional information can be particularly useful to a person learning about the system. Inc. The following diagram shows a logical data model with unique identifiers added. page 42). This information can help define primary keys in the physical warehouse schema (see Uniquely identifying data in tables with key structures. . these conventions are primarily intended for project designers.

note the Item attribute. Cardinalities and ratios Another enhancement to the logical data model is the addition of cardinalities and ratios for each attribute. For example. which are discussed in Chapter 7. Logical data modeling conventions 35 .Project Design Guide The Logical Data Model 2 one ID column to identify its elements. which requires both the Item_ID and Class_ID columns to uniquely identify its elements. Cardinality is the number of unique elements for an attribute and ratios are the ratios between the cardinalities of related attributes. Ratios can be particularly helpful when trying to © 2007 MicroStrategy. Cardinalities help the database administrator estimate the size of the data warehouse and help project designers determine the best paths for users to navigate through the data using hierarchies in MicroStrategy. Inc. Creating Hierarchies to Organize and Browse Attributes.

The following diagram shows a logical data model which includes cardinalities and ratios. it is impossible to determine how many customers have different dates of birth in the warehouse. 36 Logical data modeling conventions © 2007 MicroStrategy. this is because this information varies and is unpredictable. Attribute forms Including attribute forms in your logical data model can help you get a more complete view of all of the information that is made available in your project.2 The Logical Data Model Project Design Guide decide where creating aggregate tables will be most effective. This additional information can be invaluable to database administrators and project designers. For example. Note the cardinalities in the upper right corner of each attribute rectangle and the ratios next to some of the relationships between attributes. Inc. Also note that the cardinality of some attributes such as Date of Birth are unknown. .

and in the data. you could have included each of these pieces of information as separate attributes. In reality. Logical data modeling conventions 37 . When a one-to-one relationship exists between an attribute and one of its descriptions. you create an attribute called Customer to represent customers in your system. Each element of the Customer attribute represents a different customer. and it is part of the Customer hierarchy. these attributes simply provide additional information about the Customer attribute. you can model these additional © 2007 MicroStrategy. Inc. they do not represent different levels within the Customer hierarchy. For example. you store the following information about your customers: • • • • • Customer number (some numeric code used to uniquely identify customers) First name Last name Address Email address In your logical data model. each with a one-to-one relationship to the Customer attribute. though.Project Design Guide The Logical Data Model 2 Attribute forms contain additional descriptive information about a given attribute.

2

The Logical Data Model

Project Design Guide

pieces of descriptive information as attribute forms. The following diagram shows how you add attribute forms to a logical data model:

Attribute forms are discussed in terms of their role in MicroStrategy in Column data descriptions and identifiers: Attribute forms, page 143.

38 Logical data modeling conventions

© 2007 MicroStrategy, Inc.

3
3.

Physical Warehouse Schema

WAREHOUSE STRUCTURE FOR YOUR LOGICAL DATA MODEL

Introduction
As discussed in the previous chapter, the logical data model can help you think about the logical structure of your business data and the many relationships that exist within that information. The physical warehouse schema is based on the logical data model. It is a detailed graphic representation of your business data as it is stored in the data warehouse. The physical warehouse schema organizes the logical data model in a method that makes sense from a database perspective. In contrast, the logical data model is a logical arrangement of data from the perspective of the general user or business analyst. For more information on what a logical data model is and how to create one, see Chapter 2, The Logical Data Model. The logical data model is only concerned with logical objects of the business model, such as Day, Item, Store, or Account. Several physical warehouse schemas can be derived from the same logical data model. The structure of the schema
39

© 2007 MicroStrategy, Inc.

3

Warehouse Structure for Your Logical Data Model

Project Design Guide

depends on how the data representing those logical objects are to be stored in the warehouse. For example you can store logical objects in the same table, in separate tables, duplicated across several tables, or in some other arrangement. While the logical data model tells you what facts and attributes to create, the physical warehouse schema tells you where the underlying data for those objects is stored. The physical warehouse schema describes how your data is stored in the data warehouse and how it can be retrieved for analysis. Creating a physical warehouse schema is the next step in organizing your business data before you create a project, as shown below:

The key components that make up the physical warehouse schema are columns and tables. Columns and tables in the physical warehouse schema represent facts and attributes from the logical data model. The rows in a table represent attribute elements and fact data.

40

© 2007 MicroStrategy, Inc.

Project Design Guide

Warehouse Structure for Your Logical Data Model

3

Columns: Data identifiers and values
Columns are fields in the warehouse that contain attribute and fact data. The types of columns are: • ID columns contain attribute element identification codes. These codes are typically numeric because computers can process numbers much more rapidly than text. All attributes must have an ID column. Description columns contain descriptions (text or numeric) of attribute elements. Description columns are optional. An ID column can serve a dual purpose as both an ID and description. Date is one example of an attribute that usually does not have a description column. The majority of attributes typically have an ID column and at least one description column. If an attribute has many attribute forms—additional descriptive information about a given attribute—they are represented by additional description columns. • Fact columns contain fact data.

Tables: Physical groupings of related data
The different types of tables are • • • Lookup tables: Attribute storage, page 43 Relate tables: A unique case for relating attributes, page 45 Fact tables: Fact data and levels of aggregation, page 46

While each type of table may function differently within the data warehouse, each type of table can be assigned a primary key that uniquely identifies the elements within the given table.

© 2007 MicroStrategy, Inc.

Columns: Data identifiers and values

41

3

Warehouse Structure for Your Logical Data Model

Project Design Guide

Uniquely identifying data in tables with key structures
In relational databases, each table has a primary key that creates a unique value identifying each distinct data record or row. This applies to every type of table within the data warehouse. The types of keys that can be assigned to a table include: • • Simple key requires only one column to identify a record uniquely within a table. Compound key requires multiple columns to identify a unique record.

Which key structure you use to identify a unique attribute in a table depends on the nature of your data and business requirements. The following diagram shows how the different key structures can be used to identify a calling center.

The simple key shows how you can identify a calling center with only its Call_Ctr_id. This means that every calling center has its own unique ID. In the compound key, calling centers are identified by both Call_Ctr_id and Region_id. This means that two calling centers from different regions can share the same Call_Ctr_id. For example, there can be a calling center with ID 1 in region A, and another calling center with ID 1 in region B. In this case, you cannot identify a unique calling center without knowing both the Call_Ctr_id and the Region_id. Simple keys are generally easier to handle in the data warehouse than are compound keys because they require less storage space and they allow for simpler SQL. Compound

42 Tables: Physical groupings of related data

© 2007 MicroStrategy, Inc.

Project Design Guide

Warehouse Structure for Your Logical Data Model

3

keys tend to increase SQL query complexity, query time, and required storage space. However, compound keys have a more efficient ETL process. Which key structure you use for a particular attribute depends entirely on the nature of the data and your system. Consider what key structures work best when creating lookup tables in the physical warehouse schema.

Lookup tables: Attribute storage
Lookup tables are the physical representation of attributes. They provide the ability to aggregate data at different levels. Lookup tables store the information for an attribute in ID and description columns (see Columns: Data identifiers and values, page 41). Depending on how you choose to organize the physical schema, a lookup table can store information for one or more related attributes. If a table only stores data about one attribute, it is said to be a normalized table. If a table holds data about multiple attributes, it is said to be a denormalized table. The following diagram shows the different ways in which you can organize the same attribute information. Notice that the denormalized table holds the exact same data as the normalized tables. While the denormalized table consolidates

© 2007 MicroStrategy, Inc.

Tables: Physical groupings of related data

43

3

Warehouse Structure for Your Logical Data Model

Project Design Guide

information about attributes within one table, the normalized tables each contain only a subset of all of the information about the attributes.

You can use either structure for any table in the physical warehouse schema, though each structure has its advantages and disadvantages, as explained in the following sections and outlined in the table in Schema type comparisons, page 60.

Attribute relationships and lookup table structure
Attribute relationships are a major factor in determining the structure of lookup tables in a physical warehouse schema. In general, the following guidelines apply: • One-to-one relationships usually denote the existence of an attribute form. The description column of an attribute form should simply be included as an additional column in the attribute’s lookup table. Many-to-many relationships usually require the use of a relate table distinct from either attribute lookup table. A relate table should include the ID columns of the two attributes in question. For more information on how to use relate tables, see Relate tables: A unique case for relating attributes, page 45.

44 Tables: Physical groupings of related data

© 2007 MicroStrategy, Inc.

Project Design Guide

Warehouse Structure for Your Logical Data Model

3

Relate tables: A unique case for relating attributes
While lookup tables store information about attributes, relate tables store information about the relationship between two attributes. Relate tables contain the ID columns of two or more attributes, thus defining associations between them. Relate tables are often used to create relationships between attributes that have a many-to-many relationship to each other. With attributes whose direct relationship is one-to-many—in which every element of a parent attribute can relate to multiple elements of a child attribute—you define parent-child relationships by placing the ID column of the parent attribute in the lookup table of the child attribute. The parent ID column in the child table is called a foreign key. This technique allows you to define relationships between attributes in the attributes’ lookup tables, creating tables that function as both lookup tables and relate tables as shown in the following diagram:

In the case of a many-to-many relationship—in which multiple elements of a parent attribute can relate to multiple elements of a child attribute—you must create a separate relate table as shown in the following diagram:

© 2007 MicroStrategy, Inc.

Tables: Physical groupings of related data

45

3

Warehouse Structure for Your Logical Data Model

Project Design Guide

Fact tables: Fact data and levels of aggregation
Fact tables are used to store fact data. Since attributes provide context for fact values, both fact columns and attribute ID columns are included in fact tables. Facts help to link indirectly related attributes. The attribute ID columns included in a fact table represent the level at which the facts in that table are stored. For example, fact tables containing sales and inventory data look like the tables shown in the following diagram:

For more details on the level of aggregation of your fact data, see Fact table levels: The context of your data, page 48.

46 Tables: Physical groupings of related data

© 2007 MicroStrategy, Inc.

Tables: Physical groupings of related data 47 .Project Design Guide Warehouse Structure for Your Logical Data Model 3 Base fact columns versus derived fact columns The types of fact columns are base fact columns and derived fact columns: • Base fact columns are represented by a single column in a fact table. The following diagram shows an example of a fact table and base fact columns: • Derived fact columns are created through a mathematical combination of other existing fact columns. and Discount fact columns. the derived fact exists in several tables. The following diagram shows an example of a fact table and how you can create a derived fact column from base fact columns: In the example. Unit_Price. Inc. including Item_Mnth_Sls and City_Ctr_Sls. © 2007 MicroStrategy. Also. the derived fact Tot_Dollar_Sales is created using the Qty_Sold.

page 97. the following image shows two facts with an Item/Day/Call Center level. For more information on the different types of facts in MicroStrategy and how they are defined.3 Warehouse Structure for Your Logical Data Model Project Design Guide Because facts in different fact tables are typically stored at different levels. For example. see How facts are defined. derived fact columns can only contain fact columns from the same fact table. The Sales and Inventory facts can be analyzed at the item. For more information on what metrics are and how to create them. The Item_id. The disadvantage is that derived fact columns require more storage space and more time during the ETL process. There are advantages and disadvantages to consider when deciding if you should create a derived fact column. and call center levels because those levels exist as ID columns in the fact table. 48 Tables: Physical groupings of related data © 2007 MicroStrategy. You can create the same type of data analysis in MicroStrategy with the use of metrics. which translates into simpler SQL and a speedier query at report run time. The advantage of storing derived fact columns in the warehouse is that the calculation of data is previously performed and stored separately. see the MicroStrategy Advanced Reporting Guide. and Call_Ctr_id columns in the table above represent practical levels at which sales and inventory data can be analyzed on a report. day. . Inc. Day_id. Metrics allow you to perform calculations and aggregations on fact data from one or more fact columns. Fact table levels: The context of your data Facts and fact tables have an associated level based on the attribute ID columns included in the fact table.

Inc. this is because analyzing inventory data at the customer level does not result in a practical business calculation.Project Design Guide Warehouse Structure for Your Logical Data Model 3 You do not need to include more lookup column IDs than are necessary for a given fact table. as shown in the diagram below. For example. they store the same data: information about regions. Tables: Physical groupings of related data 49 . The levels at which facts are stored become especially important when you begin to have complex queries with multiple facts in multiple tables that are stored at levels different from one another. Fact tables should only include attribute ID columns that represent levels at which you intend to analyze the specific fact data. This is called heterogeneous column naming. Though the Region_id and Reg_id columns have different names. You must be able to support fact reporting at the business levels which users require. Homogeneous versus heterogeneous column naming Suppose the data warehouse has information from two source systems. notice that the table above does not include the Customer_id column. and when a reporting request involves still a different level. © 2007 MicroStrategy. These naming inconsistencies occur because source systems use different naming conventions to name the data they collect. and in one source system regions are identified by column name Region_id and in the other the column name is Reg_id.

you must map both the Region_id and Reg_id columns to the attribute so all information about regions is calculated correctly and displayed on reports when the Region attribute is used. it is a good idea for columns that contain the same data to have the same column name. consider the heterogeneous column names that may exist in your source systems. if you create a Region attribute given the tables in the example above. For consistency. In this case. as shown in the following diagram: 50 Tables: Physical groupings of related data © 2007 MicroStrategy. This explains why the same information about regions is represented by two columns with different names. In order for reports to retrieve accurate and complete results. This is called homogeneous column naming. . When you define facts and attributes in MicroStrategy Desktop. Inc.3 Warehouse Structure for Your Logical Data Model Project Design Guide The data for the Lookup_Region table came from a different source system than the data for the Lookup_Call_Ctr and the source systems have different naming conventions. heterogeneous columns must be mapped to their corresponding facts and attributes. the Region_ID column has the same name in both tables. For example.

is used to organize the physical schema to enhance query performance while maintaining and acceptable amount of data storage space. How you choose to structure the warehouse depends on the nature of your data. Inc. as shown below: Schema types: Data retrieval performance versus redundant storage There are many ways to structure your data warehouse and no method is inherently right or wrong. it is also possible for the same fact data to exist in different fact tables. one of the schema types.Project Design Guide Warehouse Structure for Your Logical Data Model 3 Just as it is possible for the same attribute data to exist in different lookup tables. 51 . or a combination of them. These schema types are: • • • Highly normalized schema: Minimal storage space Moderately normalized schema: Balanced storage space and query performance Highly denormalized schema: Enhanced query performance Schema types: Data retrieval performance versus redundant storage © 2007 MicroStrategy. Typically. A fact column may or may not have the same name in different tables. and the requirements of your user community. the available storage space.

Inc. you should keep in mind the following concepts: • Redundant data can cause a couple of drawbacks. such as Call_Ctr_desc. Fact table keys consist of attribute keys relevant to the level of data stored in the table. The sections below are not meant to be an exhaustive list of all possible schema types. data only has to be updated in a single place. Data redundancy also makes updating data a more intensive and difficult process because data resides in multiple places. the sections below are meant to give a description of the most common or general schema types that are used to develop a physical warehouse schema. • Joins are SQL operations that are required to combine two tables together in order to retrieve data. see Using summary tables to store data: Aggregate tables. With no data redundancy. but as with any operation performed on your data warehouse. such as Call_Ctr_id. The schema examples that follow show data at the Item/Call Center/Date level. and 52 Schema types: Data retrieval performance versus redundant storage © 2007 MicroStrategy. page 241). The most obvious drawback is that redundant data requires more storage space to hold the same amount of data as a system with no redundancy. However.3 Warehouse Structure for Your Logical Data Model Project Design Guide In each of these schemas a base fact table and any number of aggregate fact tables are used (For more information on aggregate fact tables. These operations are necessary. In highly normalized schemas. and Region_id. Dist_Ctr_desc. lookup tables contain unique developer-designed attribute keys. the number of joins required to build your queries affects the performance of those queries. Dist_Ctr_id. as shown in the figure below. When comparing the different schema types. . • Highly normalized schema: Minimal storage space The following diagram is an example of a highly normalized schema. They also contain attribute description columns.

© 2007 MicroStrategy. Also.Project Design Guide Warehouse Structure for Your Logical Data Model 3 Region_desc. Inc. Schema types: Data retrieval performance versus redundant storage 53 . such as Dist_Ctr_id in the Lookup_Call_Ctr table. the lookup table for an attribute contains the ID column of the parent attribute.

therefore. This schema type has the same basic structure as the highly normalized schema. numerous joins are required to retrieve information about the higher-level tables. However. .3 Warehouse Structure for Your Logical Data Model Project Design Guide The following diagram shows what physical lookup tables look like in the warehouse: One benefit of using a highly normalized schema is that it requires minimal storage space in the warehouse because of it uses smaller lookup tables than the other schema types. Moderately normalized schema: Balanced storage space and query performance The following diagram shows an example of a moderately normalized schema. When accessing higher-level lookup tables such as Lookup_Region in the example above. there is a drawback to using only small tables in the data warehouse. The difference 54 Schema types: Data retrieval performance versus redundant storage © 2007 MicroStrategy. This is because each table contains only a small amount of information about a given attribute. multiple tables must be joined until the required column is found. Inc.

Region_id is included in the Lookup_Call_Ctr table. Schema types: Data retrieval performance versus redundant storage 55 . Inc. For example.Project Design Guide Warehouse Structure for Your Logical Data Model 3 here is the higher-level attribute ID columns are present within all tables of related attributes. © 2007 MicroStrategy.

3 Warehouse Structure for Your Logical Data Model Project Design Guide The fact table structure within a moderately normalized schema is identical to that of the highly normalized schema. fewer joins are required when retrieving information about an attribute. Using a moderately normalized schema provides a balance between the pros and cons of normalized and denormalized schema types. the tables within this type of schema take up some redundant storage space in the warehouse. The following diagram shows what the physical lookup tables look like in the warehouse. However. With 56 Schema types: Data retrieval performance versus redundant storage © 2007 MicroStrategy. since some tables contain the same ID columns (as shown above with the Region_ID column). Inc. Because the ID columns of both the parents and grandparents of an attribute exist in multiple tables. . Highly denormalized schema: Enhanced query performance The following diagram is an example of a highly denormalized schema. A highly denormalized schema has the same basic structure as the other two schema types.

Project Design Guide Warehouse Structure for Your Logical Data Model 3 this type. For example. not only are higher-level attribute ID columns present within all related tables. © 2007 MicroStrategy. Using a highly denormalized schema further reduces the joins necessary to retrieve attribute descriptions. However. you can include the descriptions of Call Center. this schema type requires the largest amount of storage space within the warehouse because of its large lookup tables. but the description columns are present as well. For example. High denormalized schemas also cause the highest level of data redundancy. Schema types: Data retrieval performance versus redundant storage 57 . Distribution Center. and Region along with Sales Dollars in the same report while only having to join the Lookup_Call_CTR and Fact_Sales tables. Region_desc is included in the Lookup_Call_Ctr table. Inc. This is possible because Lookup_Call_CTR contains all information (including description data) for Call Center as well as for Distribution Center and Region.

geography) consists of several lookup tables. . each hierarchy (for example. star schemas can often 58 Schema types: Data retrieval performance versus redundant storage © 2007 MicroStrategy. only one lookup table is used to contain all of the attribute IDs and description columns for a given hierarchy. the amount of join operations are reduced by using a star schema. As with a highly denormalized schema type.3 Warehouse Structure for Your Logical Data Model Project Design Guide Star schema: Consolidating lookup tables When using the highly denormalized schema. as shown below. it is possible to eliminate most of the lookup tables and leave just a few. Arranging the warehouse schema this way produces a star schema. A star schema can also reduce the amount of storage space necessary in a highly denormalized schema. Inc. In a star schema. Recall that in a highly denormalized schema. However. the lookup tables are consolidated so that every attribute ID and description column for a given hierarchy exists in one table. however. as shown below: As with any schema type model there are advantages and disadvantages to using a star schema. In this type of schema.

if you have the storage space necessary to accommodate data in a star schema it may seem that you would never want to normalize your schema. slower query performance. For example. Design trade-offs 59 . Each of these categories affects the others. Design trade-offs Constructing a logical data model and physical warehouse schema is an iterative process of compromises and trade-offs. you will have to create an extensive data model and schema to support those requirements. If you try to satisfy every single user requirement from the simplest to the most complex.Project Design Guide Warehouse Structure for Your Logical Data Model 3 require large lookup tables that can take a more time to search than the smaller tables that are used in the other schema types. SQL queries directed at a consolidated table require the use of a DISTINCT operator and these types of queries tend to be very © 2007 MicroStrategy. Inc. and greater maintenance for the database administrator. This results in an increased load on the warehouse. The following diagram shows the three major requirements that must be balanced to create an effective system. You must decide which factors are most important in your particular environment and weigh them against the other factors. However.

You can even use different schema types within the same hierarchy. page 60. The use of a resource-intensive DISTINCT query could therefore negate any performance gain achieved by reducing the number of joins between higher-level lookup tables. .3 Warehouse Structure for Your Logical Data Model Project Design Guide expensive in terms of database resources and processing time. Schema type comparisons One way to achieve a balance of the various trade-offs in your schema design is to use a variety of schema types in your physical warehouse schema. Inc. Schema Type Highly normalized schema Lookup Table Structure • Attribute ID • Attribute description column • ID column of parent • Attribute ID • Attribute description column • ID column of parent • ID column of grandparents Advantages Minimal storage space and minimal data redundancy which makes updating data less intensive than for the other schema types Greatly reduces the number of joins necessary to relate an attribute to its grandparents as compared to a highly normalized schema Disadvantages Requires numerous joins to retrieve information from higher-level lookup tables Moderately normalized schema Requires some redundant storage 60 Schema type comparisons © 2007 MicroStrategy. One hierarchy can be highly normalized while another can be highly denormalized. you may need higher level lookup tables to take advantage of aggregate tables. For more comparisons between the different schema types described in this chapter. In addition to the previous points. page 241. The table below compares the different schema types. see the following section Schema type comparisons. which are discussed in Using summary tables to store data: Aggregate tables.

As facts and attributes are the cornerstones of the reports you intend to create using MicroStrategy. it is essential to understand the structure of each of these schema objects before creating a project. you can learn about these same schema objects in terms of how they exist in the MicroStrategy environment. © 2007 MicroStrategy.Project Design Guide Warehouse Structure for Your Logical Data Model 3 Schema Type Highly denormalized schema Lookup Table Structure • Attribute ID • Attribute description column • ID column of parent • description column of parent • ID column of grandparents • description column of grandparents • Consolidates an entire hierarchy into a single lookup table Advantages Further reduces joins necessary to retrieve attribute descriptions as compared to a moderately normalized schema Disadvantages Requires the most storage space and redundant data requires a more intensive process to update Star schema • Further reduces joins necessary to retrieve attribute descriptions as compared to a moderately normalized schema • Requires less storage space and data redundancy than a highly denormalized schema and thus data is easier to update Large lookup tables can negatively affect query performance when searching tables and requiring DISTINCT operations to be performed Now that you have gained an understanding of data modeling and the roles of facts and attributes. Schema type comparisons 61 . Inc.

3 Warehouse Structure for Your Logical Data Model Project Design Guide 62 Schema type comparisons © 2007 MicroStrategy. . Inc.

you are ready to create a project in MicroStrategy.4 4. To see a sample project. For more information about the © 2007 MicroStrategy. see Chapter 1. access the MicroStrategy Tutorial provided with the MicroStrategy platform. 63 . BI Architecture and the MicroStrategy Platform. It is ready to be used and requires no additional configuration tasks. Inc. This chapter guides you through the first few major steps involved in creating a project in MicroStrategy. CREATING AND CONFIGURING A PROJECT Introduction Once you create a logical model of your business data and arrange the data within the data warehouse. For definitions and descriptions of the components within the MicroStrategy platform that allow you to create and analyze your business intelligence applications. The Tutorial is a sample data warehouse and demonstration project you can use to learn about the various features of the MicroStrategy platform.

64 Project connectivity components © 2007 MicroStrategy. It is intended to familiarize you with some of the terms discussed in this guide. and project settings are stored in the MicroStrategy metadata. Inc. . MicroStrategy metadata All schema objects. application objects. Metadata is stored in a relational database with a predefined structure. Project connectivity components This section defines some of the basic terminology used in project creation in MicroStrategy Desktop. refer to the MicroStrategy Basic Reporting Guide. see Appendix A. To view the structure of the MicroStrategy Tutorial.4 Creating and Configuring a Project Project Design Guide Tutorial. The RDBMS for the metadata and warehouse do not need to be the same. configuration objects. MicroStrategy Tutorial.

To view the readme from the Start menu select Programs. Project source The project source is a configuration object which represents a connection to a metadata repository. A connection to a metadata repository is achieved in one of two ways: • Direct or two-tier mode ( ): Connects to the metadata by specifying a DSN. and then select ReadMe. page 71. Inc. © 2007 MicroStrategy. login. then MicroStrategy. You create the metadata shell with the MicroStrategy Configuration Wizard. which creates the blank tables and populates some of the tables with basic initialization data. MicroStrategy strongly suggests you always connect to the metadata through Intelligence Server because of the security and scalability it provides. Metadata shell Before you can populate the metadata repository with data. You should not connect directly to the metadata unless you are implementing a prototype environment. Project connectivity components 65 . It is highly recommended that you never use direct mode connection in a production environment. and password to a metadata repository. In MicroStrategy Desktop.Project Design Guide Creating and Configuring a Project 4 You can find the list of supported RDBMS platforms in the readme file that is installed with MicroStrategy products. This first step in the project creation process is outlined in Creating the metadata repository. The metadata shell is the set of blank tables that are created when you initially implement a MicroStrategy business intelligence environment. the necessary tables to hold the data must be present. the project source appears in the Folder List with an icon that varies depending on the type of connection it represents.

However. 66 Project connectivity components © 2007 MicroStrategy. A four-tier connection is a Server (three-tier) connection in conjunction with MicroStrategy Web deployed on a web server. A project source connects to a single metadata repository. the same metadata repository can be accessed by multiple project sources. which in turn governs and validates the connection to the metadata. This includes application objects. Inc. and ensures metadata integrity. page 8 for definitions of these object types). A project source may contain any number of projects. This is the type of connection used to create a production-ready project in MicroStrategy. Intelligence Server is a necessary part of any production project. MicroStrategy Desktop is the second tier. The project metadata is the first tier.4 Creating and Configuring a Project Project Design Guide • Server or three-tier mode( ): Connects to the metadata by pointing to an Intelligence Server definition. Intelligence Server. Intelligence Server manages all connections to databases. enforces security. After the connection to the metadata is established. and MicroStrategy Desktop. . and Intelligence Server is the third tier. For these reasons. every object definition you create within this project source is stored in this metadata. schema objects. and configuration objects from any number of projects defined within this project source (see MicroStrategy metadata. The following diagram illustrates Server connectivity between a MicroStrategy metadata repository.

For information on database instances. see the MicroStrategy Installation and Configuration Guide. page 14. metadata repository. page 72. Connecting to a data source through a database instance is explained in detail in Connecting to a data source. you specify the data source location by creating and selecting a database instance with the appropriate connection parameters. A project also represents the intersection of a data source. see MicroStrategy project. and user community. Project connectivity components 67 . When you define a project. For more information on what a project is in MicroStrategy.Project Design Guide Creating and Configuring a Project 4 Database instance The database instance is a configuration object that represents a connection to a data source. © 2007 MicroStrategy. Inc. Project A project is where you build and store all schema objects and information you need to create application objects such as reports in the MicroStrategy environment.

These steps provide you with a high-level view of the project creation process. . you can begin to build an understanding of how these various pieces work together to provide an integrated business intelligence environment as shown in the following diagram. Bear this process in mind as you proceed through the rest of this guide. and projects. project sources. 1 Creating the metadata repository The metadata repository contains the objects and definitions associated with your project. database instances. Creating a project The following procedure describes the main steps to create a MicroStrategy project. It acts as the 68 Creating a project © 2007 MicroStrategy. Inc.4 Creating and Configuring a Project Project Design Guide Summary of project connectivity With a firm understanding of the MicroStrategy metadata.

Project Design Guide

Creating and Configuring a Project

4

intermediary between your business data and your reporting environment. Therefore, the first step in the project creation process is to create a metadata repository. For detailed instructions, see Creating the metadata repository, page 71. 2 Connecting to the metadata repository and data source Once the metadata repository is created and populated with initialization data, you must establish connections to both the metadata repository and data source. For detailed instructions, see Connecting to the metadata repository and data source, page 71. 3 Creating the project Having created a metadata repository and established the necessary connections between the different parts of your MicroStrategy environment, you are ready to create the basic definition of your project. For detailed instructions, see Creating the project, page 73. 4 Creating facts and attributes Schema objects such as facts and attributes are the basic components of the logical structure of a project. The business data your user community wants to report on is represented by schema objects in MicroStrategy. Therefore, it is necessary to setup schema objects before reports can be created. This step is covered in Creating facts and attributes, page 82 of this chapter. You can use Query Builder or Freeform SQL to create schema objects as you design reports. For more information for these features, see the MicroStrategy Advanced Reporting Guide.

© 2007 MicroStrategy, Inc.

Creating a project

69

4

Creating and Configuring a Project

Project Design Guide

5 Configuring additional schema-level settings Once you create the initial schema objects, you can configure additional schema-level settings that allow you to add complexity and depth to objects in your project and to the project as a whole. For example, you can create advanced facts and attributes to retrieve specific result sets. You can also use attributes to create time-series analysis schema objects called transformations and implement various tools to optimize and maintain your project over time. For information about: • • • Advanced fact creation, see Creating and modifying simple and advanced facts, page 91. Advanced attribute creation, see Adding and modifying attributes, page 134. Hierarchies and hierarchy creation, see Chapter 7, Creating Hierarchies to Organize and Browse Attributes. Transformations and transformation creation, see Chapter 9, Creating Transformations to Define Time-Based and Other Comparisons. Project optimization and maintenance, see Chapter 8, Optimizing and Maintaining Your Project. The steps listed above relate to the process of creating a project which connects to a database or other data source such as a text file or Excel file. MicroStrategy also supports connecting to data stored in SAP BW, Microsoft Analysis Services 2000 and 2005, and Hyperion Essbase systems. When integrated with MicroStrategy, these systems are referred to as OLAP cube sources. You can connect to any of these OLAP cube sources to report and analyze the data concurrently within a project that also connects to a database, or you can create a a standalone connection to your OLAP cube source (see Appendix B, Connecting to OLAP Cube Sources).

70 Creating a project

© 2007 MicroStrategy, Inc.

Project Design Guide

Creating and Configuring a Project

4

Creating the metadata repository
Your first step in project creation is to create a metadata repository. This repository stores all the objects necessary to support your project. You can create an empty metadata repository in the database location of your choice using the Metadata Tables option in the Configuration Wizard. Before proceeding to the next section, make sure your metadata repository exists in a non-Microsoft Access database. An Access database is unsuitable for a production project. Create a metadata repository using the guidelines outlined in the Configuring and Connecting Intelligence Server chapter of the MicroStrategy Installation and Configuration Guide. When you create the metadata repository, MicroStrategy creates a default configuration in the repository. The default configuration populates the tables with the basic data required for the metadata, such as the default project folder structure and basic connection information. These tables are populated with your project information during the project creation step in the Project Creation Assistant, outlined in Creating the project, page 73. For instructions on creating a metadata repository in a database, see the MicroStrategy Installation and Configuration Guide.

Connecting to the metadata repository and data source
Once you have created a metadata repository, your next step is to connect MicroStrategy Desktop to the metadata repository and to your data source.

© 2007 MicroStrategy, Inc.

Creating the metadata repository

71

4

Creating and Configuring a Project

Project Design Guide

Connecting to the metadata repository
You connect to the metadata repository in MicroStrategy Desktop or Web through a project source. Recall that a project source is a pointer to a metadata repository. It connects either through a DSN that points to the appropriate database location or by pointing to an instance of Intelligence Server which, in turn, points to the metadata repository location. To configure Intelligence Server and establish a server connection between the metadata, Intelligence Server, and MicroStrategy Desktop, follow the steps in the MicroStrategy Installation and Configuration Guide.

Connecting to a data source
A data source contains the business data from which you intend to gain analytical insight. Once you connect to the metadata repository through Intelligence Server, your next step is to create a connection to the data source to which your project can connect. You connect to the data source by creating a database instance in MicroStrategy Desktop. Create a database instance using the procedures outlined in the Configuring and Connecting Intelligence Server chapter of the MicroStrategy Installation and Configuration Guide. When you create a project, you must assign a database instance to that project. A project specifies only one database instance at a time, but a database instance can be assigned to multiple projects.

72 Connecting to the metadata repository and data source

© 2007 MicroStrategy, Inc.

Project Design Guide

Creating and Configuring a Project

4

MicroStrategy also allows you to connect to your SAP BW, Microsoft Analysis Services, and Hyperion Essbase data sources. For information about connecting to these OLAP cube sources, see Appendix B, Connecting to OLAP Cube Sources.

Creating the project
You can now begin building the MicroStrategy project that connects to the metadata repository and data source. Project creation involves creating a basic project definition and creating your project’s first schema objects. There are several methods for creating and editing a project, which includes: • Creating a test or prototype project using Project Builder With Project Builder, you can build project prototypes for proof-of-concept tests with your own data. Project Builder is best suited for creating a test project, and it is not intended to create production projects. • Creating a production project using Project Creation Assistant This section guides you through the creation of a production-ready MicroStrategy project. The following table compares the main features of both the Project Creation Assistant and Project Builder. Use the table to determine the project creation tool that best suits your needs.
Features Intended audience Project type Complexity Project Creation Assistant Advanced users Production-ready or other large projects Extensive features require more project design knowledge Project Builder Newer users Test or basic projects Easier to use but fewer features

© 2007 MicroStrategy, Inc.

Creating the project

73

4

Creating and Configuring a Project

Project Design Guide

Features

Project Creation Assistant Advanced; can create the following objects and more: • multiple tables, attributes, and facts at once • attributes with many-to-many and joint child relationships A variety of databases and other data sources

Project Builder Limited; cannot be used to create multiple schema objects at once, but can be used to create basic hierarchies and metrics

Functionality

Metadata repository type Metric and report creation

Microsoft Access

No, must be done after project creation Yes, basic metrics and reports only

Creating a test or prototype project using Project Builder
Project Builder is a wizard that allows you to create simple MicroStrategy projects quickly and efficiently. Project Builder was created with speed in mind; thus it provides only a subset of the features and functionality of the Project Creation Assistant. It allows you to rapidly create user hierarchies and simple metrics and reports. With Project Builder, you can build project prototypes for proof-of-concept tests with your own data and simple yet functional projects. To create a project for your production environment, it is highly recommended you follow the steps outlined in Creating a production project using Project Creation Assistant, page 75. The Project Creation Assistant can add greater functionality and capability to your project in your production environment. To learn more about Project Builder, proceed through this section. You can also refer to the Introduction to MicroStrategy: Evaluation Guide and the Project Builder online help (press F1 from within Project Builder).

Using Project Builder
By default, Project Builder uses a Microsoft Access database for the metadata repository. A Microsoft Access database is suitable for creating the metadata repository for a prototype

74 Creating the project

© 2007 MicroStrategy, Inc.

Project Design Guide

Creating and Configuring a Project

4

project, but not a production project. You should not use Microsoft Access for anything other than a proof-of-concept or demonstration type of application. You can use Project Mover to move a demonstration project into a production-ready database (see the System Administration Guide.) Project Builder contains the following options that assist you in creating a prototype project: • My Database allows you to name the project and select the database that contains the business information you want to analyze with the project you create. My Business Model allows you to identify relationships that define the business information in your database. Project Builder uses this structure to help you analyze the data. My Reports allows you to use the attributes and metrics you defined using My Business Model, to create a variety of reports. These reports are based on pre-defined templates. You can also preview and run the reports. You can learn about creating and designing reports in more detail in the MicroStrategy Basic Reporting Guide. To access Project Builder from the Start menu select Programs, then MicroStrategy, then Desktop, and then select Project Builder.

Creating a production project using Project Creation Assistant
This section describes how to create a Server-connected (three-tier) project for your production setup using MicroStrategy Desktop. It is assumed you intend to implement Intelligence Server in your business intelligence environment as the means of connecting to your project as opposed to using a two-tier setup.

© 2007 MicroStrategy, Inc.

Creating the project

75

4

Creating and Configuring a Project

Project Design Guide

Creating a project using the Project Creation Assistant in MicroStrategy Desktop provides advanced functionalities and greater complexity to your project than Project Builder. It allows you to create a new project and add the following objects to it or to an existing project: • • • Tables Facts Attributes

With the Project Creation Assistant you create and configure a project and some of the essential schema objects that reside within it. The intended audience for this tool includes experienced project creators who have planned all their facts, attributes, and data relationships. This information is covered elsewhere in this guide. For a listing of information covered in specific chapters, see Planning your project below. The main advantage of the Project Creation Assistant over Project Builder is its ability to create multiple schema objects at once. Since you can efficiently add multiple tables and develop numerous attributes and facts, it is especially useful for large projects which contain many tables and schema objects. With the Project Creation Assistant you can also create attributes with many-to-many relationships.

Planning your project
Before using the Project Creation Assistant, you should plan your project and consider the following: • The logical data model you intend to use for this project; logical data models are covered in Chapter 2, The Logical Data Model. The tables to use in the project; physical warehouse schema models are covered in Chapter 3, Warehouse Structure for Your Logical Data Model. The facts to include in the project and the data types used to identify them; facts are covered in Chapter 5, The Building Blocks of Business Data: Facts.

76 Creating the project

© 2007 MicroStrategy, Inc.

Project Design Guide

Creating and Configuring a Project

4

The attributes to create in the project and the data types used to identify them, including: The description column name for each attribute. Any other attribute forms for each attribute. The child attributes for each attribute. Attributes are covered in Chapter 6, The Context of Your Business Data: Attributes.

Creating a new project using the Project Creation Assistant
Once you have planned your project and completed the prerequisites, you can use the Project Creation Assistant to build the project and populate the metadata based on the data structures present in your data warehouse. The steps of the Project Creation Assistant are: 1 Initialize/create the project. Initializing the project means giving the project a name and selecting the metadata repository in which to create the project—that is, the project source. After you specify these settings, the shell of a project is created in the metadata. This configures the folder structure and default connectivity settings. Be aware that this process can take some time to complete. 2 Select tables from the Warehouse Catalog. In this step, you use the Warehouse Catalog to specify which data warehouse tables to include in your project. 3 Create facts. 4 Create attributes. You should complete all the steps in the Project Creation Assistant at the same time. While you can save an incomplete project definition, you cannot finish creating it later with the Project Creation Assistant. Instead, you must complete it using the
© 2007 MicroStrategy, Inc. Creating the project

77

For more details on how to setup HTML documents for a project. or Attribute Creation Assistant. To create a project source which connects to your data through Intelligence Server. 2 From the Schema menu. To create a new project using the Project Creation Assistant 1 Log in to a project source in MicroStrategy Desktop. as shown below: 3 Click Create project. see the MicroStrategy Installation and Configuration Guide. . description. The New Project page opens. and default document directory location for the project. such as the Warehouse Catalog. Inc.4 Creating and Configuring a Project Project Design Guide appropriate interface. 4 Enter the name. see the Configuring and Connecting Intelligence Server chapter of the MicroStrategy Installation and Configuration Guide. 78 Creating the project © 2007 MicroStrategy. select Create New Project. Fact Creation Assistant. The Project Creation Assistant opens. The default document directory for a project is the directory location to store all HTML documents.

the language of the local machine (the LOCAL_MACHINE registry key). The Login dialog box opens. If you are not authorized by your database or system administrator to create projects in the data source you have selected. The language check prevents these inconsistencies and ensures that the language display is consistent across the project. Creating the project 79 . Adding tables using the Warehouse Catalog The warehouse tables for a project determines the set of data available to be analyzed in the project. and relationship tables to use in your new © 2007 MicroStrategy. it can lead to inconsistencies in the language display. 8 Enter a valid login ID and password and click OK. From this list. and the Project locale property match. you cannot proceed to the next step. When these properties do not match. a language check ensures that the language settings of the user profile of the local machine (the CURRENT_USER registry key). select the project source in which you created the database instance to connect to your metadata repository.Project Design Guide Creating and Configuring a Project 4 5 To support anonymous authentication mode for guest users for this project. Inc. select Enable the guest user account for this project. 7 Click OK. The Warehouse Catalog queries the data source and lists the tables and columns that exist in it. When you create a new project. You use the Warehouse Catalog to add warehouse tables to your project. Proceed to the next section to determine the tables to be used in your project. you select the lookup. 6 From the Project Source drop-down list. fact. The Project Creation Assistant creates an empty project in the metadata repository. The Warehouse Catalog lists all the tables in the data source to which you are connected through your database instance and to which your database login has read privileges.

The database instance selected in this dialog box determines which data source is accessed. select Select tables from the Warehouse Catalog. You should also include all other tables needed to complete your project. refer to the MicroStrategy Installation and Configuration Guide. and partition mapping tables. facts. The database login you use must have read privileges so you are able to view the tables in the selected warehouse.4 Creating and Configuring a Project Project Design Guide project. they become schema objects known as logical tables in MicroStrategy. You can edit your database instance by clicking Edit. and tables are abstractions built on top of the tables and columns in the data source. MicroStrategy schema objects such as attributes. including transformation tables. 2 Select a database instance from the drop-down list and click OK. 80 Creating the project © 2007 MicroStrategy. Logical Tables. The Warehouse Catalog opens. Inc. . and are discussed in detail in Appendix C. To add and remove tables to the project using the Warehouse Catalog 1 In the Project Creation Assistant. Once tables are selected from the data source and added to your project. Database instances and database logins are MicroStrategy objects that determine the warehouse to which a project connects. Logical tables are representations of the tables that are available in the data warehouse. To learn more about these objects. The Warehouse Database Instance dialog box opens. aggregate tables.

or specify a database instance for a table.Project Design Guide Creating and Configuring a Project 4 3 The left side of the Warehouse Catalog lists all available tables and the number of rows each table contains. The list on the right shows all the tables currently being used in the project. page 221. select them from the right side and click < to remove them. 5 To remove tables from your project. select the tables you want to add to the Warehouse Catalog. see Managing warehouse and project tables. Warehouse Catalog options 6 Right-clicking any table provides you with additional Warehouse Catalog functionality. For more information on these abilities and how to use them. © 2007 MicroStrategy. For example you can view rows in a table. specify a table prefix. copy a table. Inc. Creating the project 81 . and click > to add the selected tables. Click << to remove all the tables from your project. if any: 4 From the left side. Click >> to add all the listed tables.

82 Creating facts and attributes © 2007 MicroStrategy. The next step in the Project Creation Wizard involves creating schema objects: facts and attributes. For example.4 Creating and Configuring a Project Project Design Guide 7 To set advanced options you can click Options on the Warehouse Catalog toolbar. The table definitions are written to the metadata. see Modifying data warehouse connection and operation defaults. Before you create facts and attributes. page 226. This process can take some time to complete. The Building Blocks of Business Data: Facts and Chapter 6. . Follow the instructions outlined in Creating facts and attributes. 8 In the toolbar. page 220. For more information on these abilities and how to use them. it is important to understand what facts and attributes are and the defining characteristics of each. page 82 and Configuring additional schema-level settings. and decide whether schema objects are mapped automatically or manually. After exiting the Project Creation Assistant. display extra table and row information. see Adding and removing tables for a project. you can still access the Warehouse Catalog to add additional tables. click Save and Close to save your changes to the Warehouse Catalog. you can change the database instance. This information is covered in Chapter 5. however. Creating facts and attributes This step in the project creation process involves using the Project Creation Assistant to create two kinds of schema objects: facts and attributes. The Context of Your Business Data: Attributes. Inc. page 83 to learn how to create these schema objects and configure additional schema-level settings for those objects. For steps to access the Warehouse Catalog to add tables to a project. customize how tables and columns are read from the database system catalog.

Creating Hierarchies to Organize and Browse Attributes. edit. This is covered in Chapter 7. aggregate tables. The tools used to create aggregate tables and partitions are the Warehouse Catalog. Now that you have completed most of the key steps in creating a new project. Optimizing and Maintaining Your Project. and attribute form expressions. which facilitate access to attribute and element browsing and drilling. Inc. which are schema objects used for time-series analysis. the Metadata Partition Mapping Editor. Configuring additional schema-level settings 83 . This is covered in Creating and modifying simple and advanced facts. page 91.Project Design Guide Creating and Configuring a Project 4 Configuring additional schema-level settings The final step in the project creation process involves configuring additional schema-level settings to add more analytical depth to your schema objects and optimize the project as a whole. Creating Transformations to Define Time-Based and Other Comparisons. User hierarchies: The Hierarchy Editor allows you to create user hierarchies. attribute forms. Transformations are covered in Chapter 9. and configure facts. and the Warehouse Partition Mapping Editor. and partitioning and partition mappings: The Transformation Editor allows you to create transformations. • • • © 2007 MicroStrategy. These settings include: • Fact definitions: The Fact Editor allows you to create. This is covered in Adding and modifying attributes. proceed to the chapters referenced above to complete the next steps in the project creation process. This information is covered in Chapter 8. page 134. Advanced configurations: These objects include transformations. Attribute definitions: The Attribute Editor allows you to create and edit attributes.

custom groups. are beyond the scope of this guide. To learn more about how to deploy your project using MicroStrategy Web. .4 Creating and Configuring a Project Project Design Guide Deploying your project and creating reports After you create a project. and other report objects. however. reports. • 84 Deploying your project and creating reports © 2007 MicroStrategy. You can also begin creating reports in MicroStrategy Desktop and MicroStrategy Web. the project you deploy will contain only basic facts and attributes. Keep in mind. Connecting to OLAP Cube Sources. and Hyperion Essbase data sources. For information on how to use your own customized SQL statements to create reports. For a complete discussion of metrics. Proceed to the chapters listed above to add analytical depth and more functionality to your project. and prompts. Inc. Microsoft Analysis Services. filters. see the Creating Freeform SQL reports chapter in the MicroStrategy Advanced Reporting Guide. and other report objects such as filters. you can deploy it to your user community using MicroStrategy Web. see Appendix B. For information about creating reports in MicroStrategy Desktop. that if you completed only the steps in this chapter. for creating reports in MicroStrategy Web. and metrics and attributes are essential components of reports. Facts and attributes provide the backbone of the reports and documents created by report designers. refer to the MicroStrategy Basic Reporting Guide and the MicroStrategy Advanced Reporting Guide. For information about connecting to OLAP cube sources. see the MicroStrategy Web online help. refer to the MicroStrategy Basic Reporting Guide. refer to the Deploying your Project with MicroStrategy Web chapter of the MicroStrategy Installation and Configuration Guide. Metrics. Facts are used to create metrics. Note the following: • MicroStrategy allows you to connect to your SAP BW.

Facts generally represent the answers to the business questions on which users want to report. facts are numeric data and attributes are contextual data for the facts.5 5. As the project designer. In a MicroStrategy project. For example. They relate numeric data values from the data warehouse to the MicroStrategy reporting environment. Facts and attributes are necessary to define projects. facts are schema objects created by and shared between MicroStrategy users. Inc. The facts you create in MicroStrategy allow users to access data stored in the data warehouse. which are used in the majority of analyses and reports that users can create with MicroStrategy. In the MicroStrategy environment. THE BUILDING BLOCKS OF BUSINESS DATA: FACTS Introduction Facts are one of the essential elements within the business data model. you want to analyze the amount of sales at a certain store during January. © 2007 MicroStrategy. Facts form the basis for metrics. and the store and month represent attributes. 85 . the amount of sales represents the fact. In this case.

Inc. This data is used to create a metric (such as profit) which is a business measure. When fact information is requested for a report in MicroStrategy. that column is accessed to retrieve the necessary data. Each cell in the columns represents a specific piece of information. Facts are stored in the data warehouse in fact tables. as shown below. Facts are based on physical columns within tables in the data warehouse. Users can then use these facts and attributes as building blocks for metrics and reports. . 86 © 2007 MicroStrategy. These fact tables are composed of different columns.5 The Building Blocks of Business Data: Facts Project Design Guide you must create projects that contain facts and attributes.

For example. Creating facts A fact has two common characteristics: it is numeric and it is aggregatable. as well as highlight some advanced fact design techniques and procedures. profit. facts do not describe data. facts such as Tenure and Compensation Cost could exist in a data warehouse that contains human resources data. Data warehouses contain different types of facts depending on the purpose of the data. simple facts as part of the initial project design effort or later in a project’s life cycle. Creating and modifying simple and advanced facts. Creating facts • © 2007 MicroStrategy. using different techniques and MicroStrategy interfaces: • Simultaneously creating multiple. While creating facts is a major step in the initial creation of a project. 87 . page 91 covers steps to add and modify both simple and advanced facts for an existing project. Facts are the actual data values stored at a specific fact level. A fact entry level is the lowest set of attributes at which a fact is stored. Facts also allow you to create advanced metrics containing data that is not stored in the warehouse but can be derived by extending facts. Inc. This section provides steps to create facts at different phases of the project design process. units sold. page 88 covers steps to create multiple. The later sections discuss conceptual information on facts. simple facts. facts are logical MicroStrategy objects that correspond to physical columns and tables. It is important to understand how to define facts because facts are the basis for almost all metrics. and cost.Project Design Guide The Building Blocks of Business Data: Facts 5 Like other schema objects such as attributes. The procedures to perform these tasks are discussed in the first section (Creating facts. it can often be necessary to modify and create facts throughout the life cycle of a project. Facts such as Quantity and Item Cost could exist in a warehouse containing sales and distribution data. page 87) of this chapter. Examples of facts include sales dollars. Unlike attributes.

page 91. simple facts During your initial project design effort. However. you can create multiple simple facts using the Project Creation Assistant and the Fact Creation Wizard. 88 Creating facts © 2007 MicroStrategy. . It allows you to create multiple facts in a single creation process. which is discussed in Creating and modifying simple and advanced facts. is used to add advanced features to facts that already exist or to create new simple or advanced facts as your project evolves. utilizing the following MicroStrategy tools: • The Fact Creation Wizard is a step-by-step interface that is typically used when you first create a project. Facts can be created and modified using a number of various techniques. fact creation and modification can be done throughout the entire life cycle of a project. You can also access the Fact Creation Wizard in MicroStrategy Desktop from the Schema menu. • The Fact Editor. Inc. The Project Creation Assistant utilizes the Fact Creation Wizard to help you create the facts for your initial project creation effort.5 The Building Blocks of Business Data: Facts Project Design Guide Simultaneously creating multiple.

For example. 3 The Column data type area allows you to select the column data types that are available as possible fact ID columns. Rules help automate and govern the fact creation process. If the naming conventions in your warehouse do not conform to the defaults in the Fact Creation Rules page. Inc. Creating facts . select Create facts. you can only select data types for the ID columns of your facts. only columns whose data types are numeric or character-based are displayed in the Fact Creation Wizard as possible columns to use for your facts. The Fact Creation Wizard opens. Select the check boxes for the data types to be included when the wizard searches the data warehouse for available fact columns. Therefore. if you select Character and Numeric and leave the remaining check boxes cleared. 89 © 2007 MicroStrategy. as shown below: 2 Click Define Rules to set some basic fact creation rules. Unlike most attributes which can access multiple columns of description information. you may need to change these rules. a fact does not have description information. The Fact Creation Rules page opens.Project Design Guide The Building Blocks of Business Data: Facts 5 To create facts with the Fact Creation Wizard 1 In the Project Creation Assistant.

that is. whether to replace underscores in the fact name with spaces and whether the first letter is capitalized. 10 Review the summary information in the Finish page and click Finish to create the facts. Click << to remove all the columns in your project. – The Fact Creation Wizard cannot handle columns that hold the same information but have different column names (that is. Fact column selection 6 Click Next. heterogeneous columns). The selected fact definitions are stored in the metadata. see Simultaneously creating multiple attributes. 90 Creating facts © 2007 MicroStrategy. select the fact columns to use for your facts and click > to add them to your project. 5 Click OK to accept your rule changes and return to the Fact Creation Wizard. Select the appropriate check boxes to create the desired default fact names. . select them from the Facts pane and click < to move them to the left side. page 129. For more information about mapping facts to heterogeneous columns. The Finish page opens.5 The Building Blocks of Business Data: Facts Project Design Guide 4 The Fact name area allows you to determine how to create default fact names. see Facts with different column names: Heterogeneous column names. with columns that are not currently being used in the project listed in the Available columns pane. Note the following: – You can rename any fact to make its name more user-friendly by right-clicking the fact and selecting Rename. 8 To remove fact columns from your project. page 102. 7 From the Available columns pane. To continue creating a project with the Project Creation Assistant. The Column Selection page opens. Click >> to add all the listed columns. Inc. 9 Click Next.

level extensions. map multiple or heterogeneous columns. column aliases. However. Creating facts 91 . Typically. you only use the Fact Creation Wizard as part of the initial project creation.Project Design Guide The Building Blocks of Business Data: Facts 5 Creating and modifying simple and advanced facts After you have created a project. you can use it to create one or more simple facts at the same time. for creating most of the facts for the project. Inc. it limits you to creating simple facts and does not allow you to edit existing facts. you can use either the Fact Creation Wizard or the Fact Editor to create new facts in your project: • With the Fact Creation Wizard you can: Create simple facts Create multiple facts quickly Add a large number of facts during project creation • With the Fact Editor you can: Create simple and advanced facts Edit existing facts and configure additional schema-level settings The Fact Creation Wizard can create multiple facts quickly and easily. Creating one or more simple facts with the Fact Creation Wizard Although the Fact Creation Wizard is primarily used to create most of a project’s facts during initial project creation. To create facts with the Fact Creation Wizard 1 In MicroStrategy Desktop. You can use the Fact Editor to edit existing facts and create fact expressions. © 2007 MicroStrategy. and configure other settings. log in to the project source that contains your project and expand your project.

92 Creating facts © 2007 MicroStrategy. To use the Fact Creation Wizard to add facts. You can also use the Fact Editor to add extensions to those facts and configure additional settings within them to support various analytical requirements. select the project to which to add additional facts. select the project to which to add additional facts.5 The Building Blocks of Business Data: Facts Project Design Guide You must use a login that has Architect privileges. see Permissions and Privileges of the MicroStrategy System Administration Guide. To create a simple fact with the Fact Editor 1 In MicroStrategy Desktop. Inc. For more information about privileges. You must use a login that has Architect privileges. 2 From the Folder List in MicroStrategy Desktop. log in to the project source that contains your project and expand your project. see Permissions and Privileges of the MicroStrategy System Administration Guide. The Fact Creation Wizard opens. select Fact Creation Wizard. page 89. you can create additional facts and modify existing facts with the Fact Editor. follow the procedures outlined in To create facts with the Fact Creation Wizard. 2 From the Folder List in MicroStrategy Desktop. . The following procedure describes how to use the Fact Editor to create a simple fact based on a single fact column in a table. Creating simple and advanced facts with the Fact Editor As your project evolves. 3 From the Schema menu. For more information about privileges.

select the tables for which you want your constant expression to apply. with the Create New Fact Expression dialog box displayed on top of it. Inc. • © 2007 MicroStrategy. Manual mapping means that MicroStrategy scans all of the tables in the project and locates all tables with the columns used in the fact expression. select Automatic or Manual. – If you are creating a constant expression that is not based on a physical column in a project table. select the source table for the fact. 4 From the Source table drop-down list. Using automatic mapping in the Attribute Editor helps you decide which tables to map your facts to when creating a fact. The source table is the table or logical view that contains the fact column on which you want to base a new fact. select New.Project Design Guide The Building Blocks of Business Data: Facts 5 3 From the File menu. 5 From the Available columns pane. Creating facts 93 . manually select the appropriate source tables for each fact. – These mapping methods are different from the automatic mapping methods for the Warehouse Catalog. The Fact Editor opens. page 231) determine whether attributes or facts are automatically mapped to new tables when they are added after an attribute or fact is created. You can then remove any tables mapped automatically or select other tables. – If the same column name does not contain the same data across different tables. drag and drop a fact column into the Fact expression pane. The Warehouse Catalog mapping methods (discussed in Mapping schema objects and calculating logical sizes for tables. 6 In the Mapping area. • Automatic mapping means that MicroStrategy scans all of the tables in the project and selects all tables with the columns used in the fact expression as possible source tables for the fact. You then select which of those tables are used as source tables for the fact. and then Fact.

In the Fact_Sales table. However. Inc. the Sales column contains discount data. page 105. and create extensions. 7 Click OK to close the Create New Fact Expression dialog box. although the column name is the same in both tables (i. the Sales column contains revenue data.e. • Definition: This tab allows you to define fact expressions. click Save and Close. In other words. 94 Creating facts © 2007 MicroStrategy. you must select the Manual mapping method so you can select the Fact_Discount table as a source table for the Discount fact.5 The Building Blocks of Business Data: Facts Project Design Guide For example. 8 Use the tabs of the Fact Editor to define fact expressions. which exists in both the Fact_Sales table and the Fact_Discount table. Column aliases are discussed in Fact column names and data types: Column aliases. the columns contain different fact data in each table. page 97. When creating the Revenue fact. Column Alias: This tab allows you to create a column alias for the fact. suppose you have a column named Sales. . When creating the Discount fact. Fact definitions are discussed in How facts are defined. in the Fact_Discount table. Fact extensions are discussed in Modifying the levels at which facts are reported: Level extensions. you must select the Manual mapping method so you can select the Fact_Sales table as a source table for the Revenue fact. • • 9 When your changes are complete. refer to the MicroStrategy Desktop online help. Sales). create column aliases. For detailed information about the options on each tab within the Fact Editor. page 107. If you use the Automatic mapping method in both cases. Extensions: This tab allows you to create fact level extensions. the MicroStrategy SQL Engine may use the incorrect column for the facts. as described below.

navigate to the location in which to save the fact.Project Design Guide The Building Blocks of Business Data: Facts 5 10 In the Save As dialog box. The fact is saved and the Fact Editor closes. 2 Double-click the fact to open the Fact Editor and edit the fact. You can learn how to create more advanced facts in the various sections below. Enter a name for the fact and click Save. select Update Schema to update the project schema. open the folder that contains the fact to modify. Inc. 11 From the Schema menu. Modifying simple and advanced facts To modify an existing fact 1 In MicroStrategy Desktop. © 2007 MicroStrategy. Creating facts 95 .

unless you create a new column alias. Column aliases are discussed in detail in Fact column names and data types: Column aliases. even though it is stored at that level. The column alias stores the column name MicroStrategy uses to generate SQL statements when creating temporary tables related to the fact. page 105. Inc. page 97. page 107.5 The Building Blocks of Business Data: Facts Project Design Guide The structure of facts As shown in the diagram below. facts are made up of the following components: • The fact definition is composed of one or more fact expressions. Extensions can also prevent a fact from being reported at a certain level. Level extensions are discussed in detail in Modifying the levels at which facts are reported: Level extensions. Level extensions are very effective for advanced data modeling scenarios. Every fact must have at least one expression. • • 96 The structure of facts © 2007 MicroStrategy. . Fact definitions are discussed in detail in How facts are defined. Fact level extensions allow facts stored in the data warehouse at one level to be reported at an unrelated level. Every fact must have a column alias. MicroStrategy selects a default column alias depending on the type of fact.

While the Unit Price fact only has one expression. How facts are defined A fact definition contains properties that define a fact and its components. For a discussion of the tools used to created facts and procedures on how to use them. the fact expression is simply the name of the column which holds the fact data. How facts are defined 97 . and the source tables it uses. the fact expression maps the fact to the All_Sales columns in the LU_ITEM and ORDER_DETAIL tables in the warehouse. Fact Name Unit Price Expression All_Sales Source Tables LU_ITEM ORDER_DETAIL In the example. some facts use more advanced expressions to perform calculations on multiple columns of data to return a single fact. including the fact name. and often must be calculated differently from one table to the next. see Creating facts. Level extensions are optional. © 2007 MicroStrategy. page 87. when you select the numeric column used to represent the fact. The following table provides an example of a fact definition. The fact definition is composed of at least one fact expression and basic information about the fact. The fact expression contained in the definition represents how the fact is calculated by MicroStrategy. During project creation with the Fact Creation Wizard. Facts can be found in multiple tables in a warehouse schema. both the fact definition and column alias are automatically defined. However. Inc. multiple expressions can exist within a fact definition. In this case. expression. and source tables.Project Design Guide The Building Blocks of Business Data: Facts 5 You create facts in MicroStrategy Desktop using the Fact Creation Wizard and the Fact Editor. expression. which includes the fact’s name.

5 The Building Blocks of Business Data: Facts Project Design Guide Note the following: • • Each fact expression relates to one or more related tables that contain the fact. A fact definition must have one or more fact expressions. The mathematical operators that can be used in a fact expression are: • • • • Addition (+) Subtraction (-) Multiplication (*) Division (/) 98 How facts are defined © 2007 MicroStrategy. For each of the tables. The following image illustrates a column in the fact table and the associated fact expressions: Valid fact expressions are formulas constructed from fact columns with or without numeric constants or mathematical operators. fact expressions define how the fact is calculated. Inc. Mapping physical columns to facts: Fact expressions A fact expression maps facts to physical columns in the warehouse. Regardless of how it is defined. These expressions can be as simple as a fact column name from the warehouse or as sophisticated as a formula containing multiple fact column names and numeric constants. . a fact expression represents a mapping to specific fact information in the warehouse.

An implicit fact indicates a fact table from which to retrieve data. For detailed information about metrics. A fact can also be defined using an ApplySimple function. where you can sum the column holding the constant to create a COUNT.Project Design Guide The Building Blocks of Business Data: Facts 5 Note the following: • You can use the Fact Editor to create fact expressions. These steps are covered in Creating and modifying simple and advanced facts. as explained in the following sections. creates a derived fact. Any operation on a column such as adding a constant. page 91. or setting the expression to be an absolute value. Apply functions are discussed in the Pass-Through Expressions appendix in the MicroStrategy Advanced Reporting Guide. You may also find it helpful to use implicit facts when building metrics. However. some facts do not exist at all in the warehouse and are defined in other ways. The implicit fact can have its expression defined as a constant value. For example. adding another column’s values. see the MicroStrategy Advanced Reporting Guide. For example. In other words. although nothing is saved in a table column. you can define a fact equal to the constant “1”. Inc. you are creating a fact © 2007 MicroStrategy. How facts are defined 99 . These temporary columns allow you to keep track of how many rows are returned for a certain attribute. if you want to build a metric defined as Sum(1). • Most facts represent physical columns in the data warehouse. you can use implicit fact expressions to create “temporary columns” in the database with a value of “1” for every row. Derived facts and derived fact expressions A derived fact has its value determined by an expression that contains more than just a column in a table. Implicit facts and implicit fact expressions Implicit facts are virtual or constant facts that do not physically exist in the database.

. Example: creating derived facts The Cost fact in the MicroStrategy Tutorial contains the derived fact expression Qty_Sold * Unit_Cost. This expression implies that columns containing data about the quantity of items sold and the price of those units can be multiplied to produce a useful business calculation. Rather than creating a derived fact. For more information on what metrics are and how to create them. by creating the following derived fact: Sales = Quantity_Sold * Price One advantage of creating a derived fact is that a derived fact allows one consistent fact to exist in the project in lieu of having to retrieve multiple intermediary facts from multiple tables. Inc. 100 How facts are defined © 2007 MicroStrategy. Using a single fact saves storage space and limits the number of SQL passes used in queries. the columns are used to answer the business question. see the MicroStrategy Advanced Reporting Guide. you can create such analysis in MicroStrategy with the use of metrics. “How much did it cost the company to create the items purchased by customers?” The following procedure describes how to create a derived fact that uses the derived fact expression described above. For a more generalized procedure to create derived facts. refer to the MicroStrategy Desktop online help. For example. In this case. a table in your data warehouse contains the following elements: Fact Table 1 Item Quarter Quantity_Sold Price You can create a new fact.5 The Building Blocks of Business Data: Facts Project Design Guide from information that is available in the data warehouse. Metrics allow you to perform calculations and aggregations on your fact data. Sales.

double-click the UNIT_PRICE column to add it to end of the fact expression. How facts are defined 101 . 2 Navigate to the My Personal Objects folder.Project Design Guide The Building Blocks of Business Data: Facts 5 To create a derived fact 1 In MicroStrategy Desktop. point to New. 5 From the Available columns pane. and then select Fact. Inc. select Automatic. click * (multiplication operator) to add it to the expression. double-click the QTY_SOLD column to add it to the Fact expression pane on the right. 3 From the File menu. select the ORDER_DETAIL table. 6 With the cursor in the Fact expression pane. 8 Under Mapping method. 4 From the Source table drop-down list. © 2007 MicroStrategy. with the Create New Fact Expression dialog box displayed on top of it. The Fact Editor opens. log in to the MicroStrategy Tutorial project. The expression should appear as shown below: 10 Click OK. The derived fact expression appears in the Fact expression pane in the Fact Editor. 7 From the Available columns list. and open the My Objects folder. 9 Click Validate to check whether the syntax of the expression is correct.

creating a heterogeneous fact column name for dollar sales informs the system that the Dollar_Sales and Dollar_Sls columns represent the same fact.5 The Building Blocks of Business Data: Facts Project Design Guide 11 From the File menu. Table 2 includes a fact called Dollar_Sls. When you call for the information in a report through the use of a metric. you must update the project schema. With heterogeneous column names. select Save As. you can refer the same fact to multiple columns with different column names and from different tables that identify the same quantitative value. both fact columns are used in the SQL. 12 Enter a name for the derived fact and click Save. it is not necessary to update the schema. Table 1 contains a fact called Dollar_Sales. Table 1 Year Dollar_Sales Table 2 Month Dollar_Sls MicroStrategy allows you to identify heterogeneous fact column names for each fact. In the example below. since this is only an example. at this point. 13 When you create a fact for your project. The Save menu opens. resulting in an accurate representation of the fact in the report. . two fact tables in a warehouse each contain columns for dollar sales. Inc. the same fact can access columns with different column names. Facts with different column names: Heterogeneous column names In your warehouse. 102 How facts are defined © 2007 MicroStrategy. However. In the example above. These two items represent the same information.

5 From the Available columns pane. The Fact Editor opens and the fact expression you just created appears in the Fact expression pane. you create the Units Sold fact and map its corresponding heterogeneous fact columns to it. they represent the same data and are therefore both mapped to the Unit Sold fact. © 2007 MicroStrategy. To create heterogeneous fact columns 1 In MicroStrategy Desktop. point to New. log in to the MicroStrategy Tutorial project. Qty_Sold and Tot_Unit_Sales. double-click the QTY_SOLD column to add it to the Fact expression pane on the right.Project Design Guide The Building Blocks of Business Data: Facts 5 Example: mapping heterogeneous fact columns The Units Sold fact in MicroStrategy Tutorial consists of two fact columns in the warehouse. Although these fact columns have different names and exist in different fact tables. 4 From the Source table drop-down list. 6 In the Mapping method area. In the procedure. Inc. and open the My Objects folder. select Automatic. The following procedure describes how to create the Units Sold fact that already exists in MicroStrategy Tutorial. The Fact Editor opens. This is one of the tables in which a heterogeneous fact column for the Units Sold fact exists. You must map heterogeneous fact columns to their corresponding facts to ensure that accurate and complete data is displayed on reports. select the ORDER_FACT table. refer to the MicroStrategy Desktop online help. and then select Fact. 7 Click OK. How facts are defined 103 . with the Create New Fact Expression dialog box displayed on top of it. 2 Navigate to the My Personal Objects folder. For a more generalized procedure to map heterogeneous fact columns. 3 From the File menu.

12 Click OK. Inc. it is not necessary to update the schema. The Save menu opens. 8 Click New. since this is only an example. select the CITY_CTR_SALES table. select Automatic. 11 In the Mapping method area. you must update the project schema. 14 Enter a name for the new fact and click Save. 10 From the Available columns pane. However. 9 From the Source table drop-down list. double-click the TOT_UNIT_SALES column to add it to the Fact expression pane on the right. The Fact Editor opens and the fact expression you just created appears in the Fact expression pane. The Create New Fact Expression dialog box opens. 15 When you create a fact for your project. This is the other table in which a heterogeneous fact column for the Units Sold fact exists. at this point.5 The Building Blocks of Business Data: Facts Project Design Guide Now you must add the other heterogeneous fact column as separate expression for the Units Sold fact. . 104 How facts are defined © 2007 MicroStrategy. Now the Units Sold fact you are creating maps correctly to its heterogeneous fact columns. 13 From the File menu. select Save As.

there are cases where you may need to change this.#0. By default. the data type for a fact is inherited from the data type of the column on which the fact is defined in the data warehouse. For example. The SQL you create may be different. [Start_Date_Id]. you can define a fact to be the difference between two dates to perform a calculation such as the average number of days between a start and an end date. Inc. [End_Date_Id]) The expression syntax is specific to your database type. However. #1)". This syntax is specific to Microsoft SQL Server.Project Design Guide The Building Blocks of Business Data: Facts 5 Fact column names and data types: Column aliases A column alias specifies both the name of the column to be used in temporary tables and the data type to be used for the fact. You could create this fact using the following expression: ApplySimple("DateDiff(day. © 2007 MicroStrategy. Fact column names and data types: Column aliases 105 .

• 106 Fact column names and data types: Column aliases © 2007 MicroStrategy. The Fact Editor opens.Column Selection dialog box opens.5 The Building Blocks of Business Data: Facts Project Design Guide The data type for this fact is automatically set to a Date data type because the Start_Date_ID and End_Date_ID have Date data types. Inc. 4 In the Column alias area. The Column Editor . 3 Select the Column Alias tab. The Column Editor . then the system uses a Date data type and tries to insert integer data into this column.Definition dialog box opens. 6 You can modify the following properties for the column alias: • Column name: The name for the column alias which is used in any SQL statements which include the fact column. This can cause an error for some database platforms. see Appendix D. the difference between the two dates. the result of the calculation. For a description of the different data types supported by MicroStrategy. that is. To create a column alias for a fact This procedure assumes you have already created a fact with a valid fact expression for which to create a new column alias. log in to the project source that contains the fact to create a new column alias for. 1 In MicroStrategy Desktop. You can use the Fact Editor to create column aliases. This is used when a temporary SQL table needs to be created for the calculation. If you did not change the data type of the column alias. However. Data Types. is an integer. To avoid the possibility of an error due to conflicting data types. 2 Right-click the fact and select Edit. Data type: The data type for the fact. click Modify. you should modify the column alias for the fact to change the default Date data type to an Integer data type. 5 Select New to create a new column alias. .

see the MicroStrategy Desktop online help. Modifying the levels at which facts are reported: Level extensions 107 . Modifying the levels at which facts are reported: Level extensions Facts are stored at a particular business level in the warehouse.Project Design Guide The Building Blocks of Business Data: Facts 5 • Depending on the data type selected. The level of a fact is defined by the attribute IDs present in the table. 7 Click OK to save your changes and return to the Column Editor . These attribute IDs imply that the fact is reported at the item and quarter levels by default. you can specify the byte length. the fact table shown below contains several attribute IDs. Fact Table 1 Item Quarter Quantity_Sold Price Level extensions are necessary when facts are stored in the data warehouse at one level and reported at different levels. including Item and Quarter. For example. 8 Click OK to save your changes and return to the Fact Editor. or time scale for your column alias.Column Selection dialog box. Every fact is tied to a set of attributes that may or may not © 2007 MicroStrategy. 9 Select Save and Close to save your changes. scale. bit length. precision. For a detailed description on each of these properties. Inc.

For example if you have a cost fact at the level of a date attribute in a time hierarchy. That is. For example. you have to extend the level of the Discount fact to the Call Center level. without the use of level extensions. A fact extension is needed when a fact does not relate directly or indirectly to an attribute included on a report. Inc. If the entry level of a fact is at the lowest level of a hierarchy. . page 118). To see if some call centers are selling significantly more items at a discount than other call centers. 108 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. facts require level extensions to be related to any attributes that are at a lower logical level in the same hierarchy than the entry level for a fact (see Lowering the level of fact data: Fact degradations. discounts apply to particular items on particular days. MicroStrategy can aggregate the cost fact data to the level of the year attribute because it is in the same hierarchy as the date attribute and at a higher level. you record a Discount fact at the Item/Date level. which is an attribute from a different hierarchy. You can use level extensions to change a fact level and extend a fact level to a level in a completely different hierarchy. However.5 The Building Blocks of Business Data: Facts Project Design Guide satisfy all users’ reporting requirements. all attributes at a higher logical level in the hierarchy are available for use as well.

page 114 Forcing facts to relate to attributes: Using cross product joins. © 2007 MicroStrategy. page 122 You can find complete descriptions for each of these methods in the online help for the Level Extension Wizard in the Fact Editor. lowered. and they tend to be used only in specific cases. a level extension must be defined for the fact. you are allowing facts or attributes that have been captured at one level to be extended to other levels to meet reporting requirements. You can create fact level extensions by using any of the following methods: • • • • • Defining a join on fact tables using table relations. a level extension must exist to relate the fact data to the attribute. Otherwise.Project Design Guide The Building Blocks of Business Data: Facts 5 Level extensions define how facts can be extended. or disallowed to other attributes across the schema. Before a metric containing a fact can be used with an attribute that is not in or related to the attribute’s entry level. By creating a level extension. there is no way to make a connection between the fact data and the attribute. Level extensions are not required like the fact definition and column alias. page 110 Defining a join on fact tables using fact relations. page 116 Lowering the level of fact data: Fact degradations. page 118 Disallowing the reporting of a fact at a certain level. Inc. Modifying the levels at which facts are reported: Level extensions 109 . You can use the Fact Editor to create level extensions. This is because if a fact is stored at a level unrelated to an attribute on a report.

A fact extension is required to view freight values for each item included in an order. Notice that the ORDER_FACT and ORDER_DETAIL tables include Order-level Units Sold and Item-level Units Sold columns respectively. you are creating a table relation to extend a fact. The procedure also describes general principles of creating fact extensions which you can use to create fact extensions for the facts in your project. the ORDER_DETAIL table is used to create the Freight fact extension to Item because: 1 The ORDER_FACT and ORDER_DETAIL tables both contain the Order attribute’s identity column to join the tables. For example. When you specify a table to join with a fact. Inc. This metric has a table relation fact extension to the Item attribute. The following procedure steps through how to create the fact extension that has been created for the Freight fact of the Tutorial project. the Freight fact cannot be reported at the Item level. Since the ORDER_FACT table that defines Freight does not include the identity column for the Item attribute. These two columns are used to allocate the fact expression in the procedure below. An allocation expression is required to extend Freight to the Item level. A fact extension can be used to relate a fact to an attribute using a fact table. The join is important as the table contains an attribute in the entry level and the attribute to which to extend. 2 The Freight fact cannot simply be joined with a table containing Item information to return a meaningful freight value for each item. the MicroStrategy Tutorial project includes a Freight metric.5 The Building Blocks of Business Data: Facts Project Design Guide Defining a join on fact tables using table relations A table relation defines a join on tables. In this example. and ORDER_DETAIL contains the Item attribute’s identity column to extend the fact to Item. 110 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. .

The General Information page opens. The Level Extension Wizard opens. page 118) Extend the fact entry level: define a fact extension on a table relation. this example steps through how the Freight fact extension Extension to Item was created. Then select whether you want to: • Lower the fact entry level: define a fact degradation (see Lowering the level of fact data: Fact degradations. To lower. extend. The Extended Attributes page opens. so select Extend the fact entry level. dynamic fact relation. or disallow the fact entry level 6 Enter a name and a description for your fact extension (already provided). page 122) • • For this example you are creating a fact extension on a table relation. 2 Browse to the Facts folder and double-click the Freight fact to edit it. To create a new fact extension you would click New. 5 Read the Welcome statement and click Next. However. The Fact Editor opens. © 2007 MicroStrategy. 4 Select Extension to Item and click Modify. or a cross product join Disallow partially or completely the fact entry level: define a fact extension that does not allow a fact to be reported at a certain level (see Disallowing the reporting of a fact at a certain level.Project Design Guide The Building Blocks of Business Data: Facts 5 To define a fact extension with a table relation 1 In Desktop. Modifying the levels at which facts are reported: Level extensions 111 . 3 Click the Extensions tab. log in to the MicroStrategy Tutorial project. Inc. and click Next.

To select the type of fact extension 8 Select how you want to extend the fact: • • Specify the relationship table used to extend the fact: select a relationship table and join attributes. the ORDER_DETAIL table is already selected. or manually select the attribute(s). 112 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. page 116) . Click Next. join attributes. and define the allocation expression 9 Select the table used to extend the fact to the new level. Since you know that you want to join the ORDER_FACT and ORDER_DETAIL tables using the Order attribute. This allows the MicroStrategy Engine to select the table that includes the fact and join attributes you choose to create the fact extension (see Defining a join on fact tables using fact relations. and click Next to continue defining your fact extension on a table relation. The Join Type page opens. allowing the fact to be reported at the new level. page 114). choose the lowest level attribute in that hierarchy. Click Next.5 The Building Blocks of Business Data: Facts Project Design Guide To select attributes to extend the fact to 7 Select the attributes you want to extend the fact to. The Table Selection page opens. Inc. The Extension Type page opens. Perform the extension through a cross product: select to apply a cross product join (see Forcing facts to relate to attributes: Using cross product joins. The Join Attributes Direction page opens. Select the relationship table dynamically: select a fact and join attributes. To select the table. . For this example Item is already selected. To extend the fact so that it can be reported at any level in a hierarchy. 10 Select whether to allow Intelligence Server to dynamically select what attribute(s) to perform the join. • For this example select Specify the relationship table used to extend the fact. For this example. select Order and click Next.

The Allocation page opens. The SQL for your reports may vary depending on the type of DBMS you use. or join using the attribute and its children. the extension of Freight provides an estimate of the freight for each item of an order. not an exact calculation. Day. the allocation expression is already provided. Modifying the levels at which facts are reported: Level extensions 113 . Item.[ORDER_ID] AS ORDER_ID.[ITEM_ID] The SQL statement above is for an Access database.[FREIGHT] * a12. 13 Click Finish to create the fact extension.[ORDER_DATE]) AS ORDER_DATE. [ORDER_DETAIL] a12. Employee. When the engine processes a report containing Order. max(a11. a12. Click Next. In this case Order has no children. 12 Enter an allocation expression that calculates the fact at the new level. and Freight.[QTY_SOLD])) AS WJXBFS1 from [ORDER_FACT] a11. A more detailed description of why this occurs follows this procedure. © 2007 MicroStrategy. For this example. max(a13. Promotion level.[QTY_SOLD]) / a11. [LU_ITEM] a13 where a11.Project Design Guide The Building Blocks of Business Data: Facts 5 11 You can choose to join using the attribute. sum(((a11.[ITEM_NAME]) AS ITEM_NAME. a12. ((Freight * [Item-level Units Sold]) / [Order-level Units Sold]). Inc.[ITEM_ID] AS ITEM_ID.[ORDER_ID]. Notice that the expression returns an average freight amount per item of an order. and Freight (metric mapped to the Freight fact) is: select a11.[ITEM_ID] = a13.[ITEM_ID] group by a11. it joins ORDER_FACT and ORDER_DETAIL and considers the resulting table as one logical fact table at the Item. Item. The SQL generated for the report containing Order. Therefore.[ORDER_ID] = a12. so you do not have to click the Join against arrow to change the default. Take a moment to review the allocation expression.[ORDER_ID] and a12. Order.

If you want to provide exact values of data at a certain level. you most likely need to capture such data and store it in your data source. Defining a join on fact tables using fact relations Fact extensions can be defined by a fact relation instead of a table relation. This allows more flexibility in defining the relations. review the values of the first order with an extra metric that calculates the number of each item type in an order shown below. since the MicroStrategy Engine is responsible for choosing the appropriate table to join. the table join is possible on any table that contains the fact. Inc. Notice that the Freight metric averages the amount of freight per item in an order. 114 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. . This illustrates how fact extensions often provide an estimation of values at a different level rather than an exact calculation. rather than you having to select tables manually. With a fact relation.5 The Building Blocks of Business Data: Facts Project Design Guide To view how the fact extension is an estimation of freight values for each item of an order. The larger freight values occur because more than one of the item type was included in the order.

Open the Order Unit Sales fact and extend it to either Distribution Center and Order or just Distribution Center. The MicroStrategy Engine tries to join a table containing Freight to a table containing Order Unit Sales. You can define the fact relation in the Level Extension Wizard which you can access from the Fact Editor. © 2007 MicroStrategy. Inc. Next.Project Design Guide The Building Blocks of Business Data: Facts 5 The following diagram shows the schema from the example in Defining a join on fact tables using table relations. The engine can make the following joins. you can create a fact relation using the Order Unit Sales fact. and Order Table 1 and Table 4 on Distribution Center Table 2 and Table 3 on Distribution Center Table 3 and Table 4 on Distribution Center The joins described above demonstrate how the join attributes can be either Distribution Center and Order or just Distribution Center. Modifying the levels at which facts are reported: Level extensions 115 . To extend the entry level of the Freight fact to Customer. select the Select the relationship table dynamically option and specify the tables to use for the extension. This option is set in the step immediately after To select the type of fact extension. page 110 after two summary tables are added to it. depending on the join attributes specified: • • • • Table 1 and Table 2 on Distribution Center.

116 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. sum(a1. Customer. When you specify a cross product join to relate a fact to an attribute.DIST_CENTER group by a1. The tables and attributes you specify in the wizard determine the different types of joins that are created.CUSTOMER The SQL statement above is for an Access database. as explained above. In a best fit join. .5 The Building Blocks of Business Data: Facts Project Design Guide page 112 in the procedure above. TABLE4 a2 where a1. MicroStrategy does not recommend using the cross product join.DIST_CENTER. Since this method can be inefficient. The SQL generated for a report containing Distribution Center. The cross product join is an extension that allows a single fact value to relate to all elements of an unrelated attribute. you are creating a Cartesian product of the lookup attribute.Freight) from TABLE3 a1. Forcing facts to relate to attributes: Using cross product joins You can use a cross product join when a join does not exist and you need to force a fact to relate to an attribute by extending the fact. a2. As with table relations. select a1. if the only join attribute is Distribution Center. Cross products should only be used when no other way to extend the fact exists. you can specify the best fit as the join strategy so that the engine calculates the joins. a2. and Freight is shown below.DIST_CENTER. This method can produce incorrect data because data can be repeated and counted twice in some cases.DIST_CENTER = a2. the set of join attributes must contain the entire key of the left-hand-side fact table (Table 3 in the example SQL above). The SQL for your reports may vary depending on the type of DBMS you use.CUSTOMER. Inc.

TABLE2 a2 group by a1. The SQL generated for a report containing Customer. Open the Dollar Sales fact and extend it to the Distribution Center attribute.DOLLAR_SALES) from TABLE1 a1. Distribution Center.DIST_CENTER. you do not need to specify an allocation expression. Next.CUSTOMER. This option is set in the step immediately after To select the type of fact extension.DIST_CENTER The SQL statement above is for an Access database.Project Design Guide The Building Blocks of Business Data: Facts 5 For example. select the Perform the extension through a cross product option. Inc. in the following schema. sum(a2. © 2007 MicroStrategy. a cross product join must be used. You can define this cross product join in the Level Extension Wizard in the Fact Editor. Distribution Center does not relate to Dollar Sales: Table 1 Table 2 Order Customer Dollar Sales Distribution Center To report Dollar Sales by Distribution Center. Notice that no join attributes are specified. The MicroStrategy Engine always cross-joins the lookup tables of the attributes in the extension. and Dollar Sales is: select a1. The SQL for your reports may vary depending on the type of DBMS you use. Modifying the levels at which facts are reported: Level extensions 117 . a2. For this example. page 112 of the procedure above.

which lowers a fact level. facts. Inc. now that Planned Compensation is available at the Employee level. is the logical opposite of aggregation. you must degrade the fact to a lower level. However.5 The Building Blocks of Business Data: Facts Project Design Guide Lowering the level of fact data: Fact degradations Degradation. the Human Resources Analysis Module of the MicroStrategy BIDK includes a Planned Compensation fact that is stored at the Department level. To view fact data at a lower logical level than the fact is stored at. you must support those users who wish to view and analyze the same fact data at a lower logical level. as shown below: The analytical value of this fact degradation is not immediately recognizable. This scenario may occur because you stored a fact at a level that is used most commonly in reports. This causes every employee to be listed with the same planned compensation value as the employee’s department. . you can create more meaningful analysis with other fact data that is 118 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. For example. and has a fact degradation to the Employee level (the attributes. The fact extension does not use an allocation expression to degrade Planned Compensation to the Employee level. and metrics used in this example can all be found in this Analytics Module). However.

You can now view what percentage of your planned compensation per department has been spent per employee. log in to the Human Resources Analysis Module. To define a fact degradation 1 In Desktop. Modifying the levels at which facts are reported: Level extensions 119 . the Compensation Cost fact is stored at the Employee level. The procedure also describes general principles of creating fact degradations which you can use to create fact degradations for the facts in your project. The metric Actual as % Planned Compensation has been created to calculate the actual compensation of an employee as a percentage of the planned compensation for the entire department of the employee.Project Design Guide The Building Blocks of Business Data: Facts 5 stored at the Employee level. 2 Browse to the Facts / Compensation / Planning folder and double-click the Planned Compensation fact to edit it. Inc. The Fact Editor opens. The metric definition is ([Compensation Cost]/[Planned Compensation]). © 2007 MicroStrategy. as shown below: Without using a degradation of Planned Compensation to Employee. The following procedure steps through how to create the fact degradation that has been created for the Planned Compensation fact of the Human Resources Analysis Module. respectively. For example. you could not include Department and Employee on a report with these metrics and return accurate values. which performs a division of metrics defined from the Compensation Cost and Planned Compensation facts.

the Department attribute is already selected. . 4 Select Degradation to Employee and click Modify. For this example. 8 Select what attribute(s) to perform the join. choose the lowest level attribute in that hierarchy. Click Next. The Join Type page opens. 6 Enter a name and a description for your fact extension (already provided). 7 Select the attributes you want to degrade the fact to. dynamic fact relation. 120 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. The Extended Attributes page opens. this example steps through how the Planned Compensation fact degradation Degradation to Employee was created. To extend the fact so that it can be reported at any level in a hierarchy. allowing the fact to be reported at the new level. Inc.5 The Building Blocks of Business Data: Facts Project Design Guide 3 Click the Extensions tab. and click Next. The General Information page opens. To create a new fact degradation you would click New. Then select whether you want to: • • Lower the fact entry level: define a fact degradation Extend the fact entry level: define a fact extension on a table relation. page 122) • For this example you are creating a fact degradation so select Lower the fact entry level. page 110 and Defining a join on fact tables using fact relations. However. The Level Extension Wizard opens. page 114) Disallow partially or completely the fact entry level: define a fact extension that does not allow a fact to be reported at a certain level (see Disallowing the reporting of a fact at a certain level. Click Next. 5 Read the Welcome statement and click Next. or a cross product join (see Defining a join on fact tables using table relations. The Join Attributes Direction page opens. For this example Employee is already selected.

11 Click Finish to create the fact degradation. While it is possible that the fact data would be the same for every month of the year. the join is performed on the Department attribute and its children. this is often an unlikely scenario. By creating allocation expressions. You select Month to be the attribute to which to degrade. which allows the distribution of values according to a calculation you specify. 10 Enter an allocation expression that calculates the fact at the new level. Fact degradations with allocation expressions Not all fact degradations can simply be lowered to a new level. page 121 for an example of using an allocation expression for a fact degradation. The Allocation page opens. to change the definition of the fact in a level extension. Using such an allocation expression would spread a year’s fact data evenly over the 12 months of that year. Avg. For this example. For this example.Project Design Guide The Building Blocks of Business Data: Facts 5 9 You can choose to join using the attribute. you do not need to include an allocation expression. Modifying the levels at which facts are reported: Level extensions . and so on) when aggregating data to higher levels. you must add an allocation expression. Ordinarily. you can create a degradation on the fact to relate it to the monthly level. or join using the attribute and its children. you define how higher-level facts are degraded to lower-level attributes. You then specify that the allocation expression is fact/12. Inc. This is similar in concept to choosing an aggregation function (Sum. See Fact degradations with allocation expressions. Such fact degradations should be used 121 © 2007 MicroStrategy. For example. Fact degradations often produce data estimates rather than exact values for the fact data at lower logical levels. Click Next. For example. Allocation expressions are defined by operations you set on attributes and facts in the Level Extension Wizard in the Fact Editor. if your fact is stored at the yearly level and you want to report the data at the monthly level. consider the allocation expression fact/12 for a degradation from Year to Month.

the Analytical Engine does a dynamic cross-join and evaluates the report. Consider a schema containing three dimensions: Geography. if you create a report and attempt to include the fact at the Minute or Second level. The setting prevents unnecessary joins to lookup tables. the report fails because the disallow setting now prevents the cross-joins between the lookup tables and fact tables.5 The Building Blocks of Business Data: Facts Project Design Guide only when fact data is not stored at a lower logical level and there is no way to directly relate the fact data to the lower logical level. 122 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. When you create a report containing the Month attribute and the Sales metric. if you have three years’ worth of data. querying at the Minute or Second level consumes too many resources and returns extensive data. Inc. or disallow the fact entry level. does not affect normal joins. If a fact is stored at a level that is counterproductive to a query. an error is returned. such as data that is stored at the Minute or Second level. This option is set in the step immediately after To lower. Disallowing the reporting of a fact at a certain level The Disallow partially or completely the fact entry level setting within the Fact Editor is like a lock which prevents a fact from being reported at a specific level. and Product. With a disallow in place. This setting. Suppose you create a fact called Sales at the Item level in the Product dimension and a metric called Sales as the sum of the Sales fact. indicating that the report cannot be run at that level. Disallowing a fact to be extended to a level lower than the fact’s entry level due to unnecessary complexity and the cost of analyzing fact data at such a level is a common use for this feature. The following examples describe instances in which disallowing a fact entry level can prove useful. you can disallow the lower levels. After updating the schema and re-executing the report. page 111 of the procedure to create a fact extension above. For example. however. . extend. you would use the Disallow partially or completely the fact entry level setting and select the lowest attribute in the Time dimension such as Day. Time. To explicitly disallow an extension of the Sales fact to the Time dimension.

This implies that the fact extension has not been disallowed. You now disallow an extension on the Revenue fact for the Item attribute and update the schema. This is not an expected design condition. disallowing the Revenue fact at the level it is stored at in the data warehouse does not make logical sense. In this case. for the Sales fact. The Disallow the fact entry level setting applies only to attributes that can be considered as extended attributes. Modifying the levels at which facts are reported: Level extensions 123 . assume you specify an extension to the Month attribute and also disallow extension to Year which is a parent of the extended attribute. Inc. the engine sorts the extension conditions specified in some order and calculates the report based on the sorted order of extensions. you can still see Revenue by Item. It is advisable to avoid fact definitions that contain contradictory extension definitions. you create a report that contains the attributes Subcategory and Item and the Revenue metric. This is because Revenue exists at the same level as Item in the MicroStrategy Tutorial project. For example. In this case. Month. There must be a valid reason to disallow reporting a fact at a certain level. So you encounter only normal joins and no extensions.Project Design Guide The Building Blocks of Business Data: Facts 5 In the previous example. the report runs successfully. © 2007 MicroStrategy. If you re-execute the report. which is defined as sum of the Revenue fact. If you execute the report containing the Year attribute and Sales metric. although the engine returns a valid SQL.

5 The Building Blocks of Business Data: Facts Project Design Guide 124 Modifying the levels at which facts are reported: Level extensions © 2007 MicroStrategy. Inc. .

as well as a Revenue metric based on the Revenue fact. Because of the attributes on the report. Inc. you have a report with the Month. the report displays your company’s revenue at the region. you can only find out how much revenue the company generated in total. knowing where and when the sales took place provides the kind of analytical depth users require on a daily basis. and year levels. and Region attributes on the template. 125 . Year. which take the form of attributes in MicroStrategy. While knowing your company’s total sales is useful. including which regions produced the least revenue and which years saw the highest growth in revenue. a substantial amount of information is available. If you remove the attributes from the report. For example. Attributes provide the business model with a context in which to report on and analyze facts. THE CONTEXT OF YOUR BUSINESS DATA: ATTRIBUTES Introduction Business data represented by facts can offer little insight without the presence of business concepts and context. When executed.6 6. © 2007 MicroStrategy. month.

instructs the engine how to build the SQL for that report. The expressions of attributes and facts in the report define the SELECT clause of the SQL command. Date. attributes are identified by the column headers of the reports. In MicroStrategy reports. For example. New user and application requirements make attribute creation and modification an important part of the entire project life cycle. Date 126 © 2007 MicroStrategy. consider the following: Select Store_ID.6 The Context of Your Business Data: Attributes Project Design Guide Creating attributes is an important step in the initial project design effort. using this report definition. A report designer creates a report in part by determining these report column headers. Inc. In the data warehouse. attributes are normally identified by a unique ID column in a lookup table. sum(Sales) From Store_Fact Group By Store_ID. . Intelligence Server. which comes after creating facts when using the Project Creation Assistant.

and Customer Last Name are examples of attribute forms. is the lowest level of detail reported. Customer First Name. report analyzers do not have to know SQL to extract information from a data warehouse. page 159. 127 . See Column data descriptions and identifiers: Attribute forms. • • © 2007 MicroStrategy. page 147. it is just not aggregated. Attributes can have multiple attribute forms. It is important to understand the data is still the same. Attribute expression: maps a MicroStrategy attribute form to one or more columns in the warehouse. such as a report at the Year level. page 143. See Attribute form expressions. for the Customer attribute. and reports is beyond the scope of this guide and is covered in the MicroStrategy Advanced Reporting Guide. A discussion about metrics.Project Design Guide The Context of Your Business Data: Attributes 6 In the SQL above. See Attribute relationships. such as Day. filters. Attribute relationship: allows interaction of data at different conceptual levels and shows how data is related within a project. Because of this process. For example. Attributes are defined by these properties: • Attribute form: contains an identifier or descriptor of an attribute. A high-level report. Customer Email. includes the Year attribute but lacks the detail of a similar report which includes the lower level attributes Month and Week. Inc. The lowest level attribute you include in a report. sales information will be retrieved by store and date. The attributes and metrics in the report tell Intelligence Server where to look in the data warehouse for the information and how to create the SQL that will retrieve it.

Inc. it is often necessary to modify and create attributes throughout the life cycle of a project. as well as highlight some advanced attribute design techniques and procedures.6 The Context of Your Business Data: Attributes Project Design Guide The following diagram illustrates how the attribute properties listed above are related: While creating attributes is a major step in the initial creation of a project. The later sections discuss conceptual information on attributes. The procedures to perform these tasks are discussed in the first section (Creating attributes. . page 129) of this chapter. 128 © 2007 MicroStrategy.

you can create multiple attributes using the Attribute Creation Wizard. Creating attributes 129 .Project Design Guide The Context of Your Business Data: Attributes 6 Creating attributes An attribute is primarily used to group and aggregate fact data to add business context to the fact data. This section provides steps to create attributes at different phases of the project design process. Inc. which launches the Attribute Creation Wizard to complete the attribute creation tasks. • Simultaneously creating multiple attributes During your initial project design effort. therefore. This includes adding advanced features such as attribute forms to attributes that already exist or adding new attributes as your project evolves. For steps to access the Project Creation Wizard. see To create a new project using the Project Creation Assistant. creating attributes is a major step in any project design effort. The ability to report on and analyze data requires data to have a business context. using different techniques and MicroStrategy interfaces: • Simultaneously creating multiple attributes. To create attributes using the Attribute Creation Wizard This procedure is part of an initial project creation effort using the Project Creation Assistant. page 129—steps to create multiple attributes as part of the initial project design effort or later in a project’s life cycle. page 134—steps to add and modify attributes for an existing project. Adding and modifying attributes. © 2007 MicroStrategy.

The Attribute Creation Wizard opens. . Change these rules if the naming or data type conventions in your warehouse do not conform to these defaults. 1 In the Project Creation Assistant. 3 Click Define Rules to set some basic attribute creation rules.6 The Context of Your Business Data: Attributes Project Design Guide page 78. especially if you use consistent naming conventions and data types in your data warehouse. 2 Review the introduction page that is displayed. as shown below. 4 The Column data type area allows you to select the column data types to be available as possible attribute ID columns. The Attribute Creation Wizard uses these rules below to help automate the attribute creation process. The Attribute Creation Rules page opens. 130 Creating attributes © 2007 MicroStrategy. Inc. click Create attributes. Select the check boxes for the data types that should be included when the wizard searches the data warehouse for available attribute ID columns. Define attribute creation rules These rules can make the process of choosing attribute columns and naming your attributes considerably easier. You can also access the Attribute Creation Wizard at any time in the development of a project from the Schema menu in MicroStrategy Desktop.

DESC for description columns. Creating attributes 131 .Project Design Guide The Context of Your Business Data: Attributes 6 5 The Attribute name area allows you to determine how to create default attribute names. The ID Column Selection page opens. and LOOKUP for lookup tables. You should never use a column that has NULL or repeated values as the ID column for an attribute. Doing so results in unexpected behavior and errors. © 2007 MicroStrategy. 8 Click Next. When choosing the ID column for an attribute. The columns that match the identifier naming convention that you set in the warehouse search rule above are automatically highlighted. make sure that all values in the column are unique and that it does not contain NULL values. 7 Click OK to accept your rule changes and return to the Attribute Creation Wizard. ID column selection An ID column is a column or group of columns that uniquely identifies each element of an attribute. Only those columns with data types that match those chosen in the rules you defined above appear on the ID Selection page. The defaults are ID for identifier columns. Inc. You can select the appropriate check boxes to set the following default behaviors for creating attribute names: • • • Replace underscores in the attribute name with spaces Remove the word “ID” from the name Capitalize the first letter 6 The Warehouse search area determines naming conventions to help locate your warehouse objects.

Create compound attributes A compound attribute is defined as an attribute with more than one column specified as the ID column. complete the following steps: • • • Click Compound Attributes and then click Add. see Joining dissimilar column names: Heterogeneous mappings. – To remove attribute ID columns from your project. heterogeneous columns). Select the columns that are required to uniquely identify the compound attribute and click OK. 10 To create a compound attribute. select the attribute IDs in the Attributes pane and click < to move them to the Available columns pane. page 183). – The Attribute Creation Wizard cannot handle columns that hold the same information but have different column names (that is. Inc. Click >> to add all the listed columns. Note the following: – You can rename any attribute name to make it more user-friendly by right-clicking the attribute and selecting Rename. For more information about mapping attributes to heterogeneous columns. Description column selection Description columns provide the data which gives context and meaning to your attributes.6 The Context of Your Business Data: Attributes Project Design Guide 9 From the Available columns pane. 132 Creating attributes © 2007 MicroStrategy. This implies that more than one ID column is needed to uniquely identify the elements of that attribute (see Attributes with more than one ID column: Compound attributes. select the columns to use for your attribute IDs and click > to add them to your project. You are returned to the Attribute Creation Wizard. page 153. Type a name for the attribute. . The New Compound Attribute dialog box opens.

• © 2007 MicroStrategy. they provide the information for an attribute through data stored in their ID and description columns. it may make sense to use the ID column as the description column. 14 Select the lookup table for each attribute. Lookup table selection Lookup tables are the physical representation of attributes. the Relationship Definition page opens. however. – Other attribute forms need to be created through the Attribute Editor after you complete steps in the Project Creation Assistant. In some cases. In general. 13 Click Next when you are finished selecting description columns for attributes. Specify the lookup table and description column for the compound attributes and click Next. 15 Click Next: • If you have created compound attributes. such as Year. you should choose the default lookup table for each attribute. for more information about attribute forms. the Compound Attribute Definition page opens. The Lookup Table Selection page opens.Project Design Guide The Context of Your Business Data: Attributes 6 11 After adding all your attribute ID columns. page 136. you should use the default description column for each attribute. Creating attributes 133 . If you have not created a compound attribute. Refer to Adding attributes with the Attribute Editor. Inc. The Description Column Selection page opens. click Next. The column that meets the description naming convention that you set in the warehouse search rule is automatically selected. 12 Select whether to use the ID or a different column for the description of the attribute. The Relationship Definition page opens. The table that follows the lookup naming convention that you set in the warehouse search rule is automatically selected. Note the following: – In general.

the relationships between attributes should become apparent. In a logical data model. Adding and modifying attributes Just as you can add more facts to your project once you have created it. You are returned to the Attribute Creation Wizard. This completes the initial creation of a project with the Project Creation Assistant. The Select Children Attributes dialog box opens. select an attribute and click Add. The Logical Data Model). The Finish page opens. or many-to-many.6 The Context of Your Business Data: Attributes Project Design Guide Relationship definition For each attribute. When you design a logical data model for your project (see Chapter 2. 16 For each attribute. Related attributes such as City. one-to-many. . After you have completed the steps of the Attribute Creation Wizard. you can also create and add attributes as they become necessary. like Location. when attributes are in the same hierarchy they must be related to each other. so does its 134 Creating attributes © 2007 MicroStrategy. click Next. • 17 When you have defined children for all the attributes that need them. For more information on the different attribute relationship types. see Attribute relationships. As a company evolves. define child attributes: • • In the Attributes pane. Inc. or Region are often grouped in a common hierarchy. select the relationship type for the attribute to its child attribute. Select the child attributes from the list of available child attributes and click OK. the attributes are created. In the Children of: attribute name pane. whereas attributes in different hierarchies cannot be related. State. page 159. you specify the children and the type of relationship: one-to-one. 18 Review the summary information in the Finish page and click Finish to create the attributes.

or the Attribute Editor. You can use the Attribute Editor to edit existing attributes and create additional attribute forms. define advanced expressions. Creating attributes 135 . You can create attributes with either the Attribute Creation Wizard. and create the appropriate attributes so report users can analyze business data for their appropriate country. for creating most of the attributes for the project. It must then add these tables to its MicroStrategy project. map heterogeneous column names. In general. with offices only in the United States. decides to extend its operations into Europe and Asia. which allows you to define attributes. attribute forms. Inc. when the company opens its offices in Europe and Asia. Before the shift overseas. the company does not include lookup tables with information about different countries in its data warehouse. but you cannot use it to modify existing attributes or to define more advanced attributes. configure additional settings.Project Design Guide The Context of Your Business Data: Attributes 6 reporting requirements. • The Attribute Creation Wizard allows you to: Create simple attributes Create multiple attributes quickly Add a large number of attributes during project creation • The Attribute Editor allows you to: Create simple and advanced attributes Edit existing attributes and configure additional schema-level settings The Attribute Creation Wizard works well for building a large number of attributes initially. For example. However. these requirements can lead to changes to the data warehouse as well as to the schema within its MicroStrategy projects. and attribute form expressions. © 2007 MicroStrategy. it must add lookup tables that contain data about its new offices to its warehouse. a health care company. which you use to create the first attributes for your project. and so on. you only use the Attribute Creation Wizard as part of the initial project creation.

To create simple attributes in bulk using the Attribute Creation Wizard 1 In MicroStrategy Desktop. page 129. . Follow the steps below to use the Attribute Creation Wizard to create simple attributes in bulk. follow the steps outlined in Simultaneously creating multiple attributes. 4 To create attributes with the Attribute Creation Wizard. Inc. You can also use it to add new attributes to your project. You must use a login that has Architect privileges. See the Permissions and Privileges appendix of the MicroStrategy System Administration Guide for more information.6 The Context of Your Business Data: Attributes Project Design Guide Adding attributes with the Attribute Creation Wizard Although the Attribute Creation Wizard is primarily used to create most of a project’s attributes during initial project creation. 2 From the Folder List. 136 Creating attributes © 2007 MicroStrategy. select the project to which to add new attributes. The Attribute Creation Wizard opens. 3 From the Schema menu. Adding attributes with the Attribute Editor The Attribute Editor is used to add advanced features such as attribute forms to attributes that already exist. choose Attribute Creation Wizard. you may still find it useful if you need to create multiple attributes from remaining lookup columns in your warehouse. log in to the project source that contains your project and expand your project.

5 Click Validate to make sure your expression is valid. You can then clear any tables mapped automatically. © 2007 MicroStrategy. The Attribute Editor opens. use a combination of any of the following techniques: • • • Enter constants in double quotes. select a table which contains the columns of data for the attribute. Inc. To create a more advanced attribute form expression. or select other tables. 6 Under Mapping Method. When you create an expression for an attribute form. You do not have to include any operators. Click f(x) in the Form expression toolbar to create a function using the Insert Function Wizard. 3 From the Source table drop-down list. functions. Creating attributes 137 . Its columns are listed in the Available Columns pane. select New. 2 From the File menu. Click any operator in the Form expression toolbar to insert it into the expression. or parentheses.Project Design Guide The Context of Your Business Data: Attributes 6 To create an attribute using the Attribute Editor 1 In MicroStrategy Desktop. with the Create New Form Expression dialog box displayed on top of it. and then Attribute. select Automatic or Manual: • Automatic mapping means that MicroStrategy scans all of the tables in the project and selects all tables with the columns used in the attribute form expression as possible source tables for the attribute form. log in to the project source that contains your project and expand your project. page 147). you are only required to select an available column and move it to the Form expression pane. 4 To create a simple attribute form expression (Attribute form expressions. drag a column name from the Available columns pane to the Form expression pane.

You then select which of those tables are used as source tables for the attribute form. Note the following: – The mapping method defaults to Automatic for the first attribute or attribute form expression you create. page 143). Using automatic mapping in the Attribute Editor helps you decide which tables to map your attribute to when creating an attribute. page 231) determine whether attributes or facts are automatically mapped to new tables when they are added after an attribute or fact is created. Inc. The Warehouse Catalog mapping methods (discussed in Mapping schema objects and calculating logical sizes for tables. from which you can create attribute forms for the attribute (Column data descriptions and identifiers: Attribute forms. the default is Manual. .6 The Context of Your Business Data: Attributes Project Design Guide • Manual mapping means that MicroStrategy scans all of the tables in the project and locates all tables with the columns used in the attribute form expression. 7 Click OK. If you chose manual mapping. 8 From the Source tables pane. 138 Creating attributes © 2007 MicroStrategy. A lookup table holds the information for an attribute. select a table and click Set as Lookup to set the lookup table for the attribute. The Create New Attribute Form dialog box opens. – These mapping methods are NOT the same as the automatic mapping methods for the Warehouse Catalog. – A constant expression cannot use the automatic mapping method. For subsequent attributes. type a name and description in the associated fields for the attribute form. 9 In the Form general information area. The system maps the expression to each of the source tables. select the check boxes of the tables to map to the attribute form.

Therefore. 13 From the File menu. select a display type and a default sorting option from the associated drop-down lists. This ensures that your project is updated to recognize the new attribute definition. if you select a column with a non-numeric data type and set it as an ID column. Using a column with a non-numeric data type as an ID column of an attribute can result in SQL generation issues. For a description of form categories. Custom groups are sorted by the Default sort of the form that appears first in the Report display forms. 15 From the Schema menu. select Save As. Inc. a warning message appears by default when you click OK in the Create New Attribute Form dialog box. The Attribute Editor opens. 14 Navigate to the folder in which to save the attribute. For more information on custom groups. 12 Click OK. you can modify the attribute at any time using the Attribute Editor. Click Save. You cannot use the Attribute Creation Wizard to modify attributes. select Update Schema to update the project schema. refer to the MicroStrategy Advanced Reporting Guide. do one of the following: • Select a form category from the drop-down list. Enter a name for the derived fact. Click Modify to create a new form category. 11 In the Form format area. page 146. The Save dialog box opens. Creating attributes 139 .Project Design Guide The Context of Your Business Data: Attributes 6 10 In the Category used drop-down list. © 2007 MicroStrategy. • Modifying attributes After creating an attribute. see Attribute form properties.

You can learn how to create more advanced attributes in the various sections below. The Attribute Editor opens. which is described in the previous procedure To create an attribute using the Attribute Editor.6 The Context of Your Business Data: Attributes Project Design Guide To modify an existing attribute 1 In MicroStrategy Desktop. Baltimore BA. Unique sets of attribute information: Attribute elements Attribute elements are the unique sets of information or values of an attribute. open the folder that contains the attribute to modify. and Boston BN are elements of the attribute City: 140 Unique sets of attribute information: Attribute elements © 2007 MicroStrategy. Inc. You can then modify all the options available when creating and attribute in the Attribute Editor. For example. Customer is the attribute and New York NY. . in the following diagram. 2 Double-click the attribute to edit. page 137.

and so on which are defined by the attribute forms (see Column data descriptions and identifiers: Attribute forms. an attribute element is a unique set of information defined by the attribute forms of an attribute. Each attribute element is a row in an attribute lookup table in your data warehouse. each attribute element is an individual customer. Each customer (attribute element) has its own set of information such as last name. the First Name and Last Name forms are used to identify the 141 © 2007 MicroStrategy. which should be forms that provide a general description of the attribute element. email address. in the image above. For example. page 143).Project Design Guide The Context of Your Business Data: Attributes 6 The following example displays the physical warehouse table that stores elements and data for the Customer attribute. Unique sets of attribute information: Attribute elements . as shown below: The Customer attribute is a good example to understand the components of an attribute and the concept of an attribute element. first name. Inc. Attribute elements are identified by their browse forms. As shown above. With the Customer attribute.

Shoes. page 189. the attribute Division has multiple attribute elements. see Using attributes to browse and report on data. Just as you would not refer to a customer by his or her street address.6 The Context of Your Business Data: Attributes Project Design Guide attribute elements. Attribute elements can be identified in logical data models. you would not want to use the Address form to identify the Customer attribute elements. . For example. attribute elements are displayed depending on the location of the attribute they are associated with. As shown below. For more information on selecting the attribute forms used to identify attribute elements. Inc. the report below (created from the Sales 142 Unique sets of attribute information: Attribute elements © 2007 MicroStrategy. and Sporting Goods: In MicroStrategy reports. such as Men’s Clothing.

The report above uses the common practice of putting the metrics (Sales Orders Quantity (Base Units) and Cost Sales Orders) on the columns of the report. Sales Organization is on the rows of the report along with its attribute elements such as USA Central. Inc. Column data descriptions and identifiers: Attribute forms 143 . and most have at least two: © 2007 MicroStrategy. Column data descriptions and identifiers: Attribute forms Attribute forms are identifiers or descriptors of an attribute. as explained in Logical data modeling conventions. Sales Organization and Year. page 33. The display of attributes and their attribute elements is also affected by the location of the metrics on the report.Project Design Guide The Context of Your Business Data: Attributes 6 and Distribute Analysis Module of the MicroStrategy BIDK) has two attributes. Year is on the columns of the report along with its attribute elements such as 2005. Every attribute must have at least one form.

Some attributes can have additional descriptive forms that do not serve as the primary description form. . ID forms serve to uniquely identify each attribute element from other elements for the same attribute. including the Customer Name and the Address forms. The Customer attribute in the MicroStrategy Tutorial has various forms. For example. These types of forms give context and information about the Customer attribute. Attributes also have description forms. each customer must have a different value for their identity column. In this case John Smith can have a value of 1 in the Customer_ID column and Fred Black can have a value of 2 in the Customer_ID column. To differentiate between two customers such as John Smith and Fred Black.6 The Context of Your Business Data: Attributes Project Design Guide • • The ID form (required) A description form Every attribute must have an ID form (identity form). which is a column of unique numeric values to identify each customer. as shown in the following diagram: 144 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. the Customer attribute’s ID form is Customer_ID. Email is included as an additional descriptive form. For the Customer attribute. Inc.

Name. page 153. two tables exist. the LU_CUSTOMER table records all of the attribute form data for the Customer attribute. SSN. Attributes must contain at least one ID form. two columns with different names can represent the same information about an attribute.Project Design Guide The Context of Your Business Data: Attributes 6 In the data warehouse. Each table must have an ID form. you must map the appropriate columns to the same attribute to retrieve accurate and complete results when using an attribute on a report. which uniquely identifies the attribute. Name. The second lookup table contains Customer _ID and Email. The forms you create must have a reference to a lookup table and can include multiple expressions. one with the forms Customer_ID. Heterogeneous column names are discussed in Joining dissimilar column names: Heterogeneous mappings. the ID forms are used to join tables. Column data descriptions and identifiers: Attribute forms 145 . you can choose a lookup table in the Attribute Editor from a list of tables existing in the project. The attribute will have the Customer_ID. and SSN. described below: • • • Customer_ID: a unique. identifying number for each customer (ID form) Customer_Full_Name: the full name of each customer (Description form) EMAIL: the email address for the specific customer (Additional description form) In this example. © 2007 MicroStrategy. In the warehouse. When creating an attribute form. In such cases. For example. a lookup table with three columns holds the following separate forms. and Email forms and the tables will join together through the ID columns because that is the column they have in common. Inc.

Inc. For information on how attribute forms are sorted when multiple attribute forms of a single attribute define a default sort order. Each attribute can have only one Desc form. you can define the default sort order for each attribute form. Default sort governs how the form is sorted by default when included in a report. see Default sorting of multiple attribute forms. the first attribute form with a default sort order is 146 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. mapping the most commonly used or most important description form can be helpful for project designers to quickly distinguish this attribute form from the other secondary forms. below. • Format types control how the form is displayed and how filters are built. These properties affect the display of the forms and include the following: • Categories help group the types of forms.6 The Context of Your Business Data: Attributes Project Design Guide Attribute form properties You must select properties for each form when you create forms in the Attribute Editor in MicroStrategy Desktop. You can choose from Ascending. Big Decimal is discussed in detail in Appendix D. There is no way to distinguish a Desc attribute form from a None attribute form on a MicroStrategy report. . specifying a format type of Big Decimal allows users to preserve precision when qualifying on a form with more than 15 digits. and None. While there is no difference in how a Desc attribute form and None attribute form are used in MicroStrategy. Descending. it is a good practice to map the most commonly used or most important description form to the Desc form of the attribute. You can create new form categories in the Attribute Editor. Desc. the other description forms must be mapped to None forms. • Default sorting of multiple attribute forms When creating attribute forms. If you define multiple attribute forms of an attribute with ascending or descending sort orders. For example. or None. Data Types. When you have attributes that require multiple description forms. The standard category options are ID.

customers are sorted by their Last Name in ascending order. then the second attribute form with a default sort order is used for sorting. Sorting defined for a report takes precedence over default sorting defined for attribute forms. For example. Modify the Address form so that it has a descending default sort order. For example. If the first attribute form with a default sort order is not included on a report. For more information on advanced sorting. refer to the MicroStrategy Advanced Reporting Guide. Inc. If you include Customer on a report with both Last Name and Address. If you remove the Last Name form from the report. customers are sorted by their address in descending order. metrics. Each attribute form must have at least one expression.Project Design Guide The Context of Your Business Data: Attributes 6 used to sort the attribute on the report. These information units are called attribute forms. Column data descriptions and identifiers: Attribute forms . It is important to note that you can change how attribute forms are sorted from within a report. the Customer attribute in the MicroStrategy Tutorial project has the five attribute forms shown below: Of these five attribute forms. 147 © 2007 MicroStrategy. only Last Name has a default sort order set. the Customer attribute holds information about the customer such as Name and Address. An attribute form expression defines what columns in the warehouse are used to represent the attribute form in SQL. Attribute form expressions Attributes act like holders of information and provide context for fact data. and other report objects are sorted. This is the default functionality for how attributes are sorted by their attribute forms on reports. In a report you can use advanced sorting to define how attribute forms. and so on. This is because Last Name was created first and therefore is considered for sorting before the Address form.

Only implicit attributes do not include a column in the expression. These form expressions create virtual data by combining or using columns to generate the data. page 153: Heterogeneous mappings allow you to use columns with different names in the data warehouse as the same attribute form. Inc. The types of attribute form expressions are: • • Simple expressions. The definition of the simple expression includes the tables in which the column is found. Implicit expressions. Derived expressions. +. the form expression for the Customer First Name attribute form is CUST_FIRST_NAME. and/or mathematical operators. constants. the CUST_FIRST_NAME and CUST_LAST_NAME columns in the warehouse provide information about first and last names respectively.6 The Context of Your Business Data: Attributes Project Design Guide For example. page 155: Implicit form expressions do not relate directly to data stored in the data warehouse. You can create expressions using attribute columns. /. Although you can have multiple expressions in different tables. page 148: Simple form expressions access data through columns in the data warehouse. page 150: Derived form expressions perform some type of mathematical calculation on columns in the data warehouse to create an attribute form. Joining dissimilar column names: Heterogeneous mappings. You can also create a form expression using Apply functions. • • Simple expressions A simple expression is based on a single warehouse column. *. a form cannot have two different expressions in the same source table. -. since they only use the constants you declare. In this instance. 148 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. These functions are discussed in the Pass-through Expressions appendix in the MicroStrategy Advanced Reporting Guide. . The form expression for the Customer Last Name attribute form is CUST_LAST_NAME. for example.

ID and Description. including their dates of birth. To create an attribute form with a simple expression 1 In MicroStrategy Desktop. The retailer intends to analyze the data gathered from the surveys to better market their products in the future. open the Attributes folder. Once gathered. the project designer must add the column containing the customer dates of birth as an additional attribute form of the Customer attribute. Follow the procedure below to create Customer Birth Date as an attribute form in the Customer attribute. The retailer’s customers provide a variety of information on the surveys. At this point. Inc. 2 Navigate to the Schema Objects folder. The Attribute Editor opens. It has two forms. 3 Double-click the Customer attribute. © 2007 MicroStrategy. the date of birth data eventually becomes part of the retailer’s data warehouse and the appropriate lookup table is added to the retailer’s project in MicroStrategy. This will enable report designers to display each customer’s date of birth alongside each customer’s name on reports. and then the Customers folder. Both of these columns reside in the table LU_CATEGORY. both of which are defined by simple expressions. Category is an attribute in the MicroStrategy Tutorial. Example: creating an attribute form with a simple expression A retailer begins a promotion that offers customers 25% off of their purchases if they fill out a feedback survey on the company website. log in to the project source that contains the MicroStrategy Tutorial project and then log in to MicroStrategy Tutorial. Column data descriptions and identifiers: Attribute forms 149 . The expression for the ID form is the CATEGORY_ID column and the expression for the description form is the CATEGORY_DESC column.Project Design Guide The Context of Your Business Data: Attributes 6 For example.

. 6 Double-click the CUST_BIRTHDATE column to add it to the Form expression pane on the right. select DATE since Customer Birth Date is neither the ID form of Customer nor the primary description form.6 The Context of Your Business Data: Attributes Project Design Guide 4 Click New. or setting the expression to be an absolute value) creates a derived expression. type Customer Birth Date. close the Attribute Editor without saving your changes. in the Name field. and constants. you can create an attribute to hold the age of a customer or an employee that has been derived from the two columns. The new Customer Birth Date attribute form is added to the Attribute form pane in the Attribute Editor. 11 Because this is only an example. While simple expressions have their value determined by just one column in a warehouse table. functions. 7 Click OK. Inc. The Create New Attribute Form dialog box opens. By calculating the difference between the columns Date of Birth and Current Date. derived expressions are defined using one or more columns as well as other operators and values. The mapping method is selected as Automatic by default. 9 From the Category used drop-down list. Derived expressions Derived expressions are created using a combination of warehouse columns. mathematical operators. This is the table that contains customers’ dates of birth. The Create New Attribute Form dialog box opens. Any operation on a column (such as adding a constant. 10 Click OK. the attribute’s value 150 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. select the LU_CUSTOMER table. you can create a derived attribute to calculate age or anniversaries. adding another column. For example. 5 From the Source table drop-down list. By creating an attribute to calculate age in this manner. 8 In the Form general information area.

If you use syntax that is not supported by your database or other data source. To create an attribute form with a derived expression 1 In MicroStrategy Desktop. and then the Customers folder. the attribute would need to be updated every time a customer or an employee has a birthday. but you must make sure you use expressions that meet the requirements of your database-specific SQL syntax. You can achieve this using a derived form expression Name. the information is displayed as Jones. Mary under the Name column.Project Design Guide The Context of Your Business Data: Attributes 6 is automatically updated as the age changes. Column data descriptions and identifiers: Attribute forms 151 . Calculations and functions used in a derived expression can assist in deriving data from the database. you want reports to display a customer’s first name and last name together as a single entry on a report. Inc. the SQL query and resulting report can fail. If you created an attribute for age in which you included a constant number. CUST_FIRST_NAME and CUST_LAST_NAME. Example: creating an attribute form with a derived expression In your database. Using the Customer attribute. which consists of the two strings. this information is displayed as Mary Jones under the Name column. 2 Navigate to the Schema Objects folder. As another example. you could create a derived expression for Name in the format of Last Name. First Name using the following syntax: CUST_LAST_NAME + “. log in to the project source that contains the MicroStrategy Tutorial project and then log in to MicroStrategy Tutorial. “ + CUST_FIRST_NAME Using this expression. you store Customer names in two different columns. open the Attributes folder. the syntax of the derived expression for Name reads: CUST_FIRST_NAME + “ “ + CUST_LAST_NAME On a report. © 2007 MicroStrategy. However.

10 Click OK. 12 From the Category used drop-down list. 14 Because this is only an example. First Name. in the Name field. “ +. type Last Name. select None since Last Name. 4 Click New. 9 Select Automatic as the mapping method. . Your expression should be defined as shown below. First Name is neither the ID form of Customer nor the primary description form. 6 Double-click the CUST_LAST_NAME column to add it to the Form expression pane on the right. 8 Double-click the CUST_FIRST_NAME column to add it to the Form expression pane on the right. close the Attribute Editor without saving your changes. 11 In the Form general information area. place the cursor to the right of [CUST_LAST_NAME] and type + “. The new attribute form is added to the Attribute form pane in the Attribute Editor. The Create New Attribute Form dialog box opens. The Attribute Editor opens. Inc.6 The Context of Your Business Data: Attributes Project Design Guide 3 Double-click the Customer attribute. 5 From the Source table drop-down list. 7 In the Form expression pane. 152 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. The Create New Attribute Form dialog box opens. select the LU_CUSTOMER table. 13 Click OK. This is the table that contains customers’ first and last names.

depending on your database platform. Column data descriptions and identifiers: Attribute forms 153 . For example. You can map Order_Date and Day_Date to the Day attribute—this ensures that both columns are used when information about the Day attribute is displayed on a report. you can use heterogeneous mapping to map the Day attribute to all of the columns in the data warehouse that represent the same concept of Day. the ID form of the attribute Day contains two expressions. Inc. most databases cannot join a data type of Text to a data type of Number. heterogeneous mapping automatically occurs when tables and column names require it. © 2007 MicroStrategy. Of all the tables in which the columns exist. your company may have multiple columns in different tables that all represent the same business concept. The data types of columns used in a heterogeneous mapping for a given attribute must be identical or similar enough for your particular RDBMS to join them properly. in the MicroStrategy Tutorial.Project Design Guide The Context of Your Business Data: Attributes 6 Joining dissimilar column names: Heterogeneous mappings Heterogeneous mapping allows Intelligence Server to perform joins on dissimilar column names. The Day_Date column occurs in the LU_DATE table and the Order_Date column occurs in the ORDER_DETAIL and ORDER_FACT tables. If you define more than one expression for a given form. you can view the chosen tables in the source Tables area to the right of the Form Expressions area. you might be able to join columns with data types of Number and Integer. For example. In the above example. you can select as many or as few as you want to be used as part of the attribute’s definition. Because different source systems may store information in various contexts. Each expression is linked to a set of source tables that contain the columns used in the expression. However. In the Attribute Editor.

select the LU_DAY table. 11 Click OK. 9 From the Source table drop-down list. 7 Click OK. 2 Navigate to the Schema Objects folder. You could continue this process to add as many heterogeneous columns as part of one attribute form as necessary. 154 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy.6 The Context of Your Business Data: Attributes Project Design Guide To create an attribute form with a heterogeneous column mapping 1 In MicroStrategy Desktop. select the ORDER_DETAIL table. The Create New Form Expression dialog box opens. open the Attributes folder. 8 Click New. and then the Time folder. 3 Double-click the Day attribute. Notice that there are now two expressions for the attribute form definition. The Attribute Editor opens. log in to the project source that contains the MicroStrategy Tutorial project and then log in to MicroStrategy Tutorial. The mapping method is selected as Automatic by default. The Create New Attribute Form dialog box opens. 4 Click New. The Create New Attribute Form dialog box opens. 6 Double-click the DAY_DATE column to add it to the Form expression pane on the right. 10 Double-click the ORDER_DATE column to add it to the Form expression pane on the right. Inc. The Create New Form Expression dialog box opens. . both of which use different tables as the source of their information. The mapping method is selected as Automatic by default. 5 From the Source table drop-down list.

Implicit attributes are not commonly used. which stands for “Yes. for example. Implicit expressions While most attributes map directly to one or more physical columns in the warehouse. which is a constant value. although nothing is saved in an actual column. Some attribute definitions can be implied by the existence of a row in a certain table. Suppose you want a report to display which orders are rush orders so you can better keep track of your shipments. An implicit attribute such as Rush Order is useful for this purpose. they are defined by constants you specify. 14 Click OK. © 2007 MicroStrategy. Implicit attributes are useful in analyzing and retrieving relevant information. The new Date Example attribute form is added to the Attribute form pane in the Attribute Editor. the Rush Order attribute in MicroStrategy Tutorial is an example of an implicit attribute. The Rush Order attribute is defined by two expressions: the Rush_Order column in the Order_Fact table and the implicit expression “Y”.” This implicit expression is used to keep track of which orders are rush orders. Inc. 15 Because this is only an example. type Date Example. Such an attribute has an implicit expression. a “Y” is displayed in the Rush Order column. 13 From the Category used drop-down list. Any constant is acceptable. Implicit expressions are not defined by column names. in the Name field. but are useful in special cases such as the scenario described above. for each order that is a rush order. RushOrder=‘Yes’.Project Design Guide The Context of Your Business Data: Attributes 6 12 In the Form general information area. close the Attribute Editor without saving your changes. select None since this is simply an example scenario. Column data descriptions and identifiers: Attribute forms 155 . rather than being defined in terms of columns. For example. an implicit attribute is a virtual or constant attribute that does not physically exist in the warehouse. On a report with the Order and Rush Order attributes on the template.

drilling. you may need to use a different syntax. SQL Server has a Year function that extracts just the year from a date. Data Types for more information on how MicroStrategy selects a matching data type). Many database platforms have functions that can extract parts of a date from a Date data type. By default. Inc.[Date_Id]) The ApplySimple expression above is syntactically correct for SQL Server. . 0). The following are some examples of such cases. 156 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. Big Decimal. In your data warehouse you have a lookup table for an Accounts attribute where the ID is Account Number and the ID is stored in the database as DECIMAL(18. you must modify the column alias for the attribute form and map it to a special data type. but you would like to create a Year attribute. a column alias performs the same function as it does for facts. Column aliases allow you to specify a more appropriate data type that can help avoid errors in your SQL. This inheritance is governed by MicroStrategy. there are cases where you may need to change the data type. the precision can be preserved when performing filtering. In such a case. the data type for an attribute form is inherited from the data type of the column on which the form is defined. However. For attributes. They can also help you take more advantage of the data in your data warehouse. which attempts to use a data type as similar as possible to the data type in your database or other data source (see Appendix D. Because this column stores high-precision values. Another example could be a case in which your warehouse does not have a lookup table for year information. However. By doing so.6 The Context of Your Business Data: Attributes Project Design Guide Modifying attribute data types: Column aliases A column alias is a new data type that you can specify in place of the default data type for a given attribute form. For example. depending on your database or data source type. or page-by on the Account attribute. you can create a Year attribute using the following form expression: ApplySimple("Year(#0)".

To avoid the possibility of an error due to conflicting data types. You can use the Attribute Editor to create column aliases. log in to the project source that contains the attribute to create a new column alias for. some databases will return an error.Date_Id) CustCol_1. In addition to specifying the data type to be used for an attribute form. if you do not change the data type of the column alias. and it is an integer. sum(a11. This is because Date_ID is a Date data type. The above example is a simple one. and so on). © 2007 MicroStrategy.Project Design Guide The Context of Your Business Data: Attributes 6 The data type for this attribute is automatically set to a Date data type. you can change the column alias name to be more meaningful. the result of the calculation is a year. the column alias also lets you specify the column alias name to be used in the SQL generated by MicroStrategy. such as 2002.Date_Id) While the column alias name does not affect the actual results or your report. The following piece of SQL shows. However.Tot_Dollar_Sales) WJXBFS1 FROM YR_CATEGORY_SLS a11 cross join TRANS_DATE_LW_LY a12 GROUP BY Year(a12. When you create a form expression using a custom expression or multiple columns (as discussed in Attribute form expressions. When a temporary SQL table is created. the system uses a Date data type and tries to insert integer data into this column. the column alias for the attribute form defaults to CustCol (or CustCol_1. modify the column alias for the attribute form and change the default Date data type to an Integer data type. where the column alias name is used: SELECT Year(a12. CustCol_2. Column data descriptions and identifiers: Attribute forms 157 . page 147). 1 In MicroStrategy Desktop. While this does not create a problem in all database platforms. Inc. in bold. but this can be useful for troubleshooting the SQL for a particularly complex report. To create a column alias for an attribute This procedure assumes you have already created an attribute with a valid attribute expression for which to create a new column alias.

Depending on the data type selected. The Column Editor . bit length.Column Selection dialog box. Data Types. Inc. 9 Click OK to save your changes and return to the Attribute Editor. The Column Editor . 7 You can modify the following properties for the column alias: • Column name: The name for the column alias which is used in any SQL statements which include the fact column.6 The Context of Your Business Data: Attributes Project Design Guide 2 Right-click the attribute and select Edit. 3 Select an attribute form and click Modify. The Attribute Editor opens. Data type: The data type for the fact.Column Selection dialog box opens. see Appendix D. For a detailed description on each of these properties. or time scale for your column alias. precision. you can specify the byte length. For a description of the different data types supported by MicroStrategy. . see the MicroStrategy Desktop online help. The Modify Attribute Form dialog box opens. click Modify. • • 8 Click OK to save your changes and return to the Column Editor . Attribute forms versus separate attributes Attribute forms can be considered as additional descriptions for an attribute. 4 Select the Column Alias tab. 10 Select Save and Close to save your changes.Definition dialog box opens. 6 Select New to create a new column alias. whereas attributes themselves can be considered as report elements or group-by elements that have a one-to-many or a many-to-many relationship with 158 Column data descriptions and identifiers: Attribute forms © 2007 MicroStrategy. 5 In the Column alias area. scale.

which is generally undesirable. You do not group by the data. © 2007 MicroStrategy. Attribute elements. A Cartesian join. A report with two unrelated attributes. Inc. or else a Cartesian join occurs. The decision to model data as an attribute form for a given attribute or as a separate attribute is usually determined during the logical data modeling phase of project design. You can run a report with two attributes that are related—Country and City. In other words. dictate the relationships that you define between attributes. or the actual data values for an attribute. The data that you map to attributes can be represented as separate attributes or as an attribute form of an attribute. is very database intensive as every row in one table is joined to every row in the other table. for example—without any problems. how tables and columns are joined and used. or cross join. must include a metric based on a fact that is on or below the level of the two attributes. In general. Attribute relationships You link directly related attributes to each other by defining parent-child relationships. page 36. The implications of whether attributes are related become clear when you begin building reports. however. see Attribute forms. The parent-child relationships you create determine the system hierarchy within the project. these relationships define how the engine generates SQL. For more information on whether to model data as an attribute form or as a separate attribute. you should map data to an attribute form rather than a separate attribute if: • • There is a one-to-one relationship between an attribute and the data. and which tables are related to other tables. as explained in Attribute relationships.Project Design Guide The Context of Your Business Data: Attributes 6 other attributes. page 24. Attribute relationships 159 .

such as in the case of a joint checking account. One-to-many: Each element in the parent attribute corresponds to one or more elements in the child attribute. as part of the initial project design effort and in Viewing and editing the parents and children of attributes. These are the most common types of attribute relationships. Inc. and these relationships are defined by the attribute elements that exist in the related attributes. Three types of direct relationships can exist between related attributes. One year has many quarters. Q1 2007. . Year has a one-to-many relationship to quarter. One customer may have many accounts. and so on. One-to-one: Each element in the parent attribute has one and only one corresponding element in the child attribute. and each account may be associated with many customers. but a specific quarter can be in one year only. For example. The relationship is defined through the attribute’s lookup table or a relationship table. A common example of a one-to-one relationship is citizen and Taxpayer ID. after a project has already been created. you can define relationships for the attributes in your project. Attributes of this type are often in the same hierarchy. A citizen can have only one Taxpayer ID and a Taxpayer ID can be assigned to only one citizen. page 129. In banking. Many-to-many: Each element in the parent attribute can have multiple children and each child element in the child attribute can have multiple parents. customers and accounts are an example of a many-to-many relationship. This step is covered in Simultaneously creating multiple attributes. Attributes can be either related or unrelated to one another: • Related: A parent-child relationship is defined between two or more attributes.6 The Context of Your Business Data: Attributes Project Design Guide In MicroStrategy Desktop. consider the Geography hierarchy of the Customer Analysis Analytics 160 Attribute relationships © 2007 MicroStrategy. page 161. This assumes that quarters are defined with an accompanying year such as Q4 2006. Attributes can also be related to other attributes through a chain of attribute relationships.

Inc. these attributes are relatively straightforward to deal with from a project design perspective. however. © 2007 MicroStrategy. in turn. This SQL. spent $2. A particular customer and a particular day only make sense together if a fact is associated with that combination. a certain customer.Project Design Guide The Context of Your Business Data: Attributes 6 Module of the MicroStrategy BIDK. determines the output of a report.500 on January 5. For example. In this case. How attributes relate to one another and the types of relationships they share define the system hierarchy which is used to generate SQL. Don Addison. Attribute relationships 161 . Unrelated attributes can exist together in fact tables. This allows you to include Customer Region and Customer City on a report and view the different customer cities for each customer region. In general. Customer State. which contains the attributes Customer Region. No relationship is present in the lookup tables or relationship tables for these attributes. 2003 on behalf of the health care company in which he works. • Unrelated: No parent-child relationship has been defined and the attributes are not related through a chain of attribute relationships. these two attributes are related through Customer State. care must be taken when using unrelated attributes on a single report. Viewing and editing the parents and children of attributes The relationships that exist between attributes rely on the parent-child specifications that you assign to attributes. For example. Customer Region and Customer State are directly related to each other and Customer State and Customer City also have a direct relationship. giving context to the fact. and Customer City: In this scenario. the Customer and Day attributes have no relationship to one another. While Customer City is not directly related to Customer Region.

viewing and changing parent-child relationships may be a necessary troubleshooting method. The Attribute Editor opens. you can continue to make changes to the relationships between attributes even after creating your project. 4 Click the Children tab. The Call Center attribute is listed. However. 162 Attribute relationships © 2007 MicroStrategy. page 193. the Distribution Center attribute is the parent of the Call Center attribute. and the relationship table in which the relationship exists. and then the Geography folder. A one-to-one relationship exists between Distribution Center and Call Center.6 The Context of Your Business Data: Attributes Project Design Guide Parent-child relationships were designated when attributes were selected for the new project. . when a report generates inaccurate SQL and results. Inc. open the Attributes folder. log in to the project source that contains the MicroStrategy Tutorial project and then log in to MicroStrategy Tutorial. Assigning parent-child relationships to attributes allows you to connect attributes to one another in user hierarchies. as discussed in Creating Hierarchies to Organize and Browse Attributes. For a general procedure to view and edit the parents and children of an attribute. 2 Navigate to the Schema Objects folder. So these two attributes have a one-to-many relationship. Follow the procedure below to view and edit the parents and children of the Distribution Center attribute. Also. To view and edit the parents and children of an attribute 1 In MicroStrategy Desktop. is the parent of Distribution Center and multiple distribution centers exist in each country. in turn. along with the relationship type it shares with Distribution Center. For example. refer to the MicroStrategy Desktop online help. This means that only one call center exists in each distribution center. Country. 3 Double-click the Distribution Center attribute.

many-to-many relationships and joint child relationships. close the Distribution Center attribute without saving your changes. select One to Many from the Relationship type drop-down list. Supporting many-to-many and joint child relationships Two forms of attribute relationships. To change the relationship table. can introduce additional complexity to the schema and warehouse design process. 5 To change the relationship type. in this case. Logical data models and physical warehouse schemas are discussed in Chapter 2. 6 You also want the relationship between the two attributes to be defined in the LU_Employee table instead of the LU_Call_Ctr table in which it is defined now. you must change the relationship type between Call Center and Distribution Center. The Logical Data Model and Chapter 3.Project Design Guide The Context of Your Business Data: Attributes 6 Consider a scenario in which multiple call centers now exist in the same distribution center so they no longer have a one-to-one relationship. While the topics are largely related to logical model design. Attribute relationships 163 . These chapters discuss how to plan and create a conceptual framework for your business intelligence data. Inc. and how to read and interpret them. 7 Because this is only an example. Warehouse Structure for Your Logical Data Model respectively. select the LU_Employee table from the Relationship table drop-down list. a working knowledge of physical schemas is helpful when dealing with the challenges involved with these topics. © 2007 MicroStrategy. The following sections discuss the considerations you must make to ensure an effective warehouse design in light of the unique nature of these relationships. you should know what logical data models and physical warehouse schemas are. Before reading this section.

many models of cars are produced. green hats—and one color can be associated with many items—red dress. each calling center has many salespeople. both of which can be avoided by correctly modeling the relationship: • • Loss of analytical capability Multiple counting Loss of analytical capability With the color/item many-to-many relationship. . Inc. With the presence of many-to-many relationships. you must make additional considerations to effectively plan your design. In a car manufacturing plant. • The following sections use the example of items and colors to demonstrate a many-to-many relationship and the options you have for dealing with them. red shoes. Likewise. blue hats. One item can come in many colors—red hats. and many types of cars can be associated with the same color. there are many colors for a single type of car.6 The Context of Your Business Data: Attributes Project Design Guide Many-to-many relationships The presence of many-to-many relationships introduces complexity during the warehouse design process. each salesperson can work in more than one calling center. Below are some real-life examples of many-to-many relationships which must be carefully handled in the data model and schema: • In a certain organization. That is. and each comes in several colors. Potential problems with many-to-many relationships usually come in the following forms. there are usually two business questions for which users want answers: 1 In what colors are certain items available? 2 How much of a particular item/color combination was sold? 164 Attribute relationships © 2007 MicroStrategy. red socks. red hat.

© 2007 MicroStrategy. Attribute relationships 165 . Recall that one-to-many relationships are usually in the child’s lookup table. and date. a distinct relationship table needs to be present in your warehouse.Project Design Guide The Context of Your Business Data: Attributes 6 Answering the first question requires a table that contains a list of all possible item/color combinations. The following diagram shows the lookup and relationship tables for item and color: The Rel_Color_Item table provides a row for every possible item/color combination. Inc. The following diagram shows the same scenario as before. Answering the second question requires a fact table that has sales information as well as color and item information. color. In many-to-many relationships this is not feasible. Rather. but in addition it shows a simple fact table containing sales data keyed by item.

In summary.6 The Context of Your Business Data: Attributes Project Design Guide The fact table in the above diagram alone is not sufficient to answer the first question. Multiple counting When dealing with many-to-many relationships. Multiple counting occurs when all of the following takes place: • You attempt to aggregate data to the level of one of the attributes in the many-to-many relationship. the following requirements must be met: • • A distinct relationship table to identify all the possible combinations of attribute elements between attributes Both the attribute ID columns in the fact table You can implement the above points in several different ways. Inc. Another equally significant issue is multiple counting. If you have item/color combinations that are available but that have never been sold. Only item/color combinations that were actually sold—and therefore have sales recorded—can be retrieved from this table. loss of analytical capability is only one challenge. . to prevent any loss of analytical flexibility when dealing with a many-to-many attribute relationship. page 168. or a higher level than one of the attributes in the many-to-many relationship. this fact table cannot provide a complete list of item/color combinations to answer question one. The relationship exists in a distinct relationship table. All of the attributes in the many-to-many relationship are not in the fact table. which are discussed in Working with many-to-many relationships. • • 166 Attribute relationships © 2007 MicroStrategy.

This query would require both the fact table—which has the sales information by item—and the relationship table—since color is not recorded in the fact table. and socks—and that they come in three colors—red. The following diagram shows this data in the lookup tables as well as some simple sales data: The risk of multiple counting occurs when you run a query requesting the sales by color.Project Design Guide The Context of Your Business Data: Attributes 6 Recall the example from above. Assume that there are three items—hats. but make the following change: remove color from the fact table. and green—with the exception of socks. dresses. Attribute relationships 167 . © 2007 MicroStrategy. effectively aggregating to the item attribute level in the many-to-many relationship. Inc. which come in only green and blue. blue.

• What are the total sales for red items? You cannot determine an accurate answer. Inc. The following section describes several ways to prevent multiple counting when dealing with many-to-many relationships. The three techniques all have differing levels of 168 Attribute relationships © 2007 MicroStrategy. which can be calculated directly from the fact table. the correct answer is $0. the following questions cannot all be answered accurately: • What are the total sales for hats? The answer is $35. instead of calculating the sales of red items. however. For example. The answer you get is $85. using the given data. There is no way to directly relate the sales of an item in the fact table to the color of that particular item. but the answer you will get based on the data in the fact table is $50. This obviously leads to numbers that are higher than the true sales for red items. The sum includes all hats and all dresses. It is entirely possible that all the dresses sold are green. For example.6 The Context of Your Business Data: Attributes Project Design Guide The difficulty lies in the fact that color is not in the fact table. If all the dresses sold are indeed green. including blue ones and green ones. • What are the total sales for red dresses? Again. since socks do not come in red. Working with many-to-many relationships As you can see. which is the total for all hats and dresses. the query aggregates sales for all items that come in red according to the relationship table. seemingly simple questions can require you to take a number of steps to answer them when many-to-many relationships are involved. you cannot confirm this since color is not recorded in the fact table. You can use one of three techniques to provide physical support to answer the types of questions that cannot be answered accurately when using many-to-many relationships. . you cannot determine an accurate answer.

the two fundamental components remain in place in one form or another: • • A relationship table to define the attribute relationship Both the attribute’s ID columns in the fact table MicroStrategy builds the rules that MicroStrategy SQL Engine uses to generate SQL when a report request is made. Attribute relationships 169 . and flexibility is always a trade-off with complexity. Inc. If you make both of the above physical implementations.Project Design Guide The Context of Your Business Data: Attributes 6 flexibility. the SQL Engine uses the related table when no metric is included on the report. you cannot fully resolve the many-to-many relationship to calculate the amount of sales for items of a certain color. Method 1 This method is the most straightforward way to effectively manage many-to-many relationships. In all cases. © 2007 MicroStrategy. the fact table is used to answer the query. If this additional data was never captured in the source system. All of the following methods require additional data in the fact table. For example. you need to have data in the source system as to what the color is of each item sold. Method 1 requires you to create a separate relationship table (in this case. Rel_Color_Item) and add both attribute IDs to the fact table as shown in the following diagram. When a metric is included. This means that you must capture the additional data in the source system.

. or vice versa. While this method eliminates the need for a separate relationship table. Inc. to the fact table as shown in the following diagram. lower in level than either Color or Item. This attribute is essentially a concatenation of Color and Item. Here the many-to-many relationship is converted into a compound attribute relationship. Also. you lose the ability to view items independent of color. in this case Item_ID and Color_ID. Method 3 Method 3 is the most versatile solution and has the following characteristics: • • • Further simplifies the compound attribute relationship from Method 2 into a simple attribute relationship Provides the ability to view item and color together or independently Requires only one attribute column in the fact table for complete flexibility. rather than two Here you must create a new attribute. You treat one attribute as a child of the other and have a compound key for the lower level attribute. you add both attribute IDs.6 The Context of Your Business Data: Attributes Project Design Guide Method 2 Method 2 eliminates the many-to-many relationship and the need for a distinct relationship table. which gives it a 170 Attribute relationships © 2007 MicroStrategy.

you can use this single value in the fact table.Project Design Guide The Context of Your Business Data: Attributes 6 one-to-many relationship between itself and each of its parent attributes. Such attributes are called joint children. This is the SKU attribute. which extends the relationship of each item/color combination into a single value. Inc. Attribute relationships 171 . as well as possibly adding complexity to the ETL process. Joint child relationships Some attributes exist at the intersection of other indirectly related attributes. The major difference is that the distinct relationship table from Method 1 has an additional column. particularly common in retail data models or situations. The major disadvantage of Method 3 lies in creating the new attribute if your business model does not already use a similar structure. They do not fit neatly into the modeling schemes you have learned about thus far. like facts. Finally. SKU. These relationships can be modeled and conceptualized like traditional attributes but. text facts. This method is actually quite similar to Method 1. or qualities. Consequently. © 2007 MicroStrategy. Joint child relationships connect special attributes that are sometimes called cross-dimensional attributes. you only need to include this new child attribute SKU. they exist at the intersection of multiple attribute levels. rather than including Color and Item in the fact table. as shown in the following diagram.

you might create 172 Attribute relationships © 2007 MicroStrategy. Promotion has a many-to-many relationship to both Item and Quarter. . Supporting joint child relationships One way to resolve a many-to-many relationship is to have a relationship table for the attributes involved in the many-to-many relationships. For example. and Quarter. Therefore. In this case. A business might run this promotion around Valentine's Day and again at Christmas time. Inc. as shown in the following diagram. In this case. Joint child relationships are really another type of many-to-many relationship where one attribute has a many-to-many relationship to two otherwise unrelated attributes. An example of a promotion might be a “Red Sale” where all red items are on sale. Item. these are likely candidates for joint child relationships.6 The Context of Your Business Data: Attributes Project Design Guide Many source systems refer to these special attributes as flags. consider the relationship between three attributes: Promotion. if flags are referenced in your source system documentation.

it does not necessarily have to be in its own. Inc.Project Design Guide The Context of Your Business Data: Attributes 6 two relationship tables. Alternatively. These two tables are sufficient to answer questions such as: • • What items have been in what promotions? What quarters have had what promotions? However. However. The second relates Promotion and Quarter as shown in the following diagram. Promotion—would be fine. you can build the relationship directly into the fact table. © 2007 MicroStrategy. distinct relationship table. The relationship in the distinct relationship table must exist for a joint child relationship to be properly defined. Attribute relationships 173 . you must combine the two relationship tables. one to relate Promotion and Item. these tables are not sufficient to answer the following more detailed and insightful questions: • • What items were in what promotions in a given quarter? In what quarters was a certain item involved in a certain type of promotion? To answer these questions. Defining the relationship directly in the lookup table for the parent of the joint child—in this case. creating one table to relate all three attributes.

Inc. as opposed to it being related to Item and Quarter separately. The issues with many-to-many relationships—loss of analytical capability and multiple counting—also apply to many-to-many joint child relationships. This ensures that when you need to join the fact table to the parent attribute of a joint child relationship—for example. Notice that a joint child relationship can be one-to-many or many-to-many. it is important for you to define it in MicroStrategy so that you get the correct data for reports that use the parent attribute in a joint child attribute. .6 The Context of Your Business Data: Attributes Project Design Guide In these examples. If you have a joint child relationship in your data. The Promotion attribute is related to a particular Item-Quarter pair. This is the essence of a joint child relationship and is shown in the following diagram. It is important to notice the relationship between the three attributes. 174 Attribute relationships © 2007 MicroStrategy. to see sales by promotion—the join will always use both joint children rather than just one or the other.

and thus take up more storage space and be harder to maintain. © 2007 MicroStrategy. LU_AIRPORT. AIRPORT_ID. notice that the attributes Origin Airport and Destination Airport are defined using the same lookup table. in the following image. the attributes are essentially playing different attribute roles. and column. Inc. but you do not want to create two separate lookup tables with identical data. You need to support the logical concepts of an origin airport and a destination airport. Creating two separate lookup tables would create redundancy. it is understood that destination airport data differs from origin airport data.Project Design Guide The Context of Your Business Data: Attributes 6 Attributes that use the same lookup table: Attribute roles Attribute roles allow you to use the same data to define and support two separate attributes. When multiple attributes are defined using the same lookup table and column. Attributes that use the same lookup table: Attribute roles 175 . For example. Suppose you define two attributes that have the same data definition but play different roles in your business model. Although it makes sense to see JFK as either an origin or destination airport on a report. How an attribute plays multiple roles depends on the specific attribute.

In one case. If a report designer places both the Origin Airport and Destination Airport attributes on a report to obtain the number of flights that originated from MIA and arrived at LGA. a separate column exists for each of their roles. If you identify that one of your attributes needs to play multiple roles. such as description. . it refers to the 176 Attributes that use the same lookup table: Attribute roles © 2007 MicroStrategy. however.6 The Context of Your Business Data: Attributes Project Design Guide The Origin Airport and Destination Airport attributes share the same attribute forms. location. This ensures that a report with attributes playing multiple roles returns correct data. as explained in Specifying attribute roles. In the fact table. This occurs because the SQL statement tries to obtain the description of an airport that is both MIA and LGA at the same time (Airport_ID = "MIA" AND Airport_ID = "LGA"). you must create an attribute in the logical model for each of the roles. an empty result set is returned. Inc. the fact columns are ORIGIN_AIRPORT_ID and DESTINATION_AIRPORT_ID. State is another example of an attribute that can have two roles since it relates to both the Vendor and Store attributes. and so on. or various aspects about them. page 177. as shown below. In the following diagram.

where you create multiple attributes that have the same lookup table and allow MicroStrategy to automatically detect the multiple roles. In the other. Specifying attribute roles To see both roles on the same report. For example. as shown in the above diagram. Automatic recognition is enabled by the VLDB © 2007 MicroStrategy. The results may be blank if the data warehouse structure was set up incorrectly. it refers to the location of a store. In an OLTP system.Project Design Guide The Context of Your Business Data: Attributes 6 location of a vendor. To create unique attributes. That is. Inc. The SQL statement tries to obtain the description of a state that is both Arkansas and New York simultaneously. you must treat them as different attributes. The State attribute is therefore said to be playing two roles. a report is created to display vendors from Arkansas who sold to New York stores. they must have different attribute names. In the data warehouse. Attributes that use the same lookup table: Attribute roles 177 . you have the following options: • Automatic attribute role recognition. generating the empty result set. a query involving both Vendor State and Store State needs to use the State table twice in the same query. roles are most often implemented as a single table.

you encounter an error. Automatic recognition does not work if the attributes are in the same hierarchy. the attribute has multiple roles. In this example. for example. Remember this rule to help you identify attribute roles: If you want to see the same attribute multiple times on one report. if you identify that any one of your attributes needs to play multiple roles. is enabled). 178 Attributes that use the same lookup table: Attribute roles © 2007 MicroStrategy. you can have a maximum of 99 attributes defined on the same column of the same lookup table.6 The Context of Your Business Data: Attributes Project Design Guide property Engine Attribute Role Options at the database instance level. it may be the better alternative. Month is the attribute that has multiple roles. For more information. in the State example provided above. • Explicit table aliasing. In summary. and are unable to update the project schema or restart Intelligence Server. Inc. where you create multiple logical tables pointing to the same physical table and define those two logical tables as the lookup tables for the two attributes. an attribute must be created in the logical model for each of the roles. refer to the MicroStrategy System Administration Guide. it is easier to use automatic attribute role recognition. . In a MicroStrategy project in which automatic attribute role recognition is enabled (meaning that the database instance-level VLDB property. If you create more than this number of attributes. however. For example. as Ship Month and Order Month. the two State attributes do not have a common child attribute. meaning that a child attribute is shared. MicroStrategy recommends that you take advantage of automatic role recognition if you do not know the details of the modeling logic or the database. If you are new to MicroStrategy. Engine Attribute Role Options. You can use either automatic attribute role recognition or explicit table aliasing to create the attribute roles. If you are upgrading or have a very complex schema. Table aliasing provides advanced users with more control.

The logical model would look like the following: Note that both roles for the State attribute are included in the logical model so that “State” can be considered from two different perspectives. the logical model must reflect that. Automatic recognition allows these two attributes. can be used for both © 2007 MicroStrategy. Inc. The resulting SQL code contains a self-join with the LU_State table. the request is.” The same lookup table. Since the state in which a vendor resides and the state in which one of the stores is located are two different things. Attributes that use the same lookup table: Attribute roles 179 . Vendor State and Store State. a query involving both Vendor State and Store State needs to use the State table twice in the same query to get correct results. Consider the following sample desired report: Vendor_State_ID=15 (Arkansas) Metrics Vendor State Vendor Store Store State Dollar Sales In this case. You can set up two attributes. Store State and Vendor State. to access the same lookup table. “Show me total sales by Store State for all my vendors in Arkansas (Store State ID = 15). using different attribute names for the same expression. which in most cases simply represents a column or columns in a lookup table. Automatic role recognition works only when the attributes use exactly the same expression. LU_State. both of which use the same lookup table.Project Design Guide The Context of Your Business Data: Attributes 6 Using automatic attribute role recognition In the data warehouse.

The logical model would look like the following. An attribute such as State can play more than one role in the data warehouse. it can represent the Vendor State or the Store State. Explicitly aliasing tables to specify attribute roles Explicit table aliasing provides more robust functionality than automatic recognition. just as it would if you used automatic recognition: 180 Attributes that use the same lookup table: Attribute roles © 2007 MicroStrategy. When you use explicit table aliasing to designate attributes that have multiple roles. The two attributes refer to the same columns of that table. you must select the Engine Attribute Role Options. the State attribute is said to play two roles: it refers to both the location of a vendor as well as the location of a store. To use automatic attribute role recognition. Store State and Vendor State. so advanced users are encouraged to take advantage of this solution. Inc.6 The Context of Your Business Data: Attributes Project Design Guide attributes. if attribute roles are used. See the MicroStrategy Desktop online help or the MicroStrategy System Administration Guide for steps to set this VLDB property. In this case. found in the database instance-level VLDB Properties under Query Optimization. both roles for the State attribute are included in the logical model so that State can be considered from two different perspectives. .

Inc.State_Desc as State_Desc SELECT a13. the two lookup tables LU_State_Store and LU_State_Vendor are used. as shown in the following diagram. but point them each to the same physical table. Attributes that use the same lookup table: Attribute roles 181 . you create separate lookup tables in the schema. Consider the following sample desired report that should provide data about the total sales by Store State for all vendors in Arkansas (Store State ID = 15): Vendor_State_ID=15 (Arkansas) Metrics Vendor State Vendor Store Store State Dollar Sales When explicit table aliasing is used. If you use explicit table aliasing for the Store attribute. LU_State. one table (LU_State_Store) contains the attribute Store State while the other (LU_State_Vendor) contains Vendor State. for both state names. Since they are just different names for the same physical table.Project Design Guide The Context of Your Business Data: Attributes 6 The difference between automatic recognition and explicit table aliasing is that when you use explicit table aliasing. as shown by this sample SQL: SELECT a12. the report accesses the same physical table.State_Desc as State_Desc FROM LU_State a12 LU_State a13 © 2007 MicroStrategy.

4 Right-click LU_State(1). To create attribute roles with explicit table aliasing This procedure provides steps to re-create the example of explicit table aliasing described in this section. the selected table is copied. select Rename.6 The Context of Your Business Data: Attributes Project Design Guide You create table aliases in the Schema Objects/Tables folder in MicroStrategy Desktop. When you create a table alias. you would select the LU_State_Store table for the Store State attribute and LU_State_Vendor for Vendor State. log in to the project source that contains the MicroStrategy Tutorial project and then log into MicroStrategy Tutorial. 1 In MicroStrategy Desktop. 5 Right-click the LU_State table and select Create Table Alias. select Rename. and rename the table as LU_State_Vendor. Logical Tables. Inc. 182 Attributes that use the same lookup table: Attribute roles © 2007 MicroStrategy. You can use the same high-level procedure and concepts as guidelines to create attribute roles in your project setup. 6 Right-click LU_State(1). . An LU_State(1) table is created. An LU_State(1) table is created. Table aliases are one kind of logical table. allowing you to rename a copy of the same table. refer to Appendix C. For information about logical tables. When you are ready to create new attributes—as in the example discussed above—you can map the appropriate table to each attribute. 2 Navigate to the Schema Objects folder. 3 Right-click the LU_State table and select Create Table Alias. and rename the table as LU_State_Store. In the case above. Create the attributes 7 Select the Attributes folder. and then select the Tables folder.

select New. 12 In the Source tables pane. The Create New Attribute Form dialog box opens. 10 In the Available columns pane. select the LU_State_Store table. otherwise the attributes cannot have separate roles. 16 Create a Vendor State attribute with the same sub-procedure (Create the attributes. 11 Select Manual mapping and click OK. You must make sure to map any State Store attribute forms to columns from the LU_State_Store table. This implies that more than one ID column is needed to uniquely identify the elements of that attribute. Do NOT select the LU_State_Vendor table as a source table. double-click STATE_ID.Project Design Guide The Context of Your Business Data: Attributes 6 8 From the File menu. you build a compound © 2007 MicroStrategy. 13 Click OK. 14 Click New to map any other columns to attribute forms for the State Store attribute. Attributes with more than one ID column: Compound attributes 183 . The Attribute Editor opens. select LU_State_Store. Attributes with more than one ID column: Compound attributes A compound attribute is an attribute with more than one column specified as the ID column. 15 Save the State Store attribute once you are finished mapping attribute forms to columns of the LU_State_Store table. and then Attribute. Inc. page 182) used to create State Store above. 9 From the Source table drop-down list. Generally. The Create New Form Expression dialog box opens. except you must use the LU_State_Vendor table instead of the LU_State_Store table.

Class and Item. The item shirt has an Item_ID of 1. there are different shirts. For information about form groups. to uniquely identify a man’s shirt. each distribution center has a unique identification number. see Collections of attribute forms: Form groups. To uniquely identify a distribution center. Inc. regardless of country. one must know two details about the distribution center: the ID of the distribution center and the country in which it exists. a retail project has two attributes. depending on the class—men’s. and children’s. They should also use the same lookup table. creating a compound attribute. Example: Creating compound attributes Distribution Center is an example of a compound attribute in the MicroStrategy Tutorial. 184 Attributes with more than one ID column: Compound attributes © 2007 MicroStrategy. . This creates a unique identifier for each distribution center. However. Class is the parent of Item and has a one-to-many relationship with it. but in the same country. a compound key is a primary key that consists of more than one database column. page 186. The same Distribution Center identification numbers can exist for different distribution centers. Therefore. women’s. In the relational database. When defining the ID form. All of the ID forms of the compound attribute should be grouped together using form groups. For example. Item_ID and Class_ID must be grouped together. Therefore. Distribution Center. This data is represented by the Dist_Ctr_ID and Country_ID columns respectively. It is an attribute that requires that two different columns are specified as the ID column. select the source table columns for Country ID and Distribution Center ID. with two attribute forms.6 The Context of Your Business Data: Attributes Project Design Guide attribute when your logical data model reflects that a compound key relationship is present. both the Country_ID and Dist_Ctr_ID columns must be mapped to the Distribution Center attribute to ensure that data about distribution centers is displayed correctly and completely on a report. The values in the Item_ID column do not uniquely identify an item. ID and Description. You can create a compound attribute.

11 Select Automatic mapping and click OK. Inc. © 2007 MicroStrategy. The Attribute Editor opens. 4 From the Source table drop-down list. type Country ID. 8 Keep all other defaults. 9 In the Attribute Editor. 2 Navigate to the My Personal Objects folder. and then Attribute. This attribute form maps to the distribution center ID column necessary to complete the definition of the Distribution Center attribute. 10 Double-click the DIST_CTR_ID column to add it to the Form expression pane on the right. refer to the MicroStrategy Desktop online help.Project Design Guide The Context of Your Business Data: Attributes 6 Follow the procedure below to create the Distribution Center compound attribute. The Create New Attribute Form dialog box opens. log in to the project source that contains the MicroStrategy Tutorial project and then log into MicroStrategy Tutorial. and open the My Objects folder. click New to create the other attribute ID form. Attributes with more than one ID column: Compound attributes 185 . To create the Distribution Center compound attribute 1 In MicroStrategy Desktop. For a general procedure to create compound attributes. The Create New Attribute Form dialog box opens. select the LU_DIST_CTR table. This is the table in which the two ID columns of Distribution Center reside. with the Create New Form Expression dialog box displayed on top of it. select New. in the Name field. and click OK. 7 In the Form general information area. 5 Double-click the COUNTRY_ID column to add it to the Form expression pane on the right. 3 From the File menu. 6 Select Automatic mapping and click OK.

16 Because this is only an example. refer to Collections of attribute forms: Form groups. select ID from the Category drop-down list. . You must designate this attribute form as an ID column so that it can be combined with the Country_ID form to create one unique identifier ID for the Distribution Center attribute. 13 In the Form category section. Click Yes.6 The Context of Your Business Data: Attributes Project Design Guide 12 In the Form general information area. type Distribution Center and click OK. The Attribute Editor opens. This is necessary when creating compound attributes. which are attributes with more than one column specified as the ID column. Create a form group 14 A dialog box notifies you that another form (in this case. You must create a form group to create a compound key. type Distribution Center ID Number. Collections of attribute forms: Form groups A form group is a grouping of attribute forms that are related in a way that justifies combining the forms into a single form. You can also use form groups to link similar forms together so that they are displayed together on a report. 15 In the Name field. you create form groups to create compound attributes. Inc. which identifies that an attribute form requires more than one ID column to uniquely identify its elements. in the Name field. 186 Collections of attribute forms: Form groups © 2007 MicroStrategy. The Create New Attribute Form dialog box opens. For basic information and examples about form groups. page 186. In general. with the form group you created in the Attribute forms pane. close the Distribution Center attribute without saving your changes. Click OK. COUNTRY_ID) is already using the ID form category and that you must create a form group to combine the two ID columns.

This is because all countries identify distribution centers with numbers starting at 1. see the procedure To create the Distribution Center compound attribute. By grouping forms. choose the same form category for both forms—you are then prompted to name your new form group. the included forms are joined together and act as one form. Collections of attribute forms: Form groups 187 . you can design a uniquely defined form that groups two or more forms under an attribute. When you create a form group. When you create a form group. © 2007 MicroStrategy. you have a distribution center in London. Distribution Center is an example of a compound attribute. To uniquely identify a distribution center. the Distribution Center attribute is identified using a form group that combines these two forms. For an example of creating a form group (form group creation is a subtask of the complete procedure).Project Design Guide The Context of Your Business Data: Attributes 6 Supporting compound attributes Compound attributes are required when an attribute requires two or more columns to uniquely identify its elements. one needs information from both the Country_ID and Dist_Ctr_ID tables. and you also have a distribution center in Paris. page 185. a compound attribute is created by using a form group to group together two forms to create the attribute’s ID. Therefore. England which has Dist_Ctr_ID=1. For example. In the MicroStrategy Tutorial. France which has a Dist_Ctr_ID=1 as well. To uniquely identify the two distribution centers you must include the Country_ID as part of the attribute ID. In the Attribute Editor. Inc.

6 The Context of Your Business Data: Attributes Project Design Guide Displaying and organizing related forms Form groups are also used to conveniently organize common attribute forms that can be paired on a report. You can group two or more attribute forms together while creating the attribute forms as described in To create the Distribution Center compound attribute. 188 Collections of attribute forms: Form groups © 2007 MicroStrategy. the form group in the diagram below joins the forms Last_Name and First_Name to create the form group Name for the attribute Customer: By grouping these two forms. Inc. log in to the project source that contains the MicroStrategy Tutorial project and then log into MicroStrategy Tutorial. . For example. as described in the procedure below. You can also group two or more attribute forms as a form group after creating all of the attribute forms. page 185. To group attribute forms as a form group 1 In MicroStrategy Desktop. the user can simply display the Name form and the report then includes both the customers’ first and last names.

and then the Item folder. in the Name field. open the Attributes folder. do not save the changes to the Item attribute.Project Design Guide The Context of Your Business Data: Attributes 6 2 Navigate to the Schema Objects folder. type Item Name2. and then right-click the selected attribute forms and select Group. 8 In the Form category area. Inc. and users place an attribute on a report to display details about the particular attribute and how it relates to fact data. 9 Click OK. The Create New Form Expression dialog box opens. 11 In the Name field. The Create New Attribute Form dialog box opens. The Attribute Editor opens. type Item and Foreign Name and click OK. Using attributes to browse and report on data 189 . The Attribute Editor opens. Each © 2007 MicroStrategy. The Create New Attribute Form dialog box opens. 6 Select Automatic mapping and click OK. 10 Select the Item Name 2 and Foreign Name attribute forms. Using attributes to browse and report on data Once attributes are built. 4 Select New. they are used in two primary ways—browsing and reporting. select None. 7 In the Form general information area. Since this is only an example of how to create a form group. A form group which includes an item’s name and foreign name is created for the Item attribute. Users browse through attributes to locate an attribute to use on a report. 3 Double-click the Item attribute. in the Category used drop-down list. The Attribute Editor opens. 5 Double-click the ITEM_NAME column to add it to the Form expression pane on the right.

Browse forms are the attribute forms that appear as a user browses through the element list of an attribute in the Data Explorer in a project. You can modify the attribute forms displayed by: • Right-clicking an attribute on a report or template and selecting the desired attribute forms 190 Using attributes to browse and report on data © 2007 MicroStrategy. instead of the URL attribute form. or project-wide.chicago.com.6 The Context of Your Business Data: Attributes Project Design Guide attribute can be displayed in a variety of forms so you must specify the default display of each of the attributes in the project. This separation allows for greater attribute display flexibility depending on the application. such as Chicago. the first form you create is not included as a report display or browse form. The only exception is if you create multiple attribute forms. If a report lists the cities in which you have stores. a report includes Region as an attribute. browse forms identify attribute elements. the display could be a number such as four. An attribute’s report display forms determine which attribute forms are displayed by default when the report is executed. In Grid view. These browse forms are found in the Report Objects pane. You can also select which attribute forms are retrieved with the report results but not displayed on the grid. default for each attribute. Therefore. For example you can include a cities URL attribute form as a browse attribute form so that your users can choose to display the form on a report. Inc. you select a different set of values for display. Report display forms are the attribute forms that appear as columns in a completed report. . If ID is selected as the attribute form. www. For example. You must choose a default attribute display for browsing and another for reporting. but you still must specify the global. the display could be a name. all forms are included as report display forms and browse forms by default. By selecting different forms for the attribute. you can add the attribute forms in Report Objects to the report without re-executing the report. You can do this on a report-by-report basis. If Description is selected as the attribute form. then you might choose to display the Long Description form. When creating attributes. that is. such as Northwest.

For a general procedure to set how attribute forms are displayed by default. you can specify whether the identification number of each distribution center. selecting Attribute Display to open the Attribute Display dialog box For steps to display attribute forms on a report or template. displays the actual name of the Distribution Center such as “San Diego. however. the Dist_Ctr_ID form shows the identification numbers of specific distribution centers in the data warehouse. The Description form of Distribution Center.” You can use the Attribute Editor to determine how the attribute forms are displayed on a report. The ID form group is made up of two separate ID columns. In the case of the Distribution Center attribute. Setting how attribute forms are displayed by default You can generally display attribute forms in a number of ways. the distribution center names. © 2007 MicroStrategy. Displayed on a report. You can also determine which attribute forms are displayed when browsing a project with the Data Explorer. refer to the MicroStrategy Desktop online help. Inc. or both are displayed.Project Design Guide The Context of Your Business Data: Attributes 6 • From the Data menu. Country_ID and Dist_Ctr_ID. Follow the example procedure below to set one of the Distribution Center attribute’s forms to be displayed in reports and while browsing the MicroStrategy Tutorial project. see the online help and the section below. the Distribution Center attribute in the MicroStrategy Tutorial consists of an ID form group and a Description form. For example. Using attributes to browse and report on data 191 .

3 Click the Display tab. You can also determine how attributes are displayed while users are editing and viewing reports. 5 Because this is only an example. the actual names of the distribution centers are displayed. close the Attribute Editor without saving your changes. See the MicroStrategy Basic Reporting Guide for details. page 209. The Data Explorer makes hierarchies available for users to facilitate placing objects on reports. The ID 2 form in the Available forms pane represents the distribution centers’ identification numbers. To set the ID 2 form so it is displayed in the Data Explorer when a user browses the Distribution Center attribute: Select ID 2 from the Available forms pane and click the bottom > button to add the form to the Browse forms pane on the right. • 192 Using attributes to browse and report on data © 2007 MicroStrategy. when the Distribution Center attribute is used on a report. The Attribute Editor opens. The Data Explorer is discussed in Enabling hierarchy browsing in reports: Data Explorer. This means that. On the right. Inc. 4 You can set the ID 2 form to be displayed in the following ways: • To set the ID 2 form as a form that is displayed on a report by default: Select ID 2 from the Available forms pane and click the top > button to add the form to the Report display forms pane on the right. . navigate to the Schema Objects folder.6 The Context of Your Business Data: Attributes Project Design Guide To display an attribute form in reports and in the Data Explorer 1 In the MicroStrategy Tutorial. 2 Double-click the Distribution Center attribute. open the Attributes folder. the description form of the Distribution Center is set as the only display form. in the Report display forms pane. and then the Geography folder.

Month. you learned how to use hierarchies to group related attributes in practical business areas. These types of hierarchies include the system hierarchy and the user hierarchy. to reflect the relationships that exist between the attributes in a project. you can include a Time hierarchy in your model that consists of Day. This chapter discusses hierarchies as they exist in the MicroStrategy environment and provides information on the two different types of hierarchies in MicroStrategy. either ordered or unordered.7 7. In Chapter 2. The Logical Data Model. Inc. 193 . The system hierarchy is automatically created when you create a project and is maintained by the © 2007 MicroStrategy. For example. and Year attributes. Week. CREATING HIERARCHIES TO ORGANIZE AND BROWSE ATTRIBUTES Introduction Hierarchies are groupings of attributes that can be displayed.

.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide relationships that exist among the project’s schema objects. Follow the procedure below to learn how to create a user hierarchy. page 196. see Types of hierarchies. Inc. 194 Creating user hierarchies © 2007 MicroStrategy. For information on user hierarchies and system hierarchies. Creating user hierarchies In MicroStrategy Desktop. The user hierarchy is a hierarchy which you create specifically for your report designers. This chapter explores how to create and configure user hierarchies in MicroStrategy and provides additional information about hierarchy functionality in MicroStrategy Desktop. you create user hierarchies using the Hierarchy Editor.

This procedure is covered in Viewing and editing the parents and children of attributes. and then the Data Explorer folder. page 161. in the Available objects window. Drill hierarchies are discussed in Drilling using hierarchies. from the View menu. navigate to and open the Schema Objects folder. or filtered. The Hierarchy Editor opens. 3 Open the Hierarchies folder. assign the appropriate parent or child relationship to the attributes. The attributes you selected appear in the Hierarchy Viewer. Click OK to close the Select Attributes dialog box. and then Hierarchy. select the attributes to use in the hierarchy and click the arrow to add them to the Selected objects window. arrows appear between related attributes. 7 Click Save and Close. 4 From the File menu. © 2007 MicroStrategy. Creating user hierarchies 195 . you must edit the attribute(s) in the Attribute Editor. and update the schema. followed immediately by the Select Objects dialog box. an entry point. a dialog box opens notifying you that the hierarchy you are about to save is drillable in reports. log into the project source that contains your project and open the project. Inc.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 To create a new user hierarchy 1 In MicroStrategy Desktop. 6 In the Hierarchy Editor. The arrows that connect certain attributes denote the presence of a relationship between the connected attributes. 5 In the Select Attributes dialog box. page 209. If the Use as a drill hierarchy check box at the bottom of the Hierarchy Editor is selected. 2 In the Folder List. select New. These details include whether or not the attribute is locked. If arrows do not appear between attributes you know are related. select Show Details. Once you save and re-open the hierarchy. To do so. you can view the details of each attribute in the hierarchy. Type a name for the hierarchy.

you must place it in the Data Explorer sub-folder within the Hierarchies folder. User hierarchy: User hierarchies are named sets of attributes and their relationships to each other. The ordering and grouping of attributes. As the structure of your business intelligence evolves. • 196 Types of hierarchies © 2007 MicroStrategy. Inc. among other configurations. You can save user hierarchies in any folder. Although the system hierarchy specifies an ordered set of all attributes in the project. navigate to the location in which you want to save the hierarchy. to make the user hierarchy available for element browsing in the Data Explorer. is defined in user hierarchies. This type of hierarchy is created to provide flexibility in element browsing and report drilling. arranged in specific ways that make sense to a business organization. it is automatically created in Desktop when you create a project. it does not define ordering or grouping among attributes.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide 8 In the Save As dialog box. You do not need to create the system hierarchy. you can easily change the design of a user hierarchy to include additional attributes or limit user access to certain attributes. However. page 194. Steps to create user hierarchies are discussed in Creating user hierarchies. . They are user-defined and do not need to follow the logical data model. 9 Update the project schema by selecting Update Schema from the Schema menu. Types of hierarchies The two types of hierarchies that exist in MicroStrategy include: • System hierarchy: The system hierarchy is created according to the relationships defined between the attributes in your project.

Month. Any attributes that are not assigned to a user hierarchy remain available to the system as report objects. The system hierarchy cannot be edited but is updated every time you add or remove attribute children or parents in the Attribute Editor. These report objects are discussed in detail in the MicroStrategy Advanced Reporting Guide. You create user hierarchies to define the browse and drill relationships between attributes. The system hierarchy holds information on the relationships between attributes in the project. The system hierarchy is useful in determining relationships between all objects in the project. arranged in specific sequences for a logical business organization. It contains all of the attributes in the project and is actually part of the schema definition. and components of consolidations. Types of hierarchies 197 . Quarter. the only hierarchy it contains is the system hierarchy. filter conditions. For example. you can double-click Year to get to Quarter and double-click Quarter to get to Month. and so on. You can access the Hierarchy Viewer from Graphical View in the Schema menu. © 2007 MicroStrategy. When you browse the attributes in the Data Explorer. Attributes from the system hierarchy do not need to be part of an explicitly-defined user hierarchy. You can view the system hierarchy in the Data Explorer or in the Hierarchy Viewer. or when you define attribute children in the Project Creation Assistant. but not the Hierarchy Editor. Inc. and Day attributes. User hierarchies: Logical business relationships User hierarchies are sets of attributes and their relationships.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 System hierarchy: Project schema definition The system hierarchy is the default hierarchy that MicroStrategy sets up for you each time you create a project. When you first create a project. page 211. you can create a Time hierarchy that contains the Year. The Hierarchy Viewer is discussed in detail in Using the Hierarchy Viewer.

You can create user hierarchies in the Hierarchy Editor using one or more attributes from the system hierarchy. For example. . You should define user hierarchies that correspond to specific areas of your company business model and data warehouse schema. 198 Hierarchy organization © 2007 MicroStrategy. The Customer hierarchy also groups together the attributes Company. you can place related attributes into hierarchies by their level. City. in drilling the user actually chooses to move to higher or lower levels on a report or move across to levels within different hierarchies.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide Whereas browsing occurs through the Data Explorer. and Store are organized according to their relationships to each other. Hierarchy organization The best design for a user hierarchy is to organize or group attributes into logical business areas. State. The example below demonstrates the Location and Customer hierarchies. Within the Location hierarchy. For example. or across to an attribute within another hierarchy. and Customer. he or she can drill down to Month. if the user drills on the Quarter attribute in a report. and you can create any number of user hierarchies for each project. Contact. A user hierarchy is the only type of hierarchy you can define. This allows users to more easily locate attributes in a project and navigate from one attribute to another. up to Year. Inc.

and Store on a report. State. only the user hierarchy allows you to logically define and order groups of attributes. The rest of this chapter discusses user hierarchies and how to create and configure them in your project. This hierarchy allows you to create drilling and browsing options to the lower levels to view Region. keep in mind that hierarchies do not have to be separate from one another or necessarily follow the dimensional structure of your logical data model. Hierarchy organization 199 . Inc. then the only options for drilling or browsing are the Region and Store levels. When you group attributes together into user hierarchies. In the example below. Hierarchy structure While both a system hierarchy and user hierarchy allow you to navigate attributes in your project. as in the second example. there are two instances of the Region hierarchy.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 When creating user hierarchies. © 2007 MicroStrategy. One hierarchy demonstrates Region having multiple States and the States having multiple Stores. However. you are developing a working design of the display and browse functions of the attributes. if you only include Store in the Region hierarchy.

7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide Viewing hierarchies: Hierarchy Viewer The Hierarchy Viewer graphically represents user hierarchies and the system hierarchy. Inc. or limited (see Controlling the display of attribute elements. Attribute Filters: Specifies whether the data retrieved and displayed should be complete or filtered by any specific criteria. the connections between the attributes represent the parent-child relationships. In user hierarchies. You can use the Hierarchy Editor to configure each of these properties. In the system hierarchy. • • • 200 Configuring hierarchy display options © 2007 MicroStrategy. Configuring hierarchy display options Each attribute in a user hierarchy has properties that affect how that attribute is displayed and accessed in a hierarchy. unlocked. Represented by lines that connect one attribute to others (see Hierarchy browsing. The Hierarchy Viewer is discussed in further detail in Using the Hierarchy Viewer. page 206). The Hierarchy Viewer is accessed from the Graphical View option in the Schema menu. The element display may be locked. Browse Attributes: Shows the attributes to which users can browse from a given attribute. . its decreased scale allows you to navigate through the entire project. A filter on a hierarchy acts like a filter in a report. page 205). page 203). Entry Point/Not an Entry Point: Specifies whether the user can begin browsing in this hierarchy using this attribute (see Entry point. as shown in the following procedures: • Element Display: Determines the elements a user can see. page 201). Only data satisfying the filter criteria is displayed (see Filtering attributes in a hierarchy. page 211. the connections show the browse paths between the attributes. The Aerial perspective provides an overview of hierarchies.

the attribute Order is locked in the Data Explorer sample shown below. When you set the element display to locked. The Order attribute may be locked in order to prevent unauthorized users from accessing sensitive information about customer orders. © 2007 MicroStrategy. you can prevent the expansion of long attribute element lists that can consume system resources.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 The following sections explain these properties and how to use the Hierarchy Editor to configure each. he or she cannot view information about each customer’s order. Anything higher in the hierarchy is still visible. Controlling the display of attribute elements Locked/Unlocked attribute elements Locking a hierarchy prevents a user from viewing all elements of the specific attribute and any lower level attributes in the hierarchy. You can lock the hierarchy to restrict the user from viewing elements and lower level attributes for security reasons or to better manage lengthy hierarchies. For example. While the user can view the attribute elements of Customer Region and Customer City. a padlock icon appears next to the attribute name. By restricting the view of attribute elements and lower level attributes in the Data Explorer. Configuring hierarchy display options 201 . Inc. A hierarchy is referred to as locked when at least one attribute within that hierarchy has the Element Display option set to Locked.

select Element display. retrieving a large number of elements at once can negatively impact system performance. The user can then click the arrows to see the next set of elements for that attribute. A padlock icon appears next to the locked attribute. You can also lock and unlock attributes when you edit them in the Display tab of the Attribute Editor. However.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide To lock or unlock an attribute in a hierarchy 1 Double-click the hierarchy to edit. you can set the limit to five or ten at a time. and users can now view the elements of this attribute. 6 Update the project schema by selecting Update Schema from the Schema menu. no elements for Year display in the Data Explorer when Year is expanded. Instead of loading all attribute elements at once. Inc. The Hierarchy Editor opens. from the right-click menu. from the right-click menu. . This method is useful when there are extensive attribute elements in a hierarchy. Also. 3 To lock an attribute. 202 Configuring hierarchy display options © 2007 MicroStrategy. Limited attribute elements Another way to restrict users from viewing attribute elements in the Data Explorer is to limit the number of elements that appear at one time. 4 To unlock a locked attribute. The padlock icon is removed from the attribute. select Element display. 5 In the Hierarchy Editor. and then Unlocked. 2 Right-click the attribute to lock or unlock. this locks and unlocks the attributes within the system hierarchy. click Save and Close. and then Locked. and users can no longer view elements of this attribute. if the attribute Year is locked in the Attribute Editor. not any user hierarchies that contain the attributes. For example.

Inc. select Element display. refer to the Filters chapter in the MicroStrategy Advanced Reporting Guide to understand what filters are and how to create them in MicroStrategy. For example. The following graphic displays this view in the Data Explorer. click Save and Close. a limit of five items has been set. the Chocolate subcategory. Filtering attributes in a hierarchy Before reading this section. 4 In the Hierarchy Editor. you can filter a hierarchy so that data for only one © 2007 MicroStrategy. shown below. 2 From the right-click menu. 5 Update the project schema by selecting Update Schema from the Schema menu. contains many items. right-click the attribute to limit. You can add filters to a hierarchy to control how data is retrieved and displayed. 3 In the Limit dialog box. type the number of elements you want to see at one time and click OK. and then Limit. With a filter you can choose exactly which attribute elements to display in a hierarchy. Rather than displaying all of them at once and overwhelming the user.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 For example. To limit the display of attributes in a hierarchy 1 In the Hierarchy Editor. Configuring hierarchy display options 203 .

and view the Customer hierarchy in the Data Explorer. In the Hierarchy Editor. and the user is unable to see additional data in the hierarchy. you are limiting the elements of the data returned when you browse the Data Explorer. or data for only a few days of one quarter. To apply a filter to an attribute in a hierarchy 1 Create a filter in MicroStrategy Desktop.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide quarter is displayed. When adding filters to an attribute in a hierarchy. 3 If a tip about filtering opens. You cannot use a prompt-based filter to filter a hierarchy. When filtering attributes in a hierarchy. you need to make sure that each filter is relevant to the attribute’s information. however. click OK. First. Filters make data retrieval faster by only allowing specific data to be displayed. Creating a limited hierarchy reduces the number of elements displayed at one time. Each attribute in the hierarchy can have multiple filters applied to it. Only those customers younger than 30 years old are displayed. The filters allow the Data Explorer to display only the criteria you select. MicroStrategy does not validate that the associated filter makes sense on that attribute. 2 In the Hierarchy Editor. add the filter to the Customer attribute. 204 Configuring hierarchy display options © 2007 MicroStrategy. perform a type of security. For example. Inc. right-click the attribute to filter and select Define Attribute Filters. limit the elements a user is allowed to see and therefore. you want to view only those customers who are younger than 30 years old. See the MicroStrategy Desktop online help for more details. . Update the project schema. Filters increase efficiency when retrieving data because you can limit user access to parts of a hierarchy when you apply filters to attributes. Filters. create a filter on Customer Age less than 30.

© 2007 MicroStrategy. you are creating a shorter route to access that attribute. You can see the locked attribute. the attribute Week appears in the Data Explorer at the same level as Year. it still appears in the hierarchy but with a padlock icon. a typical hierarchy is Time. This is especially useful when accessing frequently-used attributes. it appears in its normal position within the hierarchy structure. such as Q1. To create entry points in a hierarchy 1 In the Hierarchy Editor. select the filters to apply and click > to add them to the Selected objects list. If you set the attribute Week as an entry point. When you click on 2006. Entry point An entry point is a shortcut to an attribute in the Data Explorer. and Q4. right-click the attribute to set as an entry point. elements for each Year. 6 In the Hierarchy Editor. such as 2007. you need to open several levels of attributes to reach the correct data level. the attributes. the hierarchy. Q3. an element for each Quarter. Creating an entry point grants users faster access to the attribute without having to browse through multiple attributes to reach different levels in a hierarchy. in the Available objects list. If an attribute is not set to be an entry point. 2006. 5 Click OK to close the Select Filters dialog box. If you are seeking Week 24. opens. Inc. When you set an attribute to be an entry point. Q2. and their elements appear in the Data Explorer. click Save and Close. The attribute to which you applied the filter appears in the hierarchy with a filter icon. open. but are unable to access elements or attributes below that level. When you click on Time. For example. Configuring hierarchy display options 205 . and 2005. If you set a locked attribute as an entry point. When you create a user hierarchy.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 4 In the Select Filters dialog box. which is Week.

Category is a parent attribute of Category and Category is the child attribute of Category. showing the parent/child relationships between the attributes. 4 Update the project schema by selecting Update Schema from the Schema menu. These relationships determine how users can browse the attributes from the Hierarchies folder. Category. For example. attributes set as entry points are denoted by a green check. you can define the relationships between them. Inc. the hierarchy resembles the example below. Subcategory. 3 In the Hierarchy Editor. 206 Configuring hierarchy display options © 2007 MicroStrategy. click Save and Close. in the hierarchy below. if Catalog. Some of the attributes in the Hierarchy Viewer may already be set as entry points. select Set as entry point.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide 2 From the right-click menu. select Remove Entry Point from the right-click menu. . and Item are the attributes that comprise the user hierarchy Catalog Items. Hierarchy browsing Once you choose which attributes to place in a hierarchy. For example. To remove an entry point from an attribute.

It can simply be a collection of attributes. see Enabling hierarchy browsing in reports: Data Explorer. Inc. Configuring hierarchy display options 207 . Subcategory Subcategory Catalog. For each attribute in a hierarchy. you can assign one or more browse attributes to it. Using the example above. Including hierarchies in the Data Explorer makes the hierarchies available for reports and to users in the project. For more information on including hierarchies in the Data Explorer. without having to first browse down through the Category © 2007 MicroStrategy. Specifically: Hierarchy Attribute Catalog Category Subcategory Item Browse Attribute(s) Category. Item The addition of these browse attributes allows users to see the Subcategory elements directly from the Catalog attribute. some of these attributes have been assigned a browse attribute. page 209. Browse attributes are attributes you specify a user can directly browse to from a given attribute in the user hierarchy.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 A user hierarchy does not need to have these direct relationships defined. When you apply browse attributes to attributes in a hierarchy. you are specifying what levels of detail are visible when browsing the Data Explorer. Attributes in a hierarchy can have both browsing and drilling relationships between them.

7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide attributes to get to Subcategory. Users can now view the subcategories in the catalog without first having to browse through the categories. Inc. the hierarchy described above resembles the example below. The ability to browse more directly through the hierarchy can be represented as shown below. 208 Configuring hierarchy display options © 2007 MicroStrategy. . In the Data Explorer.

You can save user hierarchies in any folder. When a user selects a drilling path in a report. on the new report.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 Enabling hierarchy browsing in reports: Data Explorer You can make hierarchies available for browsing and including in reports by storing the hierarchies in the Data Explorer. the attributes to which users can drill from other attributes. which contains the two attributes. This allows a user to drill down from Year to Month and. at a project level. if they need to. on a report with the Year attribute and Revenue metric. drill back up from Month to Year. The Data Explorer is a tool in the Object Browser that holds the system hierarchy and the user hierarchies. the user can drill down on the Year attribute to a lower level attribute such as the Month attribute. up. This option enables you to determine. to make a user hierarchy available for browsing in the Data Explorer you must place it in the Data Explorer folder—a subfolder of the Hierarchies folder. Depending on the level of the attributes included in the drilling specification. drilling is enabled in the Time hierarchy. Drilling using hierarchies Drilling is a function in MicroStrategy reports that allows users to browse different levels of attributes along specified paths. reports can allow users to drill down. Revenue data is reported at the Month level. When you create a new project. Inc. Configuring hierarchy display options 209 . which is located in the Schema Objects folder. You can make user hierarchies available for drilling. In the example of the Year and Month attributes. Moving hierarchies to and from this folder also allows you to keep some hierarchies visible to users while hiding others. and across to different levels of detail. the report refreshes to display the selected level of detail. However. © 2007 MicroStrategy. For example. A new report is automatically executed. the system hierarchy for that project is automatically placed in the Data Explorer.

210 Configuring hierarchy display options © 2007 MicroStrategy. the default drill path is defined by the System Hierarchy. page 206 for more details about browsing attributes. click Save and Close. you can drill from Catalog down to Subcategory—and any other browse attributes of Catalog—on a report. 2 At the bottom of the Hierarchy Editor. Therefore. 3 In the Hierarchy Editor. . you must enable the user hierarchy to be used as a drill hierarchy in the Hierarchy Editor. Subcategory is a browse attribute of Catalog. For example. which means that you can access the elements of Subcategory without having to necessarily access the elements of Catalog in Data Explorer. select the Use as a drill hierarchy check box. 4 Update the project schema by selecting Update Schema from the Schema menu.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide To enable a user hierarchy as a drill path. Inc. To enable drilling in a user hierarchy 1 Open the hierarchy in which to enable drilling. you can think of browsing paths in a user hierarchy as potential drilling paths. If you enable drilling in this hierarchy. If a user hierarchy is not enabled. in the following hierarchy. See Hierarchy browsing.

but rather the structure of the user hierarchy as defined by a project designer. Additional information on drilling is available in the MicroStrategy Advanced Reporting Guide. When a user right-clicks on Year and selects Drill Down. or you may select only one at a time. You can use the Hierarchy Viewer to view either the system hierarchy or any of your user hierarchies. you can see the actual relationships between attributes. and also allows you direct access to the attributes that comprise it. For details on entry points. assume Week is a browsing attribute assigned to Year. the attribute Week appears in the drill-down list. For instance. Using the Hierarchy Viewer The Hierarchy Viewer allows you to select the hierarchy you want to examine.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 After a user hierarchy is enabled for drilling. • When you view the system hierarchy. © 2007 MicroStrategy. MicroStrategy Architect gives you the ability to view the system hierarchy as well as all of your user hierarchies in a single place. It is used to view all of the tables in your project graphically. to facilitate user browsing and report development. Using the Hierarchy Viewer and Table Viewer 211 . The Table Viewer is another tool within MicroStrategy Architect that provides you with a bird’s eye view of some of the information within your project. You can see all of the entry points into a hierarchy at once. • The Hierarchy Viewer gives you flexibility over how much of a given hierarchy you choose to view at once. When you view a user hierarchy. page 205. see Entry point. Inc. you do not see true attribute relationships. Using the Hierarchy Viewer and Table Viewer Through the Hierarchy Viewer. as defined by the system when the project was created. the hierarchy contributes to the drilling path of any attributes in it.

from the Schema menu. page 205 for more details on creating entry points. you can define them as entry points. See Entry point. To edit an attribute from the Hierarchy Viewer 1 In the Hierarchy Viewer. See Entry point. To view a user hierarchy in the Hierarchy Viewer 1 In the Hierarchy Viewer. from the Hierarchy menu. An aerial view of the hierarchy you are currently viewing is displayed. the Aerial perspective provides an overview of the hierarchies in your project. right-click the attribute to edit. . page 205 for more details on creating entry points. 2 Attributes that have a green check mark next to them are entry points. 2 Select Edit. select the hierarchy to view. select Aerial perspective.7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide The Hierarchy Viewer also gives you direct access to any of the attributes in the hierarchy you choose to view. To view the system hierarchy in the Hierarchy Viewer 1 In MicroStrategy Desktop. 2 Select Hierarchies. Its decreased scale allows you to navigate through the entire project. In the Hierarchy Viewer. To access Aerial perspective mode in the Hierarchy Viewer 1 In the Hierarchy Viewer. from the View menu. 212 Using the Hierarchy Viewer and Table Viewer © 2007 MicroStrategy. The green squares indicate attributes that are entry points. When you access a hierarchy’s attributes directly. select Graphical View. Inc.

select Graphical View. as described above. If you make changes to the actual tables in the data warehouse. See The size of tables in a project: Logical table size. Inc. © 2007 MicroStrategy. select Options. The tables that are displayed here are logical tables. page 249 for information on updating logical table structures. Using the Table Viewer The Table Viewer allows you to view all of the tables in your project as well as the joins and/or relationships between those tables and the names of the individual columns in each table. 2 In the Table Viewer. Click a section of the aerial view display to shift your view of a hierarchy to that particular section. They represent and indicate how Architect sees the tables that were brought into the project when it was created. from the Schema menu.Project Design Guide Creating Hierarchies to Organize and Browse Attributes 7 2 The hierarchy in the Hierarchy Viewer shifts according to where you navigate in the aerial view. To view more or less information about each table in the project 1 Open the Table Viewer. 2 Select Tables. Using the Hierarchy Viewer and Table Viewer 213 . you will need to update the logical table structure. To view your project’s tables in the Table Viewer 1 In MicroStrategy Desktop.

select or clear the options for any of the following. Inc. depending on what you want to see in the Table Viewer: • • • • • Show joins Use circular joins Show relationships Show relationship types Show columns 214 Using the Hierarchy Viewer and Table Viewer © 2007 MicroStrategy. .7 Creating Hierarchies to Organize and Browse Attributes Project Design Guide 3 From the Options menu.

© 2007 MicroStrategy. you must update your project schema. Inc.8 8. creating aggregate tables. page 216—As you continue to enhance the design and functionality of your project. and using partition mapping. This chapter introduces you to maintenance and optimization concepts such as tuning the interaction between your data warehouse and your project. you will need to make various schema changes. and explains how to use these methods to enhance your project. OPTIMIZING AND MAINTAINING YOUR PROJECT Introduction Once your MicroStrategy project is set up and populated with schema objects. you are ready to start thinking about ways to better maintain the project and optimize it for both the short and long term. To see any enhancements and changes to your project schema. 215 . You can find this information in the sections listed below: • Updating your MicroStrategy project schema.

and minimize the amount of data that must be aggregated and sorted at run time. You can also tune the interaction between your data warehouse and your MicroStrategy project to bring your data into MicroStrategy in a way that meets your requirements. table sizes. You can do any of the following to update your project schema: 216 Updating your MicroStrategy project schema © 2007 MicroStrategy. your project must reflect these changes. Dividing tables to increase performance: Partition mapping. • • Updating your MicroStrategy project schema All of the schema objects—facts. Rather. Although the concepts are related.8 Optimizing and Maintaining Your Project Project Design Guide • Data warehouse and project interaction: Warehouse Catalog. and so on—in your project come together to form your project’s schema. Using summary tables to store data: Aggregate tables. attributes. transformations. page 241—Aggregate tables store data at higher levels than the data was originally collected in the data warehouse. Partitions improve query performance by minimizing the number of tables and records within a table that must be read to satisfy queries issued against the warehouse. page 250—Partition mapping involves the division of large logical tables into smaller physical tables. reduce input/output and other resource requirements. and so on within the project. hierarchies. . These summary tables provide quicker access to frequently-used data. the project schema refers to an internal map that MicroStrategy uses to keep track of attribute relationships. Inc. Whenever you make any changes to a schema object you must indicate to MicroStrategy that new schema object definitions have been included and that these definitions need to be loaded into memory. fact levels. This can include adding new tables to your project or removing tables that are no longer used. the project schema is not the same as the physical warehouse schema. page 218—As your data warehouse changes to meet new data logging requirements.

if in server-connected (3-tier) mode. modified. Recalculate table keys and fact entry levels: Use this option if you changed the key structure of a table or if you changed the level at which a fact is stored. Logical table sizes are a significant part of how the MicroStrategy SQL Engine determines the tables to use in a query. if in direct (2-tier) mode. Manually updating the schema allows you to determine which specific elements of the schema are updated.Project Design Guide Optimizing and Maintaining Your Project 8 • • • Stop and restart MicroStrategy Intelligence Server. Recalculate table logical sizes: Use this option to use MicroStrategy Desktop’s algorithm to recalculate logical table sizes and override any modifications that you have made to logical table sizes. Disconnect and reconnect to the project or the project source. Inc. 2 In the Schema Update dialog box. • Recalculate project client object cache size: Use this option to update the object cache size for the project. You can also update the schema with the last saved settings by clicking the Update Schema icon in the toolbar. select or clear the following check boxes: • • Update schema logical information: Use this option if you added. • 3 Click Update. select Update Schema. Manually update the schema. Updating your MicroStrategy project schema 217 . or deleted a schema object. © 2007 MicroStrategy. To manually update the schema 1 In MicroStrategy Desktop. from the Schema menu.

page 221 Modifying data warehouse connection and operation defaults. From this list. . the structure of the SQL catalogs. This section covers the following topics: • • • • • • • What should I know before I use the Warehouse Catalog?. Inc. page 233 Troubleshooting table and column messages. and the default SQL statements used for each database.8 Optimizing and Maintaining Your Project Project Design Guide Data warehouse and project interaction: Warehouse Catalog This section discusses how the Warehouse Catalog can control the interaction between the data warehouse and the database instance for a project. adding tables in the project through Project Builder can become a cumbersome process. page 219 Accessing the Warehouse Catalog. page 220 Managing warehouse and project tables. This section also discusses customizing catalog SQL statements. The Warehouse Catalog queries the data warehouse and lists the tables and columns that exist in it. Every project can have a unique set of warehouse tables. page 219 Adding and removing tables for a project. page 226 Customizing catalog SQL statements. You can add warehouse tables to your project with the Warehouse Catalog or MicroStrategy Project Builder. The Warehouse Catalog is better for maintaining the warehouse tables used for an existing project. you can select the tables to add to your project. Adding tables through Project Builder is useful only when you are creating a project for the first time. as later. page 239 218 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy.

For more information on Query Builder. For more information about privileges see the Permissions and Privileges appendix of the MicroStrategy System Administration Guide. Hyperion Essbase. You can connect to OLAP cube sources such as SAP BW. You must use a login that has Architect privileges. then Desktop. • What should I know before I use the Warehouse Catalog? Before you begin using the Warehouse Catalog. see the MicroStrategy Advanced Reporting Guide. and expand your project. then to MicroStrategy. Data warehouse and project interaction: Warehouse Catalog 219 . refer to Appendix B. so you know how the information in your data warehouse should be brought into MicroStrategy How to create a project Accessing the Warehouse Catalog To access the Warehouse Catalog 1 On the Windows Start menu. For more information. Connecting to OLAP Cube Sources. point to Programs. In this case. and Microsoft Analysis Services instead of a relational database. © 2007 MicroStrategy.Project Design Guide Optimizing and Maintaining Your Project 8 Note the following: • You can also add tables to a project using MicroStrategy Query Builder. 2 Log in to the project source that contains your project in MicroStrategy Desktop. the OLAP Cube Catalog handles tasks similar to the Warehouse Catalog. and then select Desktop. Inc. you need to be familiar with: • • Your schema.

and expand your project. select the tables you want to add to the Warehouse Catalog. You can access the Warehouse Catalog at any time to add additional tables from your data warehouse to your project and remove tables from your project. as your project matures. Click >> to add all the listed tables. To add or remove tables after creating a project 1 Access the Warehouse Catalog for your project as described in To access the Warehouse Catalog. The list on the right shows all the tables already being used in the project: • To add tables—From the left side. Click >> to add all the listed tables. Log in to the project source that contains your project in MicroStrategy Desktop. . The Warehouse Catalog opens after it retrieves the table information from the warehouse database. 2 The left side of the Warehouse Catalog lists all available tables and the number of rows each table contains. and click > to add the selected tables. select Warehouse Catalog. select the tables you want to add to the Warehouse Catalog. Also. it may become necessary to add additional tables from the data warehouse to your project. Inc.8 Optimizing and Maintaining Your Project Project Design Guide 3 Select a project and then from the Schema menu. you may need to remove tables from your project that are no longer used and are taking up space in the metadata. • 220 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. and click > to add the selected tables. page 219. To remove tables—From the left side. Adding and removing tables for a project As you become aware of the additional needs of report designers and users.

Managing warehouse and project tables The Warehouse Catalog allows you to view tables that have been included in the project. As you make changes to the tables in the warehouse. by selecting Update Schema. Description • © 2007 MicroStrategy.Project Design Guide Optimizing and Maintaining Your Project 8 3 In the toolbar. You can add or remove all the tables from one section to the other by clicking << and >> buttons. page 219. 4 Update the project schema from the Schema menu. but have not been included in the project. see Accessing the Warehouse Catalog. You can remove tables from the project by double-clicking the tables or by selecting the tables and then clicking <. You can update it by selecting Read the Warehouse Catalog from the Actions menu. Inc. This process can take some time to complete. click Save and Close to save your changes to the Warehouse Catalog. The table definitions are written to the metadata. You can add tables to the project by double-clicking the tables or by selecting the tables and then clicking >. Data warehouse and project interaction: Warehouse Catalog 221 . To access the Warehouse Catalog for a project. as well as those tables that are available in the warehouse but have not been included in the project. Warehouse Catalog has the following menu options. Menu File • Save Saves the current settings and status of the Warehouse Catalog. The Warehouse Catalog has the following sections: • Tables available in the warehouse: Displays tables that are located in the warehouse. you need to periodically load the updates into the Warehouse Catalog. Tables being used in the project: Displays tables that have been selected to be part of the project.

automatic mapping. Allows you to specify various settings for the Warehouse Catalog such as changing the database instance. Allows you to import the prefixes from the warehouse table name space. Calculates the number of rows in the selected tables. right-click any table in the Warehouse Catalog (see Accessing the Warehouse Catalog. row calculation. page 219) and choose Table Structure from the 222 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. For more information. and so on. page 227 of this appendix. Displays the list of tables referred to by the selected partition mapping table in the Table Partitions dialog box. Allows you to add or remove a table prefix for the selected table.8 Optimizing and Maintaining Your Project Project Design Guide Menu • Exit Tools • View Partitions Description Exits the Warehouse Catalog. Viewing table structure To view the table structure of a table. changing or assigning default table prefixes and structures. Displays MicroStrategy help options Some of these options are also available through toolbar buttons and through right-click menus for quick access. • Table Structure • Calculate Table Row Count • Table Prefix • Table Database Instances • Import Prefix • Options Actions • Read the Warehouse Catalog Help Allows you to update and reflect the changes done to tables in the warehouse. see Data warehouse connection and read operations. This option is enabled when a partition mapping table is selected. Displays the structure of a table selected in the Warehouse Catalog. Allows you to assign or update a database instance for the project. Inc. .

which provides the following options: • • Click OK to apply the change to this column in all the tables it appears. This action results in no changes being applied to any tables or columns. The dialog box displays the columns available in the selected table and the data type of each column. 2 In the Tables being used in the project list. you get a warning message of this change. right-click the table that has changed and select Update Structure. Inc. © 2007 MicroStrategy. page 219). The table structure of the selected table is displayed in the dialog box. Data warehouse and project interaction: Warehouse Catalog 223 . The warning message appears only if you have selected the Display a warning if the columns data types are modified when updating the table structure option in the Warehouse Catalog Options dialog box. Updating table structure Whenever the structure of the warehouse table changes you have to update the table structure in the Warehouse Catalog for the changes to reflect in the MicroStrategy system. You can also click Update Structure to reflect any recent changes done to that table (see Updating table structure. The Warehouse Catalog opens. or rename a column in a table associated with a project. This option is selected by default.Project Design Guide Optimizing and Maintaining Your Project 8 shortcut menu. You can also select Table Structure from the Tools menu. Some examples of these type of changes are when you add. delete. page 223). Click Cancel to undo all data type changes. When the data type of one or more columns is modified. To update the structure of a table 1 Access the Warehouse Catalog for your project (see Accessing the Warehouse Catalog.

. – Repeat the first to steps of this procedure to open the Warehouse Catalog and update the table structure. If any of the object definitions have changed. – Select the fact expression and click Modify. select Update Schema. if you rename a column in a table. this would apply if you rename a column in the table and the column is not being used in any fact expression. The Modify Fact Expression dialog box opens. – Click Save and Close to save the changes and close the Fact Editor. the warehouse structure gets updated completely with the Update Structure command. Edit the fact expression and click OK. you receive a message warning of this change. • 224 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. Inc.8 Optimizing and Maintaining Your Project Project Design Guide If the data type of one or more columns is modified. – Click Update. • If no object definitions have changed. 3 Click Save and Close to close the Warehouse Catalog dialog box. The Fact Editor opens. the table structure is only partially updated with the Update Structure command. – From the Schema menu. For example. Then. For example. you have to manually update the schema objects that depend on the outdated structure. you have to manually update the facts that use this column. Verify the changes from the information dialog box that opens and click OK to apply the change in this column to all the tables in which it appears. The procedure for manually updating the fact is as follows: – Right-click the fact and select Edit. The Schema Update dialog box opens. – From the list of source tables select the source table from which the fact has been created. You are returned to the Fact Editor.

one for the primary database and another for the secondary database. The primary database receives all SQL requests and passes them to the correct database. in your environment you might have a gateway between two databases such as an Oracle database and a DB2 database.Project Design Guide Optimizing and Maintaining Your Project 8 – Click Save and Close to save the changes and close the Warehouse Catalog dialog box. In the Warehouse Catalog. you need to define two database instances. To refresh the table data. The first 100 rows of the table are returned as sample data in the Values dialog box. The default database instance for the project is set to be the primary database. right-click a table in the Warehouse Catalog (see Accessing the Warehouse Catalog. which is used to support database gateways. This way. page 219) and choose Show Sample Data from the shortcut menu. Data warehouse and project interaction: Warehouse Catalog 225 . © 2007 MicroStrategy. Viewing sample data To view sample data from a table. Specifying a secondary database to support database gateways MicroStrategy allows you to specify a secondary database instance for a table. One of them is the primary database and the other is the secondary database. MicroStrategy products know how to generate SQL for each table. For example. Inc. click Reload table values. You can also select Show Sample Data from the Tools menu. you must set the secondary database instance for any tables that are found in the secondary database. From the perspective of MicroStrategy products in this environment.

3 In the Primary Database Instance drop-down list.8 Optimizing and Maintaining Your Project Project Design Guide To specify a secondary database for a table 1 Access the Warehouse Catalog for your project (see Accessing the Warehouse Catalog. row calculation. page 219). select the primary database instance for the table. which allows you to perform the following tasks: • • • Data warehouse connection and read operations Displaying table prefixes. 5 Click OK to accept your changes and return to the Warehouse Catalog. Modifying data warehouse connection and operation defaults You can specify various settings for data warehouse connection and operation defaults using the Warehouse Catalog. Example settings include changing the database instance. row counts. The Warehouse Catalog Options dialog box opens. (in the pane on the right side) and select Table Database Instances. You cannot select the primary database instance as a secondary database instance. automatic mapping. Inc. The settings are available from the Warehouse Catalog. The Warehouse Catalog opens. 6 From the toolbar. 4 Select one or more Secondary Database Instances. page 219 for steps to access the Warehouse Catalog). The Available Database Instances dialog box opens. and so on. changing or assigning default table prefixes and structures. select Save and Close to save your changes and close the Warehouse Catalog. 2 Right-click a table being used in the project. by choosing Options from the Tools menu (see Accessing the Warehouse Catalog. . and name spaces Mapping schema objects and calculating logical sizes for tables 226 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy.

Project Design Guide Optimizing and Maintaining Your Project 8 Data warehouse connection and read operations You can modify the database instance and database login used to connect the data warehouse to a project. – Click New to create a new database instance. You can make these type of modification from the Catalog category. see the online help. which is divided into the following subcategories: • Warehouse Connection: Select the desired database instance to use for the project as well as the custom database login. The Database Instance Wizard opens. If the desired database instance does not appear in the Database Instance box. Clicking Settings allows you to directly edit the catalog SQL statements that are used to retrieve the list of available tables from the Warehouse Catalog and the columns for the selected tables. you can select from the following: – Click Edit to modify the selected database instance. The General tab of the Database Instances dialog box opens. When connected to a Microsoft Access data source. Database Instance: You can select the database instance for the Warehouse Catalog from the drop-down list. Custom Database Login: You can either select the database login or clear the login to use no database login. the Settings option is disabled. Data warehouse and project interaction: Warehouse Catalog 227 . by © 2007 MicroStrategy. The default catalog SQL retrieves a DISTINCT list of tables and columns from all users. You could restrict the information returned. Refer to the MicroStrategy System Administration Guide for more information on either of these dialog boxes. as well as change how the database catalog tables are read. For more information on the database login. Inc. for example. • Read Settings: You can customize the SQL that reads the Warehouse Catalog for every platform except Microsoft Access. or if it does but needs to be modified.

For example. This setting should be cleared when the number of PMTs in the project is so large that reading their structure is causing performance problems when opening the Warehouse Catalog. your project includes a table named Table1 that has 228 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. Display a warning if the column data types are modified when updating the table structure: Select this option if you want to be warned when the data type for a column stored in the project is different from the one read from the data warehouse. By default this option is selected. it may redefine the data type for a column included in the project. see Ignoring table name spaces when migrating tables. do not select this option as it will have a negative effect on performance. The check for the data type change is only performed when updating a table’s structure. Ignore current table name space when reading from the database catalog and update using new table name space: This option allows you to switch between warehouses found in different database name spaces. For more information. Column Merging Options: When you add a new table to your data warehouse. page 232 of this appendix. Inc. If performance is more important than obtaining the row count. Automatically update information for all Partition Mapping tables when reading the database catalog: Select this option to read the latest information for the partition mapping tables (PMTs) currently present in the project. You can also select the following check boxes: Count the number of rows for all tables when reading the database catalog: Select this option if you want to control whether or not the Warehouse Catalog should get the number of rows each table has when loading from the data warehouse. By default this option is selected. . By default this option is selected when you open the Warehouse Catalog for the first time. This option is helpful when you want to identify fact tables and aggregation tables. By default this option is selected.8 Optimizing and Maintaining Your Project Project Design Guide specifying certain conditions and table owners (see Customizing catalog SQL statements. page 233).

When you update the table structure. as defined in Table2. This is because char(4) has a higher precision than char(1) defined in Table1. the column data type for C1 would be changed to char(4). – Use maximum denominator data type: This option updates the column data type to use the data type with the largest precision or scale. – Use most recent data type: This option updates the column data type to use the most recent column definition. In the example above. but it has column C1 set to data type char(4). In the example above. Inc. a warning is displayed and you are asked if you want to use the new data type. the column data type for C1 would be changed to char(4) since Table2 was added after Table1. This example is used to illustrate the options described below. the column data types are modified to maintain a consistent schema in one of three ways. The options below do not handle the merge if the data type has changed to an incompatible data type. Data warehouse and project interaction: Warehouse Catalog 229 . Then a new table named Table2 is added to the project. the data type with the largest precision or scale is used. If the data type has changed to an incompatible data type.Project Design Guide Optimizing and Maintaining Your Project 8 column C1 of data type char(1). as illustrated in the image below. depending on the option you select. If the data type has been changed to a different compatible data type. © 2007 MicroStrategy. a column is changed from data type char to data type integer. For example.

8 Optimizing and Maintaining Your Project Project Design Guide – Do not merge: This option renames the column in the newly added table. Manual: This option sets the Warehouse Catalog tables to be read only when the read catalog action is selected. This option can cause unwanted schema changes and should be used only when necessary. Displaying table prefixes. Inc. by using the View category. Automatically define prefixes for all tables that are added to this project: This setting enables/disables the following options: – Set a prefix based on the warehouse table name space or owner (import prefix): When this option is selected. which allows the columns to have different data types. and name spaces You can choose to show or hide table prefixes. including new tables added to the project. You have the following options: Display table prefixes in the main dialog: Select this option to display all prefixes in table names. From the example above. This category is divided into the following subcategories: • Table Prefixes: You can specify whether table prefixes are displayed in table names and how prefixes are automatically defined for tables that are added to the project. • Read Mode: The Warehouse Catalog can be automatically read upon opening the Warehouse Catalog. Column C1 in Table2 is defined as a separate copy of C1 and uses the char(4) data type. By default this option is selected. the Warehouse Catalog reads the 230 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. and name spaces. row counts. column C1 uses the char(1) data type for Table1. . row counts. or restricted to only be read when a read is manually requested: Automatic: This option sets the Warehouse Catalog tables to be read as soon as the catalog browser is loaded.

this option is selected and the number of rows are shown. and associates it with the table being added. Inc. You can select the default prefix from the Default prefix box drop-down list or create a new table prefix by clicking Modify prefix list. Data warehouse and project interaction: Warehouse Catalog 231 . – Modify prefix list: You can create a new tables prefix or delete an existing prefix by selecting this option. • Table Name Spaces: You can show or hide the name space for each table. This option is only active when the database supports prefixes. see the online help. By default. – Set a default prefix: Select this to add a prefix to tables when they are added to a project. using the following options: © 2007 MicroStrategy.Project Design Guide Optimizing and Maintaining Your Project 8 name space for each table being added. creates a prefix having the same text as the name space. using the check box: Display the name space for each table (if applicable): You can show or hide the owner or table name space where the table is located in the warehouse. • Table Row Counts: You can show or hide the number of rows per table. By default. using the check box: Display the number of rows per table: You can show or hide the values calculated for the number of rows for the tables. Mapping schema objects and calculating logical sizes for tables The Schema category is divided into the following subcategories: • Automatic Mapping: When you add new tables to the Warehouse Catalog. this option is selected and table name spaces are shown. you can determine whether existing schema objects in the project are mapped to these new tables automatically. For more information on modifying the prefix list. The Table Prefixes dialog box opens.

you change the project to point to the primary warehouse. Inc. • Table Logical Sizes: You can select whether the Warehouse Catalog calculates logical sizes for new tables using one of the following options: Calculate the logical table sizes automatically: Logical sizes are automatically calculated for tables you add to the project. the attribute Year with an attribute form mapped to YEAR_ID is included in a project. Do not map schema objects to the new tables: Objects in the schema are not automatically mapped to tables you add to the project. These automatic mapping methods are only applied to existing schema objects when tables are added to the Warehouse Catalog. Then a new table which includes a YEAR_ID column is added to the Warehouse Catalog. With the Map schema objects to new tables automatically option selected. For example. the Year attribute is automatically mapped when the new table is added. Before going into production. Automatically mapping tables to schema objects when adding attributes or facts to a project is controlled by the Attribute Editor and Fact Editor. the Warehouse Catalog automatic mapping settings do not determine whether the attribute and table are automatically mapped.8 Optimizing and Maintaining Your Project Project Design Guide Map schema objects to new tables automatically: Existing objects in the schema automatically map to tables you add to the project. respectively. . 232 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. Ignoring table name spaces when migrating tables It is a common practice to establish a secondary warehouse with less information than the primary warehouse for development and testing. If the table was added to the Warehouse Catalog first and then the attribute was created. Do not calculate table logical sizes: Logical sizes are not calculated for the tables you add to the project.

This information includes catalog tables. You now have two tables dbo. Inc.LU_STORE in the new production warehouse. Customizing catalog SQL statements In all supported warehouse platforms other than Microsoft Access. the Warehouse Catalog recognizes the two tables as the same table and saves the new table name space information. This is because the Warehouse Catalog is looking for a table named dbo. the Warehouse Catalog ignores the current table name space when it reads the catalog information. If you select this option. the Warehouse Catalog defaults to identifying the table by both table name space and table name.LU_STORE. You can find this option in the Warehouse Catalog Options dialog box under the Catalog . and the table is actually stored as admin.LU_STORE. Thus. DB2. and their data types. When you add tables to a project. Data warehouse and project interaction: Warehouse Catalog .Read Settings options subcategory. 233 © 2007 MicroStrategy. For instance. columns. MicroStrategy uses SQL statements to query the relational database management system (RDBMS) catalog tables to obtain warehouse catalog information. you can have LU_STORE in a table name space called dbo and another table LU_STORE in another table name space called admin. select the Ignore current table name space when reading from the database catalog and update using new table name space check box.LU_STORE and admin. The table name space provides an extra piece of information that uniquely identifies the table. which is a way of organizing database tables into different storage spaces. This setting allows you to migrate much more easily between warehouses. If the check box is cleared. This method allows you to repeat the same table name in different table name spaces. and others) support the concept of a table name space. To solve this problem. The Warehouse Catalog interprets the table as already in the project and not found in the new warehouse. This can cause a problem when you migrate from a warehouse that resides in a certain table name space to another warehouse in a different table name space.Project Design Guide Optimizing and Maintaining Your Project 8 Most database management systems (Oracle. the Warehouse Catalog saves information to the appropriate table name space.

Inc. a similar ODBC call is used for the Generic DBMS database type. the first SQL used in a two-pass catalog retrieval.8 Optimizing and Maintaining Your Project Project Design Guide These catalog SQL statements vary from platform to platform and can be customized according to the characteristics of the specific warehouse. so an ODBC call must be used to retrieve information about tables and columns in Access. on the other hand. 234 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. but both can be customized in the Warehouse Catalog Options dialog box. This is the recommended option for interactive warehouse catalog building because no unnecessary catalog information is read from the database. . The name Full Catalog SQL refers to the SQL used to read all the tables and columns in one pass. reads all the tables and columns in one SQL statement. it first reads only the tables from the database. which increases processing speed. In the following sections.or two-pass SQL mode. The MicroStrategy Warehouse Catalog can be configured to read the catalog information in one. One-pass SQL mode. This option is recommended only if the catalog SQL is well customized to limit the amount of data returned by it. The structure of individual tables is read only when the table is selected. By default. The two retrieval options use different catalog SQL. that is. In two-pass SQL mode. but you can choose to use custom catalog SQL for the generic type if you wish. Microsoft Access does not have catalog tables. the name Catalog Table SQL refers to the catalog SQL to retrieve the tables in the warehouse.

These placeholders are: • #LOGIN_NAME#—This placeholder is automatically replaced at run time with the login name used to connect to the database. Inc. A customized catalog SQL can omit the name space if duplicate table names do not present a problem in the warehouse database. Depending on the type of RDBMS. page 235 Structure of Catalog Table SQL. or a combination of both database and owner. a name space gives each table a unique name. page 236 Structure of Full Catalog SQL. Data warehouse and project interaction: Warehouse Catalog 235 . page 237 Default catalog SQL. a table name does not uniquely identify it in a particular database installation. page 236 Modifying catalog SQL. This helps you to avoid confusing tables that share the same table name. In both the Catalog Table SQL and Full Catalog SQL. the owner of the table. you must understand several important concepts and procedures: • • • • • • The table name space.Project Design Guide Optimizing and Maintaining Your Project 8 To customize a catalog SQL. SQL placeholder strings and incomplete catalog SQL The default system catalog SQL can contain certain placeholder strings that can be resolved at run time or must be completed manually by the user. page 235 SQL placeholder strings and incomplete catalog SQL. this name space can be the name of the database. A table name space is a partition of the database installation in which table names are unique. The table name space is optional. You can leave this template in the customized SQL if you want the catalog SQL to yield © 2007 MicroStrategy. page 238 The table name space In a typical RDBMS platform.

The following example is the default Catalog Table SQL for Oracle 8. #?Schema_Name?#. Inc. must be replaced with the name of the schema in which the database tables reside. Duplicates are not allowed. #?Schema_Name?#—This catalog SQL placeholder is an incomplete SQL string that must be completed by the user before it can be executed. Otherwise. Structure of Catalog Table SQL Catalog Table SQL is expected to return two columns. If a name space is not provided. Each row of the SQL result must uniquely identify a table. • #?Database_Name?#. one identifying the name space of the table and the other the name of the table. The column that identifies the table name has the alias TAB_NAME. must be replaced with the name of the database containing the database tables. used with Teradata. The following aliases identify each column returned: • • NAME_SPACE (optional): the table name space TAB_NAME (required): name of the table 236 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy.0: SELECT DISTINCT OWNER NAME_SPACE. used with DB2 AS/400.8 Optimizing and Maintaining Your Project Project Design Guide different results depending on the warehouse login used. TABLE_NAME TAB_NAME FROM ALL_TAB_COLUMNS WHERE OWNER = '#LOGIN_NAME#' Structure of Full Catalog SQL Full Catalog SQL is expected to return between five and seven columns. The string starts with #? and ends with ?#. this template is replaced with the name of the database user who owns the warehouse tables of interest. only the table name column is required. The command #?Database_Name?#. . depending on the RDBMS platform and the customization. The column that identifies the table name space uses the SQL column alias NAME_SPACE.

sysusers WHERE T.0: SELECT U.type in ('U'. C. C.name NAME_SPACE. 2 Modifying catalog SQL You can customize and modify the catalog SQL that is run against your database for each project. 'V') AND T.name COL_NAME. To modify the catalog SQL for your project 1 Access the Warehouse Catalog for your project (see Accessing the Warehouse Catalog.uid = U.length DATA_LEN. © 2007 MicroStrategy.uid ORDER BY 1. T. C. The Warehouse Catalog opens. C. syscolumns C. C.id = C.name TAB_NAME.type DATA_TYPE. page 219).prec DATA_PREC. The following example is the default Full Catalog SQL for Microsoft SQL Server 7. Inc.scale DATA_SCALE FROM sysobjects T.Project Design Guide Optimizing and Maintaining Your Project 8 • • • • • COL_NAME (required): name of the column DATA_TYPE (required): a string or a number that identifies the major data type of the column DATA_LEN (required): a number that describes the length or size of the column data DATA_PREC (optional): a number that describes the precision of the column data DATA_SCALE (optional): a number that describes the scale of a floating point column data Full Catalog SQL must return its rows ordered first by NAME_SPACE. Data warehouse and project interaction: Warehouse Catalog 237 . and then by TAB_NAME. The catalog SQL can be modified in the Warehouse Catalog options for your project. if available.id and T.

The catalog SQL settings are unavailable if your project is connected to a Microsoft Access database. 4 Click the Settings button. . select Options.8 Optimizing and Maintaining Your Project Project Design Guide 2 From the Tools menu. it is recommended you consult the default catalog SQL that MicroStrategy uses to support different database 238 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy.Read Settings options are displayed. The top pane controls the Catalog Table SQL and the bottom pane controls the Full Catalog SQL. The Catalog . the catalog SQL options are displayed as shown below. 3 Expand the Catalog Category. Inc. The Warehouse Catalog Options dialog box opens. and select Read Settings. Default catalog SQL When customizing the catalog SQL that is executed on your database.

• The top pane controls the Catalog Table SQL. click the bottom-most Use Default button. cut and paste the SQL statements in the two panes into any text editor. To generate and view the default Full Catalog SQL for your database platform. Data warehouse and project interaction: Warehouse Catalog 239 . click the upper-most Use Default button. which retrieves column information for the selected tables. This allows you to save any modifications you have made previously to the catalog SQL statements. Inc. Any text in the panes is overwritten with the default catalog SQL statements: • To generate and view the default Catalog Table SQL for your database platform. page 237). You can generate the default catalog SQL in MicroStrategy for the database platform your project connects to. A dialog box for the catalog SQL options is displayed. To generate and view the default catalog SQL 1 Access the catalog SQL options for your project (see Modifying catalog SQL. 2 Generate and view the default catalog SQL for your database platform. Troubleshooting table and column messages You may encounter the following messages while using the Warehouse Catalog: © 2007 MicroStrategy.Project Design Guide Optimizing and Maintaining Your Project 8 platforms. which retrieves a list of available tables in the Warehouse Catalog. Before performing the next step. • • You can use the default catalog SQL statements or compare and combine them with your own customized catalog SQL statements. and then compare them to the default statements you are about to generate. The bottom pane controls the Full Catalog SQL.

This can result in SQL errors when running reports that need data from a “missing” table. 240 Data warehouse and project interaction: Warehouse Catalog © 2007 MicroStrategy. Columns data type changed When the table structure is updated for one or more tables in which the column data types have been changed. If there are any dependencies.8 Optimizing and Maintaining Your Project Project Design Guide • • • Tables missing Columns data type changed Columns missing Tables missing This happens when one or more tables already in the project are removed from the data warehouse. the Warehouse Catalog does not check for any dependencies until you save the changes. . column name. a message is shown which explains that the table structure update cannot proceed because the table was not found in the warehouse. Inc. no changes occur and the original table structure remains intact. In this case. you get a warning message showing the table name. However the definition in the project may be inconsistent with the real physical structure in the warehouse. it displays an error message which gives you the following options: Leave the Table in the project: This leaves everything as is in the project metadata. Two cases can be seen: • When the Warehouse Catalog is starting and retrieving the table information from the data warehouse and it detects that one or more tables already in the project are missing. • When the Warehouse Catalog tries to update the structure of a table that is missing in the warehouse. and you have the option to proceed or cancel the operation. In this case. they are presented to you. Remove the table from the project.

and new data type. To understand aggregate tables. Using summary tables to store data: Aggregate tables Aggregate tables are summary tables that store data at higher levels than it was stored when the data was initially captured and saved. You can click Cancel at any time to undo all data type changes. If this happens. For more information on these topics. Column is mapped to a schema object: If this is the case. © 2007 MicroStrategy.Project Design Guide Optimizing and Maintaining Your Project 8 original data type. MicroStrategy creates aggregates only on fact tables since lookup tables and relationship tables are usually significantly smaller. Warehouse Structure for Your Logical Data Model. The Building Blocks of Business Data: Facts. while retaining the traditional power of ROLAP to directly query the database to answer any questions. and Chapter 5. You are asked to remove the mapping before continuing with the update structure and original table structure is restored. This results in no changes being applied to the tables and columns. see Chapter 2. The Logical Data Model. you should be familiar with fact tables in the context of data modeling and data warehousing. the Warehouse Catalog checks for the following: • • Column is not mapped to any schema object: If this is the case. Aggregate tables provide quicker access to frequently requested information. then no error message is shown. Inc. Columns missing Missing columns are detected when Update Structure is performed. This section describes how and why aggregate tables are used. which are mapped to the missing column and the update structure operation is canceled. Using summary tables to store data: Aggregate tables 241 . then a message is displayed that gives details on objects. Chapter 3.

Aggregate tables are advantageous because they • • • • • Reduce input/output. However.8 Optimizing and Maintaining Your Project Project Design Guide When to use aggregate tables MicroStrategy uses optimized SQL to query the relational database directly to answer users’ questions. RAM. Inc. The disadvantage to this relational OLAP (ROLAP) methodology is that accessing huge fact tables can be potentially time-consuming. CPU. . the MicroStrategy SQL Engine. 242 Using summary tables to store data: Aggregate tables © 2007 MicroStrategy. Users can ask any question that is supported by the data in their warehouse and then analyze the results until they find a precise answer. MOLAP is not scalable for large projects because of the difficulty of maintaining every possible combination of aggregates as the number of attributes and the amount of data increases. can produce results at about the same speed as MOLAP. in combination with aggregate tables and caching. and swapping requirements Eliminate the need to perform dynamic calculations Decrease the number of physical disk reads and the number of records that must be read to satisfy a query Minimize the amount of data that must be aggregated and sorted at run time Move time-intensive calculations with complicated logic or significant computations into a batch routine from dynamic SQL executed at report run time In summary. This combined solution allows questions to be answered on the fly and is also scalable for large databases. MicroStrategy’s solution is the use of aggregate tables to provide quicker access to frequently-accessed data while still retaining the power to answer any user query. Multidimensional OLAP (MOLAP) is sometimes considered by some to be the answer to this problem.

This process is called pre-aggregation.Project Design Guide Optimizing and Maintaining Your Project 8 Aggregation versus pre-aggregation Whenever the display level of data on a report must differ from the level at which the data is initially captured. By default. You can build these pre-aggregated—or aggregate—tables as part of the ETL process. © 2007 MicroStrategy. must occur. sorted. Inc. the rolling up of data. the results of the aggregation are stored in an aggregate table. that is. aggregation occurs dynamically with a SQL statement at report run-time. Using summary tables to store data: Aggregate tables 243 . as in the previous example. For example. The daily values from the fact table are selected. A report requesting month-level data is executed. as shown below. sales data is stored by day in a fact table. Aggregation can also be completed before reports are executed. aggregation. an aggregate table with the sales data rolled up to the month level is useful. and added to produce the monthly totals. If sales data is frequently requested at the month level.

it requires a completely aggregated schema to answer most questions. as shown in the following example. every possible combination of aggregate associations must be generated when the multidimensional cube is built. In these terms. Inc. and calculation of data from many database rows in a large. Degree of aggregation While MOLAP can provide fast performance when it answers a question. . lower-level fact table at run time. it is referred to as a base table. That is. If the daily sales fact table is the lowest-level fact table and contains atomic-level data. This ensures that all possible 244 Using summary tables to store data: Aggregate tables © 2007 MicroStrategy. sorting.8 Optimizing and Maintaining Your Project Project Design Guide Pre-aggregation eliminates the reading. an aggregate table is any fact table whose data is derived by aggregating data from an existing base table.

the degree of aggregation can be as dense or as sparse as is appropriate for your users. A densely aggregated warehouse has a large number of aggregate tables while a sparsely aggregated warehouse has fewer. page 246 The compression ratio—Compression ratio. if the aggregate table is useful in answering frequently-asked queries. Build aggregate tables only if they can benefit users. provides much greater flexibility than MOLAP. That is. Also. page 247 • © 2007 MicroStrategy. In a ROLAP environment. However. since the creation and maintenance of aggregate tables requires additional work by the database administrator. Only the aggregate combinations that you determine are beneficial must be created. its presence provides a response as fast as a MOLAP system can provide. the space in the RDBMS does not need to be consumed and the resources to build that table during the batch process do not need to be used. ROLAP. Sparse aggregation refers to the fact that a given project only requires as many aggregate fact tables as is useful to its users. This scenario becomes very difficult to maintain as the number of attributes and the amount of data increase. Inc. Not every attribute level or hierarchy intersection is suitable for pre-aggregation. do not waste database space for tables that will not be used. page 246 The relationship between the parent and child—Considering any related parent-child relationships. Using summary tables to store data: Aggregate tables 245 .Project Design Guide Optimizing and Maintaining Your Project 8 questions can be answered. and therefore is not very scalable. if a certain aggregate combination is rarely or never used. Consider the following factors when deciding whether to create aggregate tables: • • The frequency of queries at that level—Determining the frequency of queries at a specific level. therefore.

Inc. as well as the database backup routines. Considering any related parent-child relationships When an aggregate table is created. In any hierarchical relationship. the query must use item-level data and summarize the department data dynamically. consider the following hierarchy: A summary of data at the department level seems to be a good candidate for an aggregate table. trace the usage of any aggregate tables to determine how frequently they are used in a day-to-day business environment.8 Optimizing and Maintaining Your Project Project Design Guide Determining the frequency of queries at a specific level Build aggregate tables only if they can be useful to your users. Once your warehouse is in production. However. the department aggregate tables would not be used in this situation. Therefore. For more information on Enterprise Manager. they consume disk space and impose unnecessary burdens on the extraction. based on the key combinations in a relationship table. eliminate it from the warehouse. if users frequently want to exclude inactive items. and loading process. For example. If aggregate tables are never accessed. However. all 246 Using summary tables to store data: Aggregate tables © 2007 MicroStrategy. usefulness is not always easy to quantify. see the MicroStrategy System Administration Guide. the child records are usually summarized into the parent record. MicroStrategy Enterprise Manager allows you to easily track table usage. when the parent-child relationship is altered. translation. If any table is not used. .

Compression ratio The process of data aggregation applies an aggregate function. the relationship is called dynamic. Static relationships When elements rarely or never change relationships. If the tables are large. and the impact on the batch process. and fiscal weeks do not move into different months. and then balance the disadvantages against the advantages of having an aggregate table. For example. or the addition. In these cases. such as sum or average. Also. and complicate the batch process. Inc. maintaining aggregate tables is very easy. geographical realignment. Dynamic relationships When the relationship between parent and child elements change. Using summary tables to store data: Aggregate tables 247 . Aggregate tables that contain dynamic relationships must be recalculated every time a change is made. this process can take time. they are a part of static relationships. Frequent changes can mean aggregate tables are not optimal for this situation. to a set of child records to produce a single parent record.Project Design Guide Optimizing and Maintaining Your Project 8 tables that hold that relationship or data relevant to it must be updated. reclassification. consume resources. or discontinuation of items or services. For example. Whether these relationships are dynamic or static change how they are aggregated into tables. Consider the frequency of the changes. It is not affected by a reorganization within the geography hierarchy. the table size. The average number of child records combined to calculate one parent record is called the © 2007 MicroStrategy. rolling up an entire hierarchy can avoid many problems with relationship changes. For example. a store can decide to reclassify the department to which items belong. a table contains one value for the sum of all stores. time hierarchies are seldom dynamic—days do not migrate into different weeks. These changes often occur because of organizational restructuring.

the resource demands placed on the database server by dynamic aggregations decrease and therefore so does the effectiveness of pre-aggregation. the compression ratio suggests that an aggregate table can provide more efficient queries. Creating aggregate tables You can integrate aggregate tables in your project using the Warehouse Catalog in MicroStrategy Desktop. since it represents the decrease in records that must be read to respond to a query at that level. for smaller base tables. One measure of effectiveness of an aggregate table can be estimated from this number. .8 Optimizing and Maintaining Your Project Project Design Guide compression ratio. pre-aggregating data is effective only if the compression ratio is significant. refer to Cardinalities and ratios. Also. In contrast. Recall that some of the reasons to build aggregate tables include the reduction of disk I/O and the number of records that must be dynamically sorted and aggregated. To determine when pre-aggregation is worthwhile for your system. For more information on ratios. if the compression ratio is 3:2. if the compression ratio is 4:1. as outlined in the following procedure. you must balance the importance of speed of query response time and the availability of disk space and resources to maintain the schema. For example. Inc. page 35. Therefore. the aggregate table requires 2/3 of the base table’s storage space but yields only a 1/3 reduction in the number of records. When the number of elements differs significantly between two attributes in the same hierarchy. the aggregate table reduces the number of records by 3/4 and uses only 1/4 of the storage space. 248 Using summary tables to store data: Aggregate tables © 2007 MicroStrategy.

For steps to add tables using the Warehouse Catalog. Because the attribute levels are lower in the base fact © 2007 MicroStrategy. Using summary tables to store data: Aggregate tables 249 . the Analytical Engine chooses the smallest of all tables. Inc. When you run a report. when either could provide the answer to a query? The answer is logical table size. The other tables. Suppose the base fact table contains millions of rows of transaction-level detail. have only higher-level or summary data. Because Desktop uses the conceptual or logical attribute definitions when assigning sizes. see Adding and removing tables for a project. If your aggregate table structure is consistent with your base fact table structure. that contains enough data to answer the query. based on logical table size. 2 Use the new table in the desired fact expressions and attribute form expressions. Architect is aggregate-aware. add the table to the project. These size assignments are stored in the metadata and are calculated based on the table columns and their corresponding attributes. In other words.Project Design Guide Optimizing and Maintaining Your Project 8 To use an aggregate table in an existing project 1 Using the Warehouse Catalog. however. page 220. The size of tables in a project: Logical table size MicroStrategy Desktop assigns a size to every table in the project when you first add them to the project. this measurement is known as the logical table size. Architect automatically adds it to the definitions of your existing attributes and facts. Changing the logical table size The initial logical table size is based on the number of attribute columns and the various levels at which they exist in their respective hierarchies. How does Architect know to use the aggregate table rather than the base fact table.

such as month or department. Server versus application partitioning Partitioning can be managed by either the database server or the MicroStrategy application. see the MicroStrategy Desktop online help. Logically. Inc. Logical Tables. this division is based on a definable data level. Time is the most common category for partitioning databases. the table as a whole is assigned a higher value for the logical table size than are the summary tables with higher-level attributes. Dividing tables to increase performance: Partition mapping Partition mapping involves the division of large logical tables into smaller physical tables. Therefore. Of course. 250 Dividing tables to increase performance: Partition mapping © 2007 MicroStrategy. partitions improve the speed and efficiency of database queries.8 Optimizing and Maintaining Your Project Project Design Guide table. By distributing usage across multiple tables. The terms “application” and “server” refer to what manages the partitioned tables. this is not always true in a real warehouse. Partitioning by time limits growth of the database tables and increases stability. Logical tables are discussed in detail in Appendix C. For steps to use the Logical Table Editor. . not where the tables are split. tables are partitioned at the database level. Partitions improve query performance by minimizing the number of tables and records within a table that must be read to satisfy queries issued against the warehouse. Either way. the Logical Table Editor allows you to alter the logical table sizes based on their true relative sizes. a table with a higher-level attribute should be smaller in size.

In contrast. The original fact table is not physically broken into smaller tables. manages the partitioned tables in RDBMS server-level partitioning. rather than the RDBMS server. the partitioning is transparent to MicroStrategy. page 254—uses a specialized warehouse table to determine which table to access Metadata partition mapping Metadata partition mapping is the mapping of partitions where the mapping of partitions is performed and maintained in the project metadata by the application. rather than MicroStrategy. Application-level partitioning In application-level partitioning the application. in this case. MicroStrategy supports two types of partitioning: • • Metadata partition mapping. in application-level partitioning the relational database is unaware of the partitioned tables. 251 © 2007 MicroStrategy. MicroStrategy. A partition base table (PBT) is a warehouse table that contains one part of a larger set of data. This approach makes it easier for you to specify a flexible partitioning schema. the database server logically partitions the table according to parameters specified by the database administrator. manages the partition tables. Refer to your database documentation for details on server partitioning for your particular platform. such as time or geography. Instead. page 251—stores the mapping information in the project metadata Warehouse partition mapping. You do not need to take any action in MicroStrategy to support the partitioning. Since only the logical table is displayed to the end user. Inc. MicroStrategy manages the mapping between the logical table and the physical tables. Dividing tables to increase performance: Partition mapping . Partition tables are usually divided along logical lines.Project Design Guide Optimizing and Maintaining Your Project 8 Server-level partitioning The database server.

8

Optimizing and Maintaining Your Project

Project Design Guide

In metadata partition mapping, you specify one or more partitioning attributes in the Metadata Partition Mapping Editor. Next you define what attribute elements within those attributes should point to which PBT. You create all of the rules for choosing the appropriate PBT here and the rules are stored in the MicroStrategy metadata. For steps to create a metadata partition mapping, refer to the MicroStrategy Desktop online help.

Homogenous and heterogeneous partitions
Metadata partitions can be homogenous or heterogeneous. With heterogeneous partitioning, the PBTs can have different amounts of data stored in them at different levels. For example, one table can contain six months of sales data, while another stores an entire year. The PBT level, or key, refers to how the data is stored. For example, sales data for the current year can be stored at the daily level, while historical sales data is saved by month only. Heterogeneous partitions can therefore require additional long-term maintenance and organization because the data contained in them is stored at various levels throughout the partition. MicroStrategy stores one PBT level for each partition. If all the PBTs within a partition are not stored at the same level, the highest PBT level is used as the PBT level of the partition. For instance, if all the sales data in the previous example is stored in one partition, you cannot access current sales at the day level. This is because the PBT level for the partition is month, which is higher than day. If you save current data in a partition at the daily level and the historical data in another partition at the month level, you are able to fully access the data. In contrast, homogenous partitions must have the same amount of data stored at the same PBT level. The logical structure of the PBTs must be the same, that is, they must have the same facts and attributes defined. To continue with the previous examples, each table must store one year of data at the month level. Homogeneous partitions work well for frequently-accessed data such as information about the previous year.

252 Dividing tables to increase performance: Partition mapping

© 2007 MicroStrategy, Inc.

Project Design Guide

Optimizing and Maintaining Your Project

8

When you define the particular PBT to which an attribute is linked in MicroStrategy, you do not need to specify whether or not the PBT is homogeneous or heterogeneous. MicroStrategy makes the distinction automatically depending, in part, on how the data is stored in the PBT.

Data slices
After PBTs are created, you define a data slice. The data slice acts as a filter that describes what portions of data are placed in the partition table. Based on this data slice, the MicroStrategy engine knows which table to get data from when generating the SQL. A data slice holds the parameters that a partition is based upon, for example, Month=January. Instead of retrieving data for all months, the server knows to access a particular table that contains the data for January only. By creating a data slice with the partition, you can retrieve specific data quickly without time-consuming joins and searches. It is important to create a reasonable and valid data slice because MicroStrategy cannot verify its accuracy or relevance. The data slice must make sense for the data. A poorly crafted data slice can lead to errors from generating incorrect SQL and retrieving the wrong data. Data slicing displays and can be modified only for the metadata partitioning. Each partition mapping table must include at least one data slice. In a heterogeneous mapping, data slices can exist at different levels and can be composed of different keys.

Attribute qualifications
To create data slices, you use attribute qualifications. Attribute qualifications are types of filters that are applied to attribute forms. These qualifications allow you to limit the type and amount of data that is returned for a report. For example, if you create a report that contains the attribute Country but you want to return only the data for France, you can create a qualification on the attribute Country and select France as the element that appears on the report.

© 2007 MicroStrategy, Inc.

Dividing tables to increase performance: Partition mapping

253

8

Optimizing and Maintaining Your Project

Project Design Guide

For steps to create a data slice, refer to the MicroStrategy Desktop online help.

Warehouse partition mapping
Warehouse partition mapping is the mapping of partitions, where the mapping is performed by and maintained in the data warehouse. You can define a warehouse partition by using the MicroStrategy Warehouse Catalog to add a table with a special structure. This table contains the map for the partition, and is stored in the warehouse. Warehouse partitions divide tables physically along any number of attributes, although this is not visible to the user. Warehouse partitions must be homogenous, unlike metadata partitions, so that the same amount of data is stored at the same PBT level and the same facts and attributes are defined. Homogenous partitioning divides data of equal levels, like January and February. A sample fact table and warehouse partitioning table are shown below for months. Note how the data exists at equal levels, for example, different months of the same year.

The original fact table, which contains all of the data, is not brought into the project. Rather, the database administrator creates multiple smaller physical tables in the data warehouse. Each table contains a subset of the data in the original fact table. The database administrator is responsible for keeping the partitions consistent and up-to-date. He or

254 Dividing tables to increase performance: Partition mapping

© 2007 MicroStrategy, Inc.

Project Design Guide

Optimizing and Maintaining Your Project

8

she must also create and maintain a partition mapping table (PMT), which is used to identify and keep track of the partitioned base tables as part of a logical whole. After the PMT is created, when you run a report in Desktop or Web that requires information from one of the PBTs, the Query Engine first runs a pre-query to the PMT to determine which PBT to access to bring the data back for the report. The pre-query requests the PBT names associated with the attribute IDs from the filtering criteria. When it finds the name of the PBT, it calls the SQL Engine to write the appropriate SQL for the warehouse. When using warehouse partition mapping, it is usually not necessary to bring in the individual PBT tables into the project. Doing so can cause errors if such tables are mistakenly mapped directly to schema objects. You should only include the PMT table in the project. With this strategy you can map all related schema objects to the PMT, which then accesses the correct PBT in the warehouse. Note the following: • • There are no data slices in a warehouse partition. MicroStrategy supports warehouse partitions on both upgraded and newly created projects. These are added using the Warehouse Catalog Browser. For steps to add warehouse partitions, refer to the MicroStrategy Desktop online help.

Metadata versus warehouse partition mapping
Metadata partition mapping does not require any additional tables in the warehouse. Metadata partition mapping is generally recommended over warehouse partition mapping in MicroStrategy. However, if you already have warehouse partition tables set up and are migrating to a newer version of MicroStrategy, you can continue to use the warehouse partitions. If you are creating partitions for the first time, however, it is recommended you implement metadata partition mapping.

© 2007 MicroStrategy, Inc.

Dividing tables to increase performance: Partition mapping

255

8

Optimizing and Maintaining Your Project

Project Design Guide

Metadata partition mapping is recommended because you create the rules in MicroStrategy that the Query Engine uses to generate the SQL to run reports. Because you create the partitions directly in the metadata, it is easier to maintain. Metadata partition mapping also allows both heterogeneous and homogenous partitions, unlike warehouse partition mapping. With heterogeneous partitions, the PBTs can have different amounts of data stored in them at different levels. Only homogenous partitions can be used in warehouse partition mapping. For steps to map partitions, refer to the MicroStrategy Desktop online help.

256 Dividing tables to increase performance: Partition mapping

© 2007 MicroStrategy, Inc.

9
9.

CREATING TRANSFORMATIONS TO DEFINE TIME-BASED AND OTHER COMPARISONS

Introduction
Suppose you want to compare how much revenue your company grew last year to how much it grew this year. This type of analysis, called a TY/LY comparison (This Year versus Last Year), is a commonly used form of time-series analysis and is relevant to many different industries, including retail, banking, and telecommunications. Transformations—schema objects you can create using attributes in your project—are one of the many MicroStrategy techniques used to perform time-series analysis. To calculate a variance or a growth percentage such as last year’s revenue versus this year’s 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. This chapter discusses the different types of transformations and how to create them. It is assumed that you have some understanding of what metrics are, as transformation metrics
© 2007 MicroStrategy, Inc.

257

9

Creating Transformations to Define Time-Based and Other Comparisons

Project Design Guide

are discussed in this chapter. For information on metrics and using transformations in metrics and reports, see the Metrics chapter of the MicroStrategy Advanced Reporting Guide.

Creating transformations
A transformation is a schema object that typically maps a specified time period to another time period, applying an offset value, such as current month minus one month. Usually defined by a project designer, transformations are used in the definition of a metric to alter the behavior of that metric. Such a metric is referred to as a transformation metric. For example, time-related transformations are commonly used in metrics to compare values at different times, such as this year versus last year or current date versus month-to-date. Any transformation can be included as part of the definition of a metric and multiple transformations can be applied to the same metric. Transformation metrics are beyond the scope of this guide; for information about transformation metrics, refer to the MicroStrategy Advanced Reporting Guide. Recall the example used in the introduction, the TY/LY comparison. To calculate this year’s revenue, you can use the Revenue metric in conjunction with a filter for this year. Similarly, to calculate last year's revenue, you can use the Revenue metric in conjunction with a filter for last year. However, a more flexible alternative is to use a previously created Last Year transformation in the definition of a new metric, last year’s revenue. With a single filter, on 2003 for example, the two metrics Revenue and Last Year Revenue give you results for 2003 and 2002, respectively. Since a transformation represents a rule, it can describe the effect of that rule for different levels. For instance, the Last Year transformation intuitively describes how a specific year relates to the year before. It can in addition express how each month of a year corresponds to a month of the prior year. In the same way, the transformation can describe how each day of a year maps to a day of the year before. This information defines the transformation and abstracts all cases into a

258 Creating transformations

© 2007 MicroStrategy, Inc.

Project Design Guide

Creating Transformations to Define Time-Based and Other Comparisons

9

generic concept. That is, you can use a single metric with a last year transformation regardless of the time attribute contained on the report. While transformations are most often used for discovering and analyzing time-based trends in your data, not all transformations have to be time-based. An example of a non-time-based transformation is This Catalog/Last Catalog, which might use Catalog_ID-1 to perform the transformation.

Expression-based versus table-based transformations
The definition of the association between an original value and a transformed one can be represented in an expression that uses columns of the warehouse, constants, arithmetic operators, and mathematical functions. This is known as an expression-based transformation. However, it is sometimes desirable to precalculate these values and store them in a table designed for the transformation. This method is sometimes referred to as a table-based transformation. The advantage of a table-based transformation is the possible use of indexing to speed query times. Another advantage is that table-based transformations provide additional flexibility beyond what formula expressions can produce. The drawback of this kind of transformation is that it requires the creation and management of an additional table in the warehouse. However, once the table is created, it usually significantly decreases the query time. Returning to the TY/LY example, you have the option of using a simple formula such as Year_ID - 1 in the definition of the transformation or precalculating the data and storing it in a column in a table. A table-based transformation is required when a many-to-many transformation is performed. An example is a year-to-date calculation. A significant advantage to the dynamic calculation of an expression-based transformation is that the database administrator does not have to create and maintain a transformation table. The drawback is that the system must perform the calculation every time.

© 2007 MicroStrategy, Inc.

Creating transformations

259

9

Creating Transformations to Define Time-Based and Other Comparisons

Project Design Guide

A single transformation can use a combination of table-based and expression-based transformations. For example, you can create a last year transformation based on Year and Month. The ID of the Year attribute is in the format YYYY, so the transformation can use the expression Year_ID - 1. The ID for the Month attribute is in the format ‘MonthName,’ so you cannot easily use a mathematical expression. You must use a table instead. The following sections walk you through creating both a table-based transformation and an expression-based one.

Building a table-based transformation
The following example shows how to create a last year transformation based on a lookup table in MicroStrategy Tutorial, which pairs each year with the previous year. This transformation is used in the report displayed below, which compares revenue for this year and last year.

Creating the transformation metric and the report are discussed in the Transformation metrics section in the Metrics chapter of the MicroStrategy Advanced Reporting Guide.

260 Creating transformations

© 2007 MicroStrategy, Inc.

The Year . then double-click Year. The Transformation Editor opens with the Select a Member Attribute dialog box displayed. Name the transformation Last Year (Table). Inc. Notice that this table contains a previous year column. A report designer can now use the transformation in a revenue metric to calculate last year’s revenue. 2 From the File menu. The Year_ID is in the format YYYY. Building an expression-based transformation This example shows how to create a last year transformation using an expression rather than a table. 6 Click OK. 2004. so the previous year is simply Year_ID minus one. The table's columns appear in the Available columns list.Project Design Guide Creating Transformations to Define Time-Based and Other Comparisons 9 To create a last year transformation based on a table 1 Log in to the project source that contains your project in MicroStrategy Desktop and expand your project. 5 Double-click the PREV_YEAR_ID column to place it in the expression box. which maps this year to last year. then create a report using that transformation metric to obtain last year’s revenue. You have now created the transformation. 3 Double-click Time to open the folder. 4 Select the LU_Year table from the Table drop-down list. point to New. © 2007 MicroStrategy. and select Transformation.Define a new member attribute expression dialog box opens. For example. one subtracted from the year 2005 results in the previous year. 7 Click Save and Close on the toolbar. Creating transformations 261 .

. 3 Select the LU_Year table from the Table drop-down list. Again.9 Creating Transformations to Define Time-Based and Other Comparisons Project Design Guide This transformation is added to the report shown in the table-based transformation example above. and select Transformation. The resulting report is displayed below. 5 Type -1 in the expression box. point to New. then double-click Year. The Year . from the File menu. Inc. creating the transformation metric and the report are discussed in the Transformation metrics section in the Metrics chapter of the MicroStrategy Advanced Reporting Guide. 262 Creating transformations © 2007 MicroStrategy. To create a last year transformation based on an expression 1 In MicroStrategy Desktop. The transformation will subtract 1 from the Year ID to calculate last year’s ID. 4 Double-click the YEAR_ID column to place it in the expression box. 2 Double-click Time to open the folder.Define a new member attribute expression dialog box opens. The Transformation Editor opens with the Select a Member Attribute dialog box displayed. The table's columns appear in the Available columns list.

The message “Valid expression” appears with a green check mark. A report designer can now use the transformation in a revenue metric to calculate last year’s revenue. generally the lookup table corresponding to the attribute being transformed. that is. the member attributes are Year. Inc. the member tables are LU_YEAR. for the member attributes Year. 8 Click Save and Close on the toolbar. then add it to the report created in the previous example. and Day. LU_MONTH. LU_QUARTER. © 2007 MicroStrategy. each member expression is based on a specific table. Quarter. You have now created the last year transformation. in the Last Year transformation. Quarter. For a table-based transformation. Month. • Member tables: These tables store the data for the member attributes. For an expression-based transformation. and LU_DAY. Transformation components All transformations have the following components: • Member attributes: This component contains the attributes to which the transformation applies. For example. this is the transformation table defining the relationship. 7 Click OK. For example. Month. in the Last Year transformation in the MicroStrategy Tutorial. Transformation components 263 . • Member expressions: Each member attribute has a corresponding expression. and Day. the different levels to which the rule applies. respectively.Project Design Guide Creating Transformations to Define Time-Based and Other Comparisons 9 6 Click Validate. Name the transformation Last Year (Expression).

consider YearToDate defined as a many-to-many transformation and Revenue (YTD) as a transformation metric. the member expressions are LY_DAY_DATE.” One day or month this year maps exactly to one day or month from last year. . you cannot subtract one and receive December 1999 as the result. this is simply a column from a specific warehouse table specifically populated with data supporting the transformation. LY_MONTH_ID. For example. arithmetic operators. this approach provides considerable flexibility in the transformation definition. For instance. For a table-based transformation. The mapping can be one of the following: One-to-one: A typical one-to-one relationship is “last year to this year. For example. many other dates are included in the year-to-date calculation. However. and columns from the warehouse. These are all columns from the lookup tables set in the Member tables field. this is a mathematical expression. Many-to-many transformations can lead to double-counting scenarios. LY_QUARTER_ID. mathematical functions. many cases can exist where the data is not conducive to such calculation. It is particularly effective when no straightforward formula can express the rule. Inc. Many-to-many: A typical many-to-many relationship is year-to-date. in the Last Year transformation. Suppose this metric is used on 264 Transformation components © 2007 MicroStrategy. typically the attribute ID column. if you store Month as 200001 (January 2000). For one date. in the case of a many-to-many transformation.9 Creating Transformations to Define Time-Based and Other Comparisons Project Design Guide For an expression-based transformation. this expression uses constants. a separate table is required. For example. Since the data defines the rule. you can create a Last Year transformation using Year_ID-1 as the expression. • Mapping type: This component determines how the transformation is created based on the nature of the data. The rule is then not encapsulated in an expression but directly in the data of the column. In fact. and PREV_YEAR_ID. In the most generic case.

a transformation metric displays the current attribute with transformed data. the joint child attribute Promotion is added to the previous report. For more information about joint child attributes. The joint child attribute cannot be transformed because not all of its joint children—Quarter and Item—are time-related. a conflict arises. In a report. that is. Inc. as shown below: When a joint child attribute—an attribute that exists at the intersection of other indirectly related attributes—is added. the Revenue (YTD) metric will double count. a range of dates is specified in the filter. see Joint child relationships. the values for the transformation. which is the member attribute on the template. Transformation metrics and joint child attributes Review the discussion of joint child attributes and relationships in Joint child relationships. page 171. a report contains Quarter and the transformation metric Last Year’s Revenue. For example. For example.Project Design Guide Creating Transformations to Define Time-Based and Other Comparisons 9 a report that does not include the Day attribute. the © 2007 MicroStrategy. with the previous year’s revenue. In this instance. The report displays the quarter. Each quarter is displayed. Transformation metrics and joint child attributes 265 . In the report. page 171 before proceeding in this section.

since the Valentine’s Day promotion was not run in 2002. but not attributes such as Promotion. remember that only the metric values are transformed. and the revenue data from the date-promotion combination. A sample report is shown below: The displayed attributes should still be current. the Valentine’s Day-Q1 2002 combination cannot be displayed on the report. While you may want to see it listed for 2002.9 Creating Transformations to Define Time-Based and Other Comparisons Project Design Guide promotion associated with a given quarter. again. not the attributes. However. minus one year. Notice that the Valentine’s Day promotion existed in 2003 but not in 2002. This is the case because. That is. displaying transformed data. since the joint child attribute Promotion essentially exists in both the time dimension and a non-time dimension. the Valentine’s Day promotion is not listed for Q1 2002 despite the existence of the last year transformation. transformations “transform” metric values such as Revenue. In summary. it is not intuitive how the transformation should be performed. . 266 Transformation metrics and joint child attributes © 2007 MicroStrategy. Inc.

and a set of demonstration applications designed to illustrate the features of the MicroStrategy platform. MICROSTRATEGY TUTORIAL Introduction This appendix provides information on the MicroStrategy Tutorial. the project is the environment in which all related reporting is done. © 2007 MicroStrategy. metrics. filters. and functions.A A. Inc. What is the MicroStrategy Tutorial? 267 . and user community. Conceptually. which includes a metadata and warehouse. What is the MicroStrategy Tutorial? The MicroStrategy Tutorial is a MicroStrategy project. You create projects that users access to run reports. metadata repository. A typical project contains reports. including the data model and physical warehouse schema. A project is the highest-level of intersection of a data warehouse.

Company Executives. © 2007 MicroStrategy. Products. • • • MicroStrategy Tutorial reporting areas MicroStrategy Tutorial reports are grouped into four folders: • Business Roles: This folder contains subfolders that reflect different types of business intelligence users within an organization. Inventory. They are a sampling of the types of reporting documents that can be built using MicroStrategy Report Services. Each hierarchy can be viewed graphically through MicroStrategy Desktop and MicroStrategy Web. Employee. books. 268 What is the MicroStrategy Tutorial? . The key features include the following: • Hierarchies—Customer. Brand Managers. such as scorecards and dashboards. Regional Sales Managers. the Billing Managers folder contains an Invoice report and a customer-level transaction detail report. Options to create reports from MicroStrategy Desktop and MicroStrategy Web focusing on a particular analysis area. District Sales Managers. Promotions. Numerous customers and purchased items. Inventory and Supply Chain Analysis. Each subfolder contains reports that would be of interest to the type of business user for which the subfolder is named. managed metrics reports. Inc. Enterprise Performance Management. and business reports. Human Resources Analysis. and Suppliers. and Supplier Analysis. production and operational reports. Time. such as Customer.A MicroStrategy Tutorial Project Design Guide The theme of the MicroStrategy Tutorial project is a retail store for the time 2003 to 2006 that sells electronics. Sales and Profitability Analysis. For instance. Category. Reporting areas: Customer Analysis. and Time. Geography. Products. and the Brand Managers subfolder contains a report called Brand Performance by Region. Operations Managers. The Supplier folder contains a Supplier Sales report. or Call Center. Category Managers. movies and music. including Billing Managers. • Enterprise Reporting Documents: This folder contains various examples of different types of standard enterprise reporting documents. invoices and statements.

Project Design Guide

MicroStrategy Tutorial

A

MicroStrategy Platform Capabilities: This folder contains examples of many of the sophisticated capabilities within the MicroStrategy platform. Evaluators of the software, as well as customers, can use the examples to get a better feel for many of the platform’s capabilities. Customers can use the examples to guide their own development. The subfolders under these folders are named according to the capabilities that their reports exemplify. For instance, the Graph Styles folder contains examples of most of the graph types that can be created in MicroStrategy, and the Analytics and Data Mining folder contains examples of Linear Regression models built within MicroStrategy.

Subject Areas: This folder contains reports that are categorized further by topic. Topics covered include Customer Analysis, Enterprise Performance Management, Human Resource Analysis, Inventory and Supply Chain Analysis, Sales and Profitability Analysis, and Supplier Analysis. Customer Analysis: Reports analyzing the customer base, studying areas such as Customer Income, Customer Counts, Revenue per Customer, and Revenue Growth. Enterprise Performance Management: Reports containing information on revenue amounts, trends and forecasts, profits, profit margins, and profit forecasts. These reports make it easy for an executive at any level of the company to understand how the company is performing as a whole or at the region, category, and subcategory levels. Human Resource Analysis: Reports containing information on employees, including headcount, birthdays, length of employment, and the top five employees by revenue. These reports are based on employees, time, geography, and sales. The Human Resources Analysis reports provide insight into human capital so that managers can boost the efficiency and effectiveness of their employees. Human Resource Representatives can highlight under-performing employees and misallocated headcount. Managers at all levels can focus on the

© 2007 MicroStrategy, Inc.

What is the MicroStrategy Tutorial?

269

A

MicroStrategy Tutorial

Project Design Guide

performance of their employees, drill down to an individual employee detail level, view trends, and extract intelligence not otherwise evident. Inventory and Supply Chain Analysis: Reports containing information based on supplier, product, cost, revenue and profit, such as Inventory and Unit Sales, or Inventory Received from Suppliers by Quarter. The Inventory reports track inventory information within the company and through to suppliers. Essentially, these reports show how many units of an item are on hand, how many are expected from a particular supplier, and how many units have been sold. Inventory reports are used to ensure that the supply chain is as efficient as possible. Using these reports, employees can analyze trends and details, quickly adjust inventory and distribution, and understand underlying supply chain costs and inefficiencies. Sales and Profitability Analysis: Reports analyzing revenue and profit from multiple perspectives. Examples include Sales by Region, Revenue over Time, and Brand Performance by Region. The Product Sales reports allow managers and analysts to monitor and analyze sales trends, track corporate revenue goals, compare store-to-store performance, and respond more quickly and accurately to feedback from the marketplace. In turn, executives can analyze sales trends and details, quickly adjust pricing and promotions, identify product affinities and key profit centers, and understand costs and revenue trends. Supplier Analysis: Reports containing supplier, sales, profit, and revenue information, such as Brand Sales by Supplier, Supplier Sell-Through Percentage, and Units Sold and Profit by Supplier. The Supplier reports allow managers and analysts to monitor and analyze vendor performance so that they can quickly identify performance problems. These reports track brands and items sold that came from a particular vendor. They also correlate profit and revenue information with particular suppliers so that relationships with key vendors can be strengthened.

270 What is the MicroStrategy Tutorial?

© 2007 MicroStrategy, Inc.

Project Design Guide

MicroStrategy Tutorial

A

These reports and documents are located in the Public Objects/Reports folder of the MicroStrategy Tutorial project. Once the areas of analysis are determined, a data model is created.

MicroStrategy Tutorial data model
A logical data model graphically depicts the flow and structure of data in a business environment. It provides a way of organizing facts so that they can be analyzed from different business perspectives. For example, a simple logical data model for a retail company can organize all necessary facts by store, product, and time, which are the three common business perspectives typically associated with retail business. For detailed information about data modeling, see Chapter 2, The Logical Data Model. For MicroStrategy Tutorial, the areas of analysis discussed earlier, Customer Analysis, Human Resources Analysis, and so on, are organized into the following hierarchical groupings: • • • • • Geography Products Customers Time Promotions

These MicroStrategy Tutorial hierarchies are displayed on the following pages for your reference.

© 2007 MicroStrategy, Inc.

MicroStrategy Tutorial data model

271

A

MicroStrategy Tutorial

Project Design Guide

Data modeling notations
The following notations are used in graphical depictions of hierarchies.
Symbol Indicates entry point Definition An entry point is a shortcut to an attribute element in the Data Explorer. Creating an entry point grants you faster access to the attribute without having to browse through multiple attributes to reach different levels of the hierarchy.

attribute

A data level defined by the system architect and associated with one or more columns in the data warehouse lookup table. Attributes include data classifications like Region, Order, Customer, Age, Item, City, and Year. They provide a handle for aggregating and filtering at a given level. An attribute relationship in which every element of a parent attribute relates to multiple elements of a child attribute, while every element of the child attribute relates to only one element of the parent. The one-to-many attribute relationship is the most common in data models.

one-to-many relationship

Geography hierarchy
The Geography hierarchy contains attributes, such as Country and Region, as well as Distribution Center, Call Center, and employee-specific attributes. It is easy to understand why Country and Region are in the Geography hierarchy, but what about Distribution Center, Call Center, and the employee-related attributes? The data used in MicroStrategy Tutorial is based upon a fictitious company that sells electronics, movies, music, and books. The company does not have physical stores, but instead does its business from catalog and Web sales. Customers review the products in a printed or online catalog and call in their order over the phone. The order is then processed by an employee located at one of the call centers. The order is then fulfilled by a distribution center that holds the correct item and sends it through one of the shippers.

272 MicroStrategy Tutorial data model

© 2007 MicroStrategy, Inc.

Project Design Guide

MicroStrategy Tutorial

A

The Geography hierarchy contains the following attributes.
Attribute Country Region Call Center Distribution Center Manager Employee Experience Hire Date Salary Employee Age Employee Birth Date Employee Description Countries where the company does or hopes to do business in the future. Also refers to countries where employees work. Each country is split into regions. Where product phone-in orders are taken. Each call center is located in a different city. The location where product orders are sent out to customers. Currently, each is located in the same city as the call center it services. Person responsible for a specific call center. The number of years an employee has worked for the organization. The date on which a particular employee was hired. The amount of money an employee makes per year. The age of each employee. The date each employee was born. The lowest level in the Geography hierarchy, representing the individual responsible for each order placed. Example USA, Spain, France. Central, Northeast, Southwest. Atlanta, Boston, Charleston. Miami, New Orleans, Fargo. Peter Rose, Alice Cooper. 3, 5, 6. 2/16/97, 3/15/99. 24,000, 35,000. 29, 36, 52. 5/6/66, 1/1/77. Jennifer Lee, Laura Kelly.

© 2007 MicroStrategy, Inc.

MicroStrategy Tutorial data model

273

A

MicroStrategy Tutorial

Project Design Guide

Refer to the following image to see how all these attributes are organized into the MicroStrategy Tutorial Geography hierarchy.

Products hierarchy
The products hierarchy contains attributes, such as Category, Brand, Catalog, and Supplier. The Products hierarchy contains the following attributes.
Attribute Category Subcategory Description Products are organized into categories at the highest level. Used to further differentiate a subset of products within a category. Example Electronics, Music. Business, Cameras, Drama.

274 MicroStrategy Tutorial data model

© 2007 MicroStrategy, Inc.

Project Design Guide

MicroStrategy Tutorial

A

Attribute Warranty Brand Catalog Supplier Discontinued Code Item

Description The time period in months during which a manufacturer repairs a broken item (specific to Narrowcast Server). The manufacturer or artist for a particular product. The medium used to sell products. The distributor for a set of brands. 0 = discontinued product, 1 = non-discontinued product. The individual product sold.

Example 3, 5. Ayn Rand, 3Com, Sony. Spring 2002, Fall 2003. McGraw Hill, Disney Studios. 0, 1 The Great Gatsby, Sony Discman.

Refer to the following image to see how all these attributes are organized into the MicroStrategy Tutorial Products hierarchy.

© 2007 MicroStrategy, Inc.

MicroStrategy Tutorial data model

275

A

MicroStrategy Tutorial

Project Design Guide

Customers hierarchy
The Customers hierarchy contains customer demographic and purchase information, such as Customer Age, Income Bracket, Payment Method, and Ship Date. The Customers hierarchy contains the following attributes.
Attribute Customer Country Customer Region Customer State Customer City Customer Age Customer Birth Date Income Bracket Zip Code Customer Shipper Rush Order Description The highest level of differentiation for where Customers live The highest level of differentiation for where customers live. Each Customer Region is divided into multiple States. Each Customer State is broken down into cities. The age of a particular customer at a current point in time. The date on which the Customer was born. The salary range reported by the customer. The lowest level of differentiation for where customers live. The name of the individual customer. The vendor used to send products to the customer. (Currently not implemented in the project.) Indicates whether a customer chose to expedite delivery of an order. The way a customer pays for an order. The date on which an order is shipped from the distribution center. The tracking number associated with a particular group of items purchased. Amex, Check. 9/15/02, 3/26/03. 167, 2635. Example USA, Spain, France Northeast, South, France. Maine, North Dakota. Albany, Chicago, Memphis. 26, 38, 59. 8/4/50, 4/30/72. $31,000 - 40,000, $61,000 70,000. 07026, 36303. Selene Allen, Chad Laurie. Pronto Packages, MailFast.

Payment Method Ship Date Order

276 MicroStrategy Tutorial data model

© 2007 MicroStrategy, Inc.

Project Design Guide

MicroStrategy Tutorial

A

Refer to the following image to see how all these attributes are organized into the MicroStrategy Tutorial Customers hierarchy.

Time hierarchy
The Time hierarchy contains time-specific attributes, Year, Quarter, Month, and Day.

© 2007 MicroStrategy, Inc.

MicroStrategy Tutorial data model

277

Q2 02. Promotions hierarchy The Promotions hierarchy contains Promotion and Promotion Type. Inc. Q3 03. Calendar month of purchase.A MicroStrategy Tutorial Project Design Guide The Time hierarchy contains the following attributes. January. Calendar quarter of purchase. Calendar date of purchase. This hierarchy is useful for recording whether a sale was a promotional purchase. Jul 02. 2003. Month of purchase. 12/26/03. 5/14/02. November. Aug 03. Attribute Year Quarter Month of Year Month Day Description Calendar year of purchase. Refer to the following image to see how all these attributes are organized into the MicroStrategy Tutorial Time hierarchy. . Example 2002. 278 MicroStrategy Tutorial data model © 2007 MicroStrategy.

Attribute Promotion Type Promotion Description (Currently not implemented in the project. 2/16/03 2/19/03. you can also view it directly in the product. (Currently not implemented in the project. Labor Day. Inc. Example Mother’s Day. © 2007 MicroStrategy. Specify the user name as Administrator and provide a blank password to complete these steps.) Date range for a particular discount period under which an item is purchased (Sales Date). Refer to the following image to see how all these attributes are organized into the MicroStrategy Tutorial Promotions hierarchy.) Type of discount period offered (Sale type).9/4/02. You must log on as an Administrator. Viewing the MicroStrategy Tutorial data model Although the MicroStrategy Tutorial data model is displayed in the previous pages. To view the MicroStrategy Tutorial data model 1 If you are not already using the MicroStrategy Tutorial.Project Design Guide MicroStrategy Tutorial A The Promotions hierarchy contains the following attributes. 9/1/02 . log on to the project source containing the MicroStrategy Tutorial and expand the MicroStrategy Tutorial project. MicroStrategy Tutorial data model 279 .

but allows you to view the hierarchy in a way meaningful to you. 6 You can rearrange the attributes by dragging and dropping them. characteristics. After the data model is created. MicroStrategy Tutorial schema A schema is a logical and physical definition of warehouse data elements. 3 To view a different hierarchy. This does not affect the browse order. click Fit in window from the toolbar. 8 To save the layout view of the hierarchy. the next step is to create the schema. click Save in the toolbar. select it from the Hierarchy drop-down list on the toolbar. physical characteristics. the HierarchiesMicroStrategy Tutorial dialog box opens. and then choose Hierarchies. Inc. this saved view is displayed. 7 To return to the default view.A MicroStrategy Tutorial Project Design Guide 2 From the Schema menu. and interrelationships. select it from the Entry Point drop-down list in the toolbar. point to Graphical View. 280 MicroStrategy Tutorial schema © 2007 MicroStrategy. . or conceptual environment. Once loaded. 5 To view the entire hierarchy in the window. 4 To focus on a different entry point. The logical data model is a picture of all the pieces of information necessary to understand your data and how it relates to your business. and relationships of data in a business. technical. click Auto arrange in the toolbar. The next time you open the Hierarchy Viewer. It is a graphic-intensive technique that results in a data model representing the definition.

The physical warehouse schema describes how your data is stored in the data warehouse. The MicroStrategy Tutorial schema is divided into the following parts: • • • • • • Geography Products Customers Time Promotions Fact tables Schema notations The following notations are used in the graphical depictions of the MicroStrategy Tutorial schema. Several physical warehouse schemas can be derived from the same logical data model. Inc. including data types. refer to earlier chapters in this guide. such as Day. They typically consist of descriptions of dimensions. © 2007 MicroStrategy. Store. Symbol LU_ Indicates Definition a lookup table A database table used to uniquely identify attribute elements. This appendix shows the physical warehouse schema. Item. MicroStrategy Tutorial schema 281 . a primary key In a relational database. the set of columns required to uniquely identify a record in a table. Lookup tables are usually joined to fact tables in order to group the numeric facts in the fact table by dimensional attributes in the lookup tables. For more detailed information on the physical schema.Project Design Guide MicroStrategy Tutorial A The physical warehouse schema is based on the logical data model. or Account. While the logical data model tells you what facts and attributes to create. the physical warehouse schema tells you where the underlying data for those objects is stored.

Fact tables may contain atomic or summarized data. A fact table is a database table containing numeric data that may be aggregated along one or more dimensions. relate tables store information about the relationship between two attributes. 282 MicroStrategy Tutorial schema © 2007 MicroStrategy. The amount of money charged to expedite delivery service. The amount of money charged by the supplier to the company per individual item purchased. Fact Cost Discount End on hand Description The total amount charged by the supplier to the company. thus defining associations between them. .unit cost. Unit price .A MicroStrategy Tutorial Project Design Guide Symbol REL_ Indicates a relationship table Definition While lookup tables store information about one or more attributes. The basic facts from which all metrics in the MicroStrategy Tutorial were created from are listed below. The number of individual items remaining at the close of each month. Also referred to as a PMT. The total income produced by a given source accounting for all product sales deducting discounts. The amount of money charged by the company to the customer per individual item sold. The excess of the selling price of goods over their cost. The schema also contains fact tables. Inc. Freight Profit Revenue Rush Charge Unit Cost Unit Price Unit Profit Units Received Units Sold The compensation paid for the transportation of goods. The number of individual items bought by customers. The number of individual items acquired from a supplier. Relate tables contain the ID columns of two or more attributes. PMT_ a partition A warehouse table that contains information used to identify the mapping table partitioned base tables as part of a logical whole. A monetary reduction made from a regular price. Begin on hand The number of individual items available at the beginning of each month.

Inc.Project Design Guide MicroStrategy Tutorial A Geography schema © 2007 MicroStrategy. MicroStrategy Tutorial schema 283 .

A MicroStrategy Tutorial Project Design Guide Products schema 284 MicroStrategy Tutorial schema © 2007 MicroStrategy. . Inc.

MicroStrategy Tutorial schema 285 . Inc.Project Design Guide MicroStrategy Tutorial A Customers schema © 2007 MicroStrategy.

. Inc.A MicroStrategy Tutorial Project Design Guide Time schema 286 MicroStrategy Tutorial schema © 2007 MicroStrategy.

Inc. MicroStrategy Tutorial schema 287 .Project Design Guide MicroStrategy Tutorial A Promotions schema Sales fact tables © 2007 MicroStrategy.

.A MicroStrategy Tutorial Project Design Guide Inventory fact tables Miscellaneous fact tables 288 MicroStrategy Tutorial schema © 2007 MicroStrategy. Inc.

4 To change display preferences for the physical view. you can also view it or the logical schema directly in the product. Use circular joins: Select whether to use circular joins. Once loaded. the TablesMicroStrategy Tutorial dialog box opens with the physical view displayed. 2 From the Schema menu. Show column data types: Select whether to show the data type and size for each column. You must login as an Administrator to complete these steps. Show table prefixes: Select whether to display the table prefix as part of the table name. Inc. use the following options from the Options menu: • • Show joins: Select whether to connect the tables to represent the joins between the table columns. © 2007 MicroStrategy. and then choose Tables. 5 To change display preferences for the logical view. then Logical View. select View. point to Graphical View. MicroStrategy Tutorial schema 289 .Project Design Guide MicroStrategy Tutorial A Viewing the MicroStrategy Tutorial schema Although the MicroStrategy Tutorial physical schema is displayed in the previous pages. To view the MicroStrategy Tutorial schema 1 If you are not already using the Tutorial. Use circular joins: Select whether to use circular joins. 3 To switch to the logical view. use the following options from the Options menu: • • • • Show joins: Select whether to connect the tables to represent the joins between the warehouse tables. log in to the project source containing the MicroStrategy Tutorial and expand the MicroStrategy Tutorial project.

7 To view the entire schema in the window. many-to-one. one-to-many. but allows you to view the tables in a way meaningful to you. This does not affect the relationships or joins. click Auto arrange in the toolbar. Inc. The next time you open the Table Viewer. click the Fit in window button on the toolbar. 8 You can rearrange the tables by dragging and dropping them. then Physical View. select Copy as Metafile from the File menu. 290 MicroStrategy Tutorial schema © 2007 MicroStrategy. as a link between the logical and physical views. 10 To save the layout view of the tables. Show relationship types: Choose whether to differentiate between one-to-one. Show columns: Select whether to display the warehouse columns that define each attribute.A MicroStrategy Tutorial Project Design Guide • • Show relationships: Choose whether to map the relationships between the tables. click Save in the toolbar. • 6 To switch back to the physical view. . 9 To return to the default view. this saved view is displayed. select View. 11 To copy the layout view. and many-to-many relationships.

Integration with Analysis Services 2000. or Hyperion Essbase (Essbase). page 292 Understanding the SAP BW terminology. this appendix discusses the following topics: • • MicroStrategy integration with OLAP cube sources. The integration with SAP BW uses SAP’s OLAP Business Application Programming Interface (BAPI). SAP BW. Analysis Services 2005. This appendix describes how MicroStrategy Intelligence Server integrates with these products using MultiDimensional Expressions (MDX). Hyperion Essbase. Inc. Microsoft Analysis Services (Analysis Services).B CONNECTING TO OLAP CUBE SOURCES B. and Essbase uses XML for Analysis (XMLA). This system setup requires an integrated business intelligence (BI) solution. such as MicroStrategy. and Microsoft Analysis Services Introduction Many companies have both a data warehouse and an OLAP cube source such as SAP Business Intelligence Warehouse (SAP BW). that can concurrently access OLAP cube sources and the data warehouse effectively. Specifically. page 298 © 2007 MicroStrategy. 291 .

Using the MicroStrategy standard interface. page 311 Relating objects from Analysis Services 2000 to MicroStrategy. page 302 Relating objects from Essbase to MicroStrategy. all of which can be exposed via a unified Web interface. page 334 Connecting to Analysis Services 2000 servers.0.B Connecting to OLAP Cube Sources Project Design Guide • • • • • • • • • Relating objects from SAP BW to MicroStrategy. page 340 Integrating OLAP cubes into MicroStrategy. MicroStrategy refers to SAP BW/SAP BI OLAP cube sources as SAP BW.1 and 3. Intelligence Server can join data from different OLAP cube sources. • • • Microsoft Analysis Services 2000 Microsoft Analysis Services 2005 Hyperion Essbase 7.0 With version 7. page 322 Connecting to SAP BW servers.5 and SAP BI 7. page 327 Connecting to Essbase servers. Inc. page 343 MicroStrategy integration with OLAP cube sources MicroStrategy provides a rich set of functionality ranging from OLAP Services and Report Services to Narrowcast capabilities.1 292 MicroStrategy integration with OLAP cube sources © 2007 MicroStrategy. in addition to relational databases. These additional OLAP cube sources include the following: • SAP BW 3. page 317 Relating objects from Analysis Services 2005 to MicroStrategy. page 337 Connecting to Analysis Services 2005 servers. and bring the data into one single MicroStrategy project. SAP has renamed SAP BW to SAP BI. .

The XMLA integration provides a Web Service interface for OLAP and data mining functions. or another SAP data source system. MicroStrategy Intelligence Server is certified to connect and execute reports against SAP BW cubes.5. Analysis Services and Essbase store data in cubes obtained from various sources. MicroStrategy has chosen to use the OLAP BAPI approach because it is the most native interface that SAP provides. and properties data.com/ and search for MDX. As SAP’s proprietary API for accessing SAP BW data and functionality. Rather. To access the data. In other words. and MicroStrategy Web and SDK are certified to run with SAP Enterprise Portal through iView Packages. you can get the best out of both products. Inc. the OLAP BAPI provides an open interface through which Intelligence Server can access the SAP BW data.3. With the Powered by Net Weaver Certification on MicroStrategy 7i -7.xmla.1 of the specification is available at www. It is important to understand that the MicroStrategy integration with OLAP cube sources does not change the overall structure of the MicroStrategy product. SAP BW obtains data from R/3.microsoft. This data is stored in cubes or other SAP objects.org and is the basis for the MicroStrategy implementation. With the SAP BW OLAP BAPI Certification on MicroStrategy 8. each of these products is simply another data warehouse that holds data for report generation. SEM. If you use OLAP cube sources and MicroStrategy as your combined BI solution. including the following: © 2007 MicroStrategy. Likewise.0. An MDX expression returns a multidimensional result set (dataset) that consists of axis data. cell data. refer to http://msdn. Defined by Microsoft. Version 1. CRM. For more information on MDX syntax. integration allows MicroStrategy to gain additional data sources for analysis. MicroStrategy integration with OLAP cube sources 293 . MicroStrategy Web Universal is certified to run on SAP Web Application Server. see the MicroStrategy readme. the Intelligence Server generates MDX. MDX is similar to SQL but is used to query cubes.Project Design Guide Connecting to OLAP Cube Sources B For MicroStrategy’s support status with the OLAP cube sources listed above.

Data is pulled from multiple OLAP cube sources using MDX and operational systems using Freeform SQL or Query Builder. see the Troubleshooting the System chapter of the MicroStrategy System Administration Guide. Report Services. . Understanding MicroStrategy architecture The MicroStrategy platform offers OLAP Services. Essbase. refer to the MicroStrategy Advanced Reporting Guide. Support for SAP BW. and Query Builder provides additional mechanisms for pulling data into the MicroStrategy platform for analysis. it is treated in the same 294 MicroStrategy integration with OLAP cube sources © 2007 MicroStrategy. Once the data is retrieved.B Connecting to OLAP Cube Sources Project Design Guide • • • • • Access to OLAP cube sources and a regular data warehouse Five styles of BI Custom development of reports and applications Transaction-level analysis Integration with other systems via Web Services For troubleshooting and diagnostics logging routines related to OLAP cube sources. Analysis Services. Freeform SQL. as illustrated in the following diagram. For information on Freeform SQL and Query Builder reporting. and Narrowcast Server functionality. all of which can be accessed through MicroStrategy Web. Inc.

This means that core MicroStrategy capabilities are available no matter what the original data source is. © 2007 MicroStrategy. shown below. MicroStrategy integration with OLAP cube sources 295 . Object model in MicroStrategy 7i In the 7i metadata model. Inc. To understand the current MicroStrategy architecture better. One database instance could be referenced by multiple projects in a configuration.Project Design Guide Connecting to OLAP Cube Sources B manner as data pulled from the relational data warehouse. you could have multiple MicroStrategy projects. Each project contained one project schema that held the logical model for that project. which was represented by the database instance. each pointing to a data warehouse. it is helpful to review the basic object model of MicroStrategy 7i and how various data sources were accessed then.

However. Object model in MicroStrategy 8 The MicroStrategy 8 model shown below highlights how a project can be extended to access OLAP cube sources through a separate database instance. each of which can represent a distinct OLAP cube source. In addition. 296 MicroStrategy integration with OLAP cube sources © 2007 MicroStrategy. note that instead of pointing to the project schema. and a single MicroStrategy project can reference multiple database instances. a Report Services document can contain multiple datasets. . which is a logical placeholder for a physical cube that exists in an OLAP cube source. Inc. Each report can only reference one specific cube. due to the structure in OLAP cube sources where queries can only be run against one cube at a time. but the only source is the data warehouse. the SQL Engine would implicitly reference the schema to determine which table(s) should be queried. You can create multiple reports to run against one cube.B Connecting to OLAP Cube Sources Project Design Guide When a report was executed. each OLAP cube report points directly to one cube in MicroStrategy.

Inc. Query Builder reports. refer to the MicroStrategy Advanced Reporting Guide. described as follows: © 2007 MicroStrategy. For information on Freeform SQL and Query Builder reports.Project Design Guide Connecting to OLAP Cube Sources B The model also shows how you can include any number of standard reports. refer to the MicroStrategy Document Creation Guide. Freeform SQL reports. and OLAP cube reports in one Report Services document. MicroStrategy integration with OLAP cube sources 297 . report designers can create rich reports and analytics that take advantage of data from both data warehouses and OLAP cube sources. By bringing these different types of reports together inside a document. Authentication Most of the standard MicroStrategy platform authentication features also apply to OLAP cube sources and OLAP cube reports. For information on Report Services documents.

refer to your SAP documentation. specific connection mappings may be designated for each database instance and user or group combination. Some of these terms are provided in the following section. but not to the cube sources. NT Authentication can be used to authenticate the user to the Intelligence Server. page 302. 298 Understanding the SAP BW terminology © 2007 MicroStrategy.B Connecting to OLAP Cube Sources Project Design Guide • Standard authentication and LDAP authentication: are supported independent of the data source that is being used. . then the same login information must be applicable to all sources. • • • For information on authentication in general. This is explained in Relating objects from SAP BW to MicroStrategy. Further information is provided later in this appendix on how the SAP BW objects are related to those in the MicroStrategy environment. relational databases or OLAP cube sources. it is recommended that you use connection mapping or pass-through authentication. Understanding the SAP BW terminology Before looking in depth into how MicroStrategy integrates with SAP BW. Warehouse pass-through authentication: is supported in the same way as for relational data providers. Inc. for example. Connection mapping: is supported the same way as for standard MicroStrategy reports. refer to the MicroStrategy System Administration Guide. NT authentication: used for database logins are not supported with OLAP cube sources. If multiple sources are configured for warehouse pass-through execution. To enforce OLAP cube source security in MicroStrategy. you need to be familiar with the terms that are used to describe the SAP BW objects. For a comprehensive and detailed explanation on SAP BW objects. In addition.

Data is organized by dimension and stored physically in a star schema. To release a query for analysis in MicroStrategy. ODS objects are flat relational tables and are similar to MicroStrategy fact tables. The relationship between the InfoCube and the query cube is very similar to how a MicroStrategy report includes a subset of modeled attributes and metrics that are available in the data warehouse. three InfoCubes or two ODS objects. which are roughly equivalent to attributes and facts in a MicroStrategy project. Understanding the SAP BW terminology 299 . InfoProvider: is a generic term defining all SAP BW data structures available for reporting and analysis purposes such as the following: InfoCube: is a multi-dimensional cube. They include objects such as characteristics and key figures. InfoSets. A query cube includes characteristics (dimensions/attributes) and key figures (metrics) from its source provider. Query cubes generally offer better performance than InfoCubes because they are smaller and can be scheduled and cached within SAP BW. Inc. InfoCubes define a specific domain of analysis in special areas. MultiProvider: is a logical union of two or more InfoProviders that are used to combine data from two different subject areas. Any existing query can be released for analysis within MicroStrategy. Query cubes also provide MicroStrategy users access to additional InfoProviders including ODS objects. which is described below. • • InfoCube: is the primary object that SAP BW uses to store data for analysis. ODS object: is an operational data store object. for example. for example.Project Design Guide Connecting to OLAP Cube Sources B • InfoObject: are the building blocks for individual cubes. The fact table at the center of an InfoCube contains the data available for analysis. and MultiProviders. finance or sales. Query cube (or query): defines a subset of data from an InfoCube or another InfoProvider. select the Allow External Access to This Query check box under the Extended tab in the SAP Query Properties dialog box in the Query Analyzer • © 2007 MicroStrategy.

• Characteristic: provides classification possibilities for a dataset. With this option enabled. When the query is executed. However. Inc. numbers. hierarchies can be associated with a specific characteristic within SAP BW. a Sales Region characteristic can have North. and finally Item. There are five types of key figures: amount. This is similar to creating derived metrics and conditional metrics within the MicroStrategy environment. and number of call centers. For example. However. and master data attributes. texts. In addition. as noted later. These hierarchies are also available when you work with a cube in MicroStrategy. quantities. it is treated as a separate dimension for analysis. For example. You can also create calculated key figures and restricted key figures in the query definition in the Business Explorer. and period. profit. hierarchies. such as revenue. they are presented with the traditional attribute-based parent-child relationships. when each characteristic is translated into a cube. • • 300 Understanding the SAP BW terminology . when the levels of a hierarchy are viewed in MicroStrategy. ODS objects. the Item characteristic might have a hierarchy that includes Category. variables can be of such types as characteristic values. Defined in the Query Designer. designers can quickly access existing query cubes and business content when working in MicroStrategy. all of which can be used in InfoCubes. but it is equivalent to an attribute form in MicroStrategy. customer group. hierarchy nodes.B Connecting to OLAP Cube Sources Project Design Guide interface. and South specifications. Hierarchy: is a way of defining the relationships among elements within a characteristic. date. Central. and formulas. • Key figure: describes numeric data. © 2007 MicroStrategy. product. such as sales region. SAP BW characteristics are similar to MicroStrategy attributes. and time. Variable: is used as a parameter of a query in SAP BW. these variables are filled with values by the system or by the user. SAP BW also has an object called an attribute. Subcategory. This is a different paradigm from MicroStrategy’s model where each attribute defines its own level. fiscal year.

you also need to have a basic understanding of the SAP Query Designer. rows. refer to the MicroStrategy Desktop online help.Project Design Guide Connecting to OLAP Cube Sources B When an OLAP cube is imported into a MicroStrategy project. the report inherits all those prompts. © 2007 MicroStrategy. Understanding the SAP BW terminology 301 . page 308. In addition. Inc. columns. For more information. all the variables in this cube are represented as prompts. InfoCubes. refer to documentation provided by SAP BW. see Supporting SAP BW variables. and free characteristics. Besides the above-mentioned terminology. For more information on variables. For step-by-step instructions on how to create MicroStrategy reports from the data in SAP BW cubes. you will find a list of available cubes for reporting. standard prompts can also be created for this report. You can select and combine InfoObjects or reusable structures for an InfoProvider and specify the view of the data (query view) by distributing them to filters. including all of the published query cubes. and MultiProviders. where you define queries. When the OLAP cube is used to create a MicroStrategy report. When working in MicroStrategy.

302 Relating objects from SAP BW to MicroStrategy © 2007 MicroStrategy. The translation process involves the following steps: 1 From SAP BW to ODBO: SAP exposes its query cubes and InfoCubes to Intelligence Server through the ODBO model. ODBO defines an object model that is used in conjunction with MDX to query cubes.B Connecting to OLAP Cube Sources Project Design Guide Relating objects from SAP BW to MicroStrategy As a Web or Desktop Analyst. ODBO stands for OLE database for OLAP and is a protocol defined by Microsoft. However. but not identical. The ODBO model is similar to SAP’s standard model. when thinking about SAP objects. . Thus. you can treat SAP BW reports as if they were standard MicroStrategy reports. keep in mind how those objects appear in ODBO. it is helpful to understand how SAP’s metadata model is translated into MicroStrategy’s metadata model. if you are a report designer. Inc.

SAP BW ---> InfoCube ODBO ---> catalog MicroStrategy (catalog) • SAP BW: InfoCube Each InfoCube that has queries associated with it is exposed as a catalog in ODBO. You can then interact with SAP content while working within the paradigm that is consistent with the rest of MicroStrategy’s products.Project Design Guide Connecting to OLAP Cube Sources B 2 From ODBO to MicroStrategy: After SAP objects are translated into the ODBO model. Inc. they are then translated into the MicroStrategy metadata model. Query cubes are accessed through their respective InfoCube catalogs. The following sub-sections—each starting with a table—describe each level of comparison from top to bottom as shown in the above illustration. Relating objects from SAP BW to MicroStrategy 303 . © 2007 MicroStrategy. The following image demonstrates how SAP BW objects are exposed in ODBO and then how they are related to objects in the MicroStrategy environment.

a MicroStrategy cube maps the physical columns of an SAP BW cube to attributes and metrics. Catalogs in MicroStrategy are represented in a folder. Inc. . SAP BW ---> N/A ODBO ---> schema MicroStrategy N/A • • SAP BW: not supported ODBO: schema Schema in ODBO provides another grouping mechanism. The cube can be used to represent InfoCubes. ODBO catalogs are exposed in a few editors when selecting and managing cubes. 304 Relating objects from SAP BW to MicroStrategy © 2007 MicroStrategy.B Connecting to OLAP Cube Sources Project Design Guide • ODBO: Catalog Catalogs are used to group cubes. In the same way that a regular table maps the physical columns of a relational table to attributes and metrics. MultiProviders. • MicroStrategy: not supported SAP BW ---> InfoCube/ query cube ODBO ---> cube MicroStrategy cube • • • SAP BW: InfoCube/query cube ODBO: cube MicroStrategy: cube A MicroStrategy cube is an object that is used to map the levels of an SAP BW cube into the MicroStrategy environment. • MicroStrategy: (Catalog) Each catalog includes one InfoCube and associated query cubes. if any. and query cubes. Cubes are treated in a manner very similar to tables in the MicroStrategy metadata. Therefore.

However. © 2007 MicroStrategy. Quarter. which represents months just like it does in MicroStrategy. and Month. and the second level is the detailed data. Dimensions in SAP BW are used to group characteristics and are not exposed through the ODBO interface. The SAP BW characteristic hierarchies appear as hierarchies to MicroStrategy users. For example. an InfoCube might include the Month characteristic. A characteristic can have any number of additional hierarchies. This hierarchy defines a number of levels including Year. They can only be seen inside the SAP BEx Query Designer when you build a query cube. For more information. Inc. Each characteristic in SAP is modeled as a dimension in ODBO and is shared across cubes. see the following sub-section. A characteristic appears as a dimension for MicroStrategy users. Therefore. Each characteristic (dimension) has at least one hierarchy with two levels: the first level is an aggregate of all the data. For example. • ODBO: dimension A dimension in ODBO defines a logical category of analysis. Shared dimensions allow a designer to use only one definition for a dimension across multiple cubes.Project Design Guide Connecting to OLAP Cube Sources B SAP BW ---> characteristic ODBO ---> dimension MicroStrategy dimension • SAP BW: characteristic Characteristics in SAP BW are similar to attributes in MicroStrategy. Relating objects from SAP BW to MicroStrategy 305 . Time and Geography are dimensions along which you can slice data. For example. these same levels could either be specifically defined as part of the hierarchy. all dimensions in cubes coming from SAP BW are shared. you can build a Time hierarchy that is attached to the Month characteristic. or they could be other characteristics that are used to define the levels of this one hierarchy. each with an arbitrary number of levels.

It is used to group attributes and define parent-child relationships. Inc. In this way. Measures in ODBO are called key figures in SAP BW. which are very similar to metrics in MicroStrategy. SAP BW ---> virtual level ODBO ---> level MicroStrategy attribute • SAP BW: virtual level Levels are generated automatically based on either the definition of the characteristic or the hierarchies associated with a characteristic. 306 Relating objects from SAP BW to MicroStrategy © 2007 MicroStrategy. The inclusion of the term “Level” is an SAP BW convention. measures are simply one more dimension of a cube. architects have the option to rename the levels of a cube with a more readable convention. and they are represented as physical columns. . SAP BW ---> hierarchy ODBO ---> hierarchy MicroStrategy hierarchy • • • SAP BW: hierarchy ODBO: hierarchy MicroStrategy: hierarchy Hierarchies are used to group attributes (levels) together and define the relationships between these attributes.B Connecting to OLAP Cube Sources Project Design Guide Measures (metrics) are stored in a special measure dimension. and so on. MicroStrategy reuses the hierarchy objects to represent both dimensions and hierarchies from ODBO. • MicroStrategy: dimension A dimension object in MicroStrategy is very similar to an ODBO dimension. Region Level 02. In MicroStrategy. SAP BW levels have names such as Region Level 01.

Project Design Guide Connecting to OLAP Cube Sources B • • ODBO: level MicroStrategy: attribute (ID/DESC) MicroStrategy attributes map to ODBO levels. each ODBO level generates two physical columns and forms in MicroStrategy—ID and DESC. These attributes are presented as distinct dimensions when working in MicroStrategy. © 2007 MicroStrategy. This concept also applies to ODBO and SAP BW. For example. SAP BW ---> characteristic value ODBO ---> member MicroStrategy (attribute element) • • • SAP BW: characteristic value ODBO: member MicroStrategy: (attribute element) Element values come from either the database or a cube. SAP BW ---> characteristic attribute ODBO ---> property MicroStrategy attribute form • • • SAP BW: characteristic attribute ODBO: property MicroStrategy: attribute form Attribute forms provide additional information about a given attribute. forms are sometimes referred to directly as attributes. 2003 and 2004 are elements of the Year attribute. the Customer attribute may have the forms First Name and Last Name. For example. However. Relating objects from SAP BW to MicroStrategy 307 . In SAP BW. SAP BW also supports navigational attributes. Inc.

For more information. On top of the “inherited” variable prompts. additional standard MicroStrategy prompts can also be created for the report. When the query is being executed. the report inherits the prompts included in the OLAP cube. The conversion process involves the following general steps: 1 When an SAP query cube is imported into a MicroStrategy project. Only variables with the Manual Entry/Default processing type are presented to users for resolution. see the Prompts section of the Creating OLAP Cube Reports chapter of the MicroStrategy Advanced Reporting Guide. 308 Relating objects from SAP BW to MicroStrategy © 2007 MicroStrategy. and formula elements. you must remove them before importing the cube into MicroStrategy. these variables are filled with values. an error occurs when you attempt to import the SAP BW cube. . variables are represented as prompts in the MicroStrategy environment.B Connecting to OLAP Cube Sources Project Design Guide Supporting SAP BW variables Variables are used in SAP BW to enter values as parameters for the queries on a cube. texts. 2 When a MicroStrategy report is created using a MicroStrategy OLAP cube. including characteristic values. Inc. Otherwise. hierarchies. refer to your SAP documentation. For detailed information on variables. Variable types with the Customer Exit/SAP Exit and Authorization processing types are automatically resolved by the SAP BW system. If your SAP BW cube included variables of type Replacement Path. variables are automatically turned into prompts in the MicroStrategy OLAP cube. There are several types of variables. Originally created in an SAP query cube. SAP BW variables of type Replacement Path cannot be imported into MicroStrategy. hierarchy nodes.

Inc. Default Low Description. dimensions. you can view any variable’s properties by right-clicking its name and then selecting Properties. Entry Type. Rename the prompt. including Variable Name. © 2007 MicroStrategy. The OLAP Cube Catalog lists all the prompts that were converted from variables. as shown in the following image. Details about this variable in SAP BW are displayed on the Variable tab. In addition. and measures/key figures. In the OLAP Cube Catalog. Default Low. and Variable Ordinal. or Map the variable to a prompt in an existing MicroStrategy project. Selection Type. in addition to cube names.Project Design Guide Connecting to OLAP Cube Sources B Mapping between variables and prompts can be viewed in the OLAP Cube Catalog. Variable Type. using the right-mouse click you can Edit the prompt in the Prompt Generation Wizard. Relating objects from SAP BW to MicroStrategy 309 .

Inc. see the Prompts section of the Creating OLAP Cube Reports chapter of the MicroStrategy Advanced Reporting Guide. This allows the same prompt answer to be used to resolve multiple variables during document execution. you can view the prompt details in the Report Details pane in the Report Editor. Not supported. After an OLAP cube report is executed. so it is distinguished from a simple characteristic variable on date. 310 Relating objects from SAP BW to MicroStrategy © 2007 MicroStrategy. When executing a Report Services document with multiple datasets using these cubes. The following table contains information on how the different types of SAP BW variables are mapped to MicroStrategy prompts. the MicroStrategy interface qualifies on the key value of each element by default. To be consistent with the SAP functionality. a prompt is displayed only once. Hierarchy Node variable Hierarchy element list prompt Text variable Formula variable N/A Value prompt: all types Characteristic value variables offer an “Including/Excluding” option. . Not available from SAP BW. For more information about prompts in OLAP cube reports. you need to manually set the variable’s property in the OLAP Cube Catalog.B Connecting to OLAP Cube Sources Project Design Guide One prompt can be mapped to more than one variable across cubes. Both single and multiple selection are supported. SAP Variable Type ---> Characteristic Value variable Hierarchy variable MicroStrategy Prompt Element list prompt or attribute qualification prompt N/A Notes See the note below for more information. Qualifications in the Including section cause the data to be brought into the query. while those in the Excluding section restrict the data from being displayed in the query. No major changes. If you use any SAP BW key date variables in your query. This is especially useful if you want to get a summary of the variable elements that are used in answering the variable prompts.

it is helpful to understand how Essbase’s metadata model is translated into MicroStrategy’s metadata model. and then click OK. a query could also have characteristic structures. 2 On the Variable tab. Relating objects from Essbase to MicroStrategy 311 . Inc. Each element of a key figure structure is represented as a unique metric in the MicroStrategy environment. each of which is represented as a single flat dimension with one level. This representation is consistent with how characteristic variables are represented in SAP BW through the OLAP Business Application Programming Interface (BAPI). Relating objects from Essbase to MicroStrategy As a Web or Desktop Analyst.Project Design Guide Connecting to OLAP Cube Sources B Set the properties for key date variables 1 Right-click the variable name and select Properties. In a MicroStrategy report. you cannot drill down into the elements of characteristic structures. However. The Properties [variable name] dialog box is displayed. In addition to key figure structures. © 2007 MicroStrategy. you can treat OLAP cube reports from an Essbase OLAP cube as if they were standard MicroStrategy reports. select the Set Key Date check box. if you are a report designer. SAP BW structures Structures in an SAP BW query cube define the two axes of a query (rows and columns) and are of two types: key figure structures and characteristic structures.

312 Relating objects from Essbase to MicroStrategy © 2007 MicroStrategy.B Connecting to OLAP Cube Sources Project Design Guide The translation process involves the following steps: 1 From Essbase to XMLA: Essbase exposes its databases through the XMLA model which is derived from the ODBO model used by SAP. Inc. keep in mind how those objects appear in XMLA. XMLA defines an object model that is used in conjunction with MDX to query cubes. they are then translated into the MicroStrategy metadata model. . The Essbase model predates XMLA so there are some differences. When thinking about Essbase objects. 2 From XMLA to MicroStrategy: After Essbase objects are translated into the XMLA model. The following image demonstrates how Essbase objects are exposed in XMLA and then how they are related to objects in the MicroStrategy environment. You can then interact with Essbase content while working within the paradigm that is consistent with the rest of MicroStrategy’s products.

• MicroStrategy: not supported Essbase ---> database XMLA ---> cube MicroStrategy cube • • Essbase: database XMLA: cube © 2007 MicroStrategy. Relating objects from Essbase to MicroStrategy 313 . Databases are accessed through their respective catalogs. Inc. • XMLA: catalog Catalogs are used to group cubes. Therefore. Essbase ---> N/A XMLA ---> schema MicroStrategy N/A • • Essbase: not supported XMLA: schema Schema in XMLA provides another grouping mechanism. XMLA catalogs are exposed in editors when selecting and managing cubes. if any. Catalogs in MicroStrategy are represented as a folder.Project Design Guide Connecting to OLAP Cube Sources B The following subsections (each starting with a table) describe each level of comparison from top to bottom as shown in the above illustration. • MicroStrategy: (catalog) Each catalog includes one application and associated databases. Essbase ---> Application XMLA ---> catalog MicroStrategy (catalog) • Essbase: Application Each Application is exposed as a catalog in XMLA.

For example. An Essbase dimension appears as a dimension for MicroStrategy users. Measures in ODBO are the members of the dimension of type=Accounts in Essbase. . • XMLA: dimension A dimension in XMLA defines a logical category of analysis. Cubes are treated in a manner very similar to tables in the MicroStrategy metadata. These can be raw data or formulas with associated calculation or aggregation rules. measures are simply one more dimension of a cube. Time and Geography are dimensions along which you can slice data. In this way. Essbase ---> dimension XMLA ---> dimension MicroStrategy dimension • Essbase: dimension In Essbase. A MicroStrategy cube maps the physical columns of an Essbase cube to attributes and metrics in the same way that a regular table maps the physical columns of a relational table to attributes and metrics. Measures (metrics) are stored in a special measure dimension. a dimension represents the highest consolidation level in the database outline. Inc.B Connecting to OLAP Cube Sources Project Design Guide • MicroStrategy: cube A MicroStrategy cube is an object that is used to map the levels of an Essbase cube into the MicroStrategy environment. Each dimension has a single hierarchy with the number of levels determined by the greatest depth in the outline. The cube represents an Essbase database. The dimension therefore is both the highest level member in the dimension and the dimension itself. Each dimension has a single root node or member and is a child of the outline root node which is the database. • MicroStrategy: dimension 314 Relating objects from Essbase to MicroStrategy © 2007 MicroStrategy.

Project Design Guide Connecting to OLAP Cube Sources B A dimension object in MicroStrategy is very similar to an XMLA dimension. • • XMLA: level MicroStrategy: attribute (ID/DESC) © 2007 MicroStrategy. • • XMLA: hierarchy MicroStrategy: hierarchy Hierarchies are used to group attributes (levels) together and define the relationships between these attributes. Inc. Essbase ---> dimension XMLA ---> hierarchy MicroStrategy hierarchy • Essbase: dimension An Essbase dimension is defined as part of the database outline. It is used to group attributes and define parent-child relationships. Essbase ---> level XMLA ---> level MicroStrategy attribute • Essbase: level Levels group together members in an Essbase database outline. Relating objects from Essbase to MicroStrategy 315 . In MicroStrategy.Levels(0). the outline defines a single hierarchy. As a result. Essbase levels may have default names such as Time. architects have the option to rename the levels of a cube with a more readable convention. Therefore the dimension is the same as the hierarchy in Essbase. MicroStrategy reuses the hierarchy objects to represent both dimensions and hierarchies from XMLA. The outline is a hierarchical structure of database members with a parent containing its children.

Until they are returned as rows in the property schema rowset they are not available as attribute forms in MicroStrategy. For example. However. 316 Relating objects from Essbase to MicroStrategy © 2007 MicroStrategy.B Connecting to OLAP Cube Sources Project Design Guide MicroStrategy attributes map to XMLA levels. For example. However. each XMLA level generates the two physical columns and forms ID and DESC in MicroStrategy. Essbase ---> member XMLA ---> member MicroStrategy attribute element • • • Essbase: member XMLA: member MicroStrategy: attribute element Element values come from either the database or a cube. 2003 and 2004 are elements of the Year attribute. Inc.1. • • XMLA: property MicroStrategy: attribute form Attribute forms provide additional information about a given attribute. properties can be defined for a database as user defined attributes or attribute dimensions and used in an MDX statement. Essbase ---> N/A XMLA ---> property MicroStrategy attribute form • Essbase: N/A Essbase as of version 7. .3 does not return any properties in the XMLA property schema rowset. the Customer attribute may have the forms First Name and Last Name.

XMLA defines an object model that is used in conjunction with MDX to query cubes.Project Design Guide Connecting to OLAP Cube Sources B Relating objects from Analysis Services 2000 to MicroStrategy Microsoft Analysis Services 2000 (Analysis Services 2000) cubes are exposed directly for XMLA access. it is helpful to understand how Analysis Services 2000’s metadata model is translated into MicroStrategy’s metadata model. If you are a report designer. © 2007 MicroStrategy. The translation process involves the following steps: 1 From Analysis Services 2000 to XMLA: Analysis Services 2000 exposes its cubes through the XMLA model which is derived from the ODBO model. they are then translated into the MicroStrategy metadata model. Relating objects from Analysis Services 2000 to MicroStrategy 317 . Inc. 2 From XMLA to MicroStrategy: After Analysis Services 2000 objects are translated into the XMLA model. You can then interact with Analysis Services 2000 content while working within the paradigm that is consistent with the rest of MicroStrategy’s products.

Therefore. Analysis Services 2000 ---> XMLA ---> database catalog MicroStrategy (catalog) • Analysis Services 2000: database Each database is exposed as a catalog in XMLA. Cubes are accessed through their respective catalogs. • MicroStrategy: (catalog) 318 Relating objects from Analysis Services 2000 to MicroStrategy © 2007 MicroStrategy. • XMLA: catalog Catalogs are used to group cubes. The following sub-sections—each starting with a table—describe each level of comparison from top to bottom as shown in the above illustration. XMLA catalogs are exposed in editors when selecting and managing cubes. .B Connecting to OLAP Cube Sources Project Design Guide The following image demonstrates how Analysis Services 2000 objects are exposed in XMLA and then how they are related to objects in the MicroStrategy environment. Inc.

Catalogs in MicroStrategy are represented as a folder. Relating objects from Analysis Services 2000 to MicroStrategy 319 . In the same way that a regular table maps the physical columns of a relational table to attributes and metrics. Inc. if any. • MicroStrategy: not supported Analysis Services 2000 ---> XMLA ---> cube cube MicroStrategy cube • • • Analysis Services 2000: cube XMLA: cube MicroStrategy: cube A MicroStrategy cube is an object that is used to map the levels of an Analysis Services 2000 cube into the MicroStrategy environment. Cubes are treated in a manner very similar to tables in the MicroStrategy metadata.Project Design Guide Connecting to OLAP Cube Sources B Each catalog includes one database and associated cubes. Analysis Services 2000 ---> XMLA ---> N/A schema MicroStrategy N/A • • Analysis Services 2000: not supported XMLA: schema Schema in XMLA provides another grouping mechanism. a MicroStrategy cube maps the physical columns of an Analysis Services 2000 cube to attributes and metrics. Analysis Services 2000 ---> XMLA ---> dimension dimension MicroStrategy dimension • Analysis Services 2000: dimension © 2007 MicroStrategy. The cube represents an Analysis Services 2000 cube.

Time and Geography are dimensions along which you can slice data. related dimensions can be grouped together so that they represent hierarchies of the same dimension from an XMLA perspective. measures are simply one more dimension of a cube.B Connecting to OLAP Cube Sources Project Design Guide In Analysis Services 2000. An Analysis Services 2000 dimension appears as a dimension for MicroStrategy users. MicroStrategy reuses the hierarchy objects to represent both dimensions and hierarchies from XMLA. In this way. 320 Relating objects from Analysis Services 2000 to MicroStrategy © 2007 MicroStrategy. Measures (metrics) are stored in a special measure dimension. • MicroStrategy: dimension A dimension object in MicroStrategy is very similar to an XMLA dimension. • XMLA: dimension A dimension in XMLA defines a logical category of analysis. Analysis Services 2000 ---> XMLA ---> dimension hierarchy MicroStrategy hierarchy • Analysis Services 2000: dimension Using a structured naming approach. Measures in XMLA are the members of the Measures dimension in Analysis Services 2000. These can be columns in the table or calculated members represented by formulas with associated aggregation rules. It is used to group attributes and define parent-child relationships. a dimension is defined from one or more tables of data. • • XMLA: hierarchy MicroStrategy: hierarchy Hierarchies are used to group attributes (levels) together and define the relationships between these attributes. Inc. For example. Each dimension can have one or more hierarchies. .

each XMLA level generates two physical columns and forms in MicroStrategy—ID and DESC. For example. 2003 and 2004 are elements of the Year attribute. Inc. However. • • XMLA: level MicroStrategy: attribute (ID/DESC) MicroStrategy attributes map to XMLA levels. Member properties are returned in the XMLA property schema rowset. Analysis Services 2000 ---> XMLA ---> member property property MicroStrategy attribute form • Analysis Services 2000: member property A member property is a descriptive piece of information associated with the element of a level. XMLA: property MicroStrategy: attribute form Relating objects from Analysis Services 2000 to MicroStrategy 321 . Analysis Services 2000 ---> XMLA ---> member member MicroStrategy attribute element • • • Analysis Services 2000: member XMLA: member MicroStrategy: attribute element Element values come from a cube.Project Design Guide Connecting to OLAP Cube Sources B Analysis Services 2000 ---> XMLA ---> level level MicroStrategy attribute • Analysis Services 2000: level Levels are mapped to columns in a table and are organized into hierarchies and dimensions. • • © 2007 MicroStrategy.

This section is limited to information on the basic cube object and how it relates to the XMLA model. Inc. . You can then interact with Analysis Services 2005 content while working within the paradigm that is consistent with the rest of MicroStrategy’s products. Relating objects from Analysis Services 2005 to MicroStrategy Microsoft Analysis Services 2005 (Analysis Services 2005) has a unique modeling approach for building cubes. The translation process involves the following steps: 1 From Analysis Services 2005 to XMLA: Analysis Services 2005 exposes its cubes through the XMLA model which is derived from the ODBO model. 322 Relating objects from Analysis Services 2005 to MicroStrategy © 2007 MicroStrategy. they are then translated into the MicroStrategy metadata model. 2 From XMLA to MicroStrategy: After Analysis Services 2005 objects are translated into the XMLA model.B Connecting to OLAP Cube Sources Project Design Guide Attribute forms provide additional information about a given attribute. the Customer attribute may have the forms First Name and Last Name. For example. XMLA defines an object model that is used in conjunction with MDX to query cubes.

Relating objects from Analysis Services 2005 to MicroStrategy 323 . Cubes are accessed through their respective catalogs. • XMLA: catalog Catalogs are used to group cubes. Therefore. The following sub-sections—each starting with a table—describe each level of comparison from top to bottom as shown in the above illustration. • MicroStrategy: (catalog) © 2007 MicroStrategy. Analysis Services 2005 ---> XMLA ---> database catalog MicroStrategy (catalog) • Analysis Services 2005: database Each database is exposed as a catalog in XMLA.Project Design Guide Connecting to OLAP Cube Sources B The following image demonstrates how Analysis Services 2005 objects are exposed in XMLA and then how they are related to objects in the MicroStrategy environment. Inc. XMLA catalogs are exposed in editors when selecting and managing cubes.

324 Relating objects from Analysis Services 2005 to MicroStrategy © 2007 MicroStrategy. . The cube represents an Analysis Services 2005 cube. Cubes are treated in a manner very similar to tables in the MicroStrategy metadata. In the same way that a regular table maps the physical columns of a relational table to attributes and metrics.B Connecting to OLAP Cube Sources Project Design Guide Each catalog includes one database and associated cubes. • • XMLA: cube MicroStrategy: cube A MicroStrategy cube is an object that is used to map the levels of an Analysis Services 2005 cube into the MicroStrategy environment. Analysis Services 2005 ---> XMLA ---> N/A schema MicroStrategy N/A • • Analysis Services 2005: not supported XMLA: schema Schema in XMLA provides another grouping mechanism. Inc. • MicroStrategy: not supported Analysis Services 2005 ---> XMLA ---> perspective cube MicroStrategy cube • Analysis Services 2005: perspective A perspective in Analysis Services 2005 is a view of the defined cube and the list of perspectives includes the original cube. Catalogs in MicroStrategy are represented as a folder. a MicroStrategy cube maps the physical columns of an Analysis Services 2005 cube to attributes and metrics. if any.

measures are simply one more dimension of a cube. It is used to group attributes and define parent-child relationships. a dimension is defined from one or more data source tables. a data source does not always map directly to the tables in a relational database. Time and Geography are dimensions along which you can slice data. For example. In this way. Each attribute is used to define a hierarchy within the dimension and multi-level hierarchies can be defined as well. Each dimension can have one or more hierarchies. • XMLA: dimension A dimension in XMLA defines a logical category of analysis. • MicroStrategy: dimension A dimension object in MicroStrategy is very similar to an XMLA dimension. These can be columns in the data source table or calculated members represented by formulas with associated aggregation rules.Project Design Guide Connecting to OLAP Cube Sources B Analysis Services 2005 ---> XMLA ---> dimension dimension MicroStrategy dimension • Analysis Services 2005: dimension In Analysis Services 2005. Measures (metrics) are stored in a special measure dimension. Relating objects from Analysis Services 2005 to MicroStrategy 325 . Measures in XMLA are the members of the Measures dimension in Analysis Services 2005. Inc. Unlike Analysis Services 2000. An Analysis Services 2005 dimension appears as a dimension for MicroStrategy users. Analysis Services 2005 ---> XMLA ---> hierarchy hierarchy MicroStrategy hierarchy © 2007 MicroStrategy. All columns in the tables are eligible to become attributes of the dimension.

However.B Connecting to OLAP Cube Sources Project Design Guide • Analysis Services 2005: hierarchy Analysis Services 2005 allows the definition of one or more hierarchies within a dimension as collections of attributes which become levels of the hierarchy. 326 Relating objects from Analysis Services 2005 to MicroStrategy © 2007 MicroStrategy. • • XMLA: level MicroStrategy: attribute (ID/DESC) MicroStrategy attributes map to XMLA levels. Analysis Services 2005 ---> XMLA ---> member member MicroStrategy attribute element • • • Analysis Services 2005: member XMLA: member MicroStrategy: attribute element Element values come from a cube. 2003 and 2004 are elements of the Year attribute. each XMLA level generates two physical columns and forms in MicroStrategy—ID and DESC. MicroStrategy reuses the hierarchy objects to represent both dimensions and hierarchies from XMLA. Analysis Services 2005 ---> XMLA ---> level level MicroStrategy attribute • Analysis Services 2005: level Each attribute in a hierarchy becomes a level. . Inc. • • XMLA: hierarchy MicroStrategy: hierarchy Hierarchies are used to group attributes (levels) together and define the relationships between these attributes. For example.

Connecting to SAP BW servers In addition to relational databases. For example.5. MicroStrategy certifies connecting to SAP BW 3. • • XMLA: property MicroStrategy: attribute form Attribute forms provide additional information about a given attribute. you need to establish a connection to the SAP BW system. Before creating any reports using the SAP BW data. refer to the MicroStrategy Desktop online help. For more information on establishing a connection to SAP BW. Connecting to SAP BW servers 327 . 3.0. For any late-breaking changes to the certification status of connecting to various SAP BW versions. and 7. This section discusses how to connect to SAP BW servers in the following environments: • • Connecting to SAP BW servers on Windows Connecting to SAP BW servers on UNIX and Linux © 2007 MicroStrategy.1.Project Design Guide Connecting to OLAP Cube Sources B Analysis Services 2005 ---> XMLA ---> member property property MicroStrategy attribute form • Analysis Services 2005: member property Attributes can be related as member properties when defining the levels of a dimension. Inc. MicroStrategy can also use SAP BW as a data source to conduct enterprise reporting and analysis. see the MicroStrategy readme. Member properties are returned in the XMLA property schema rowset. the Customer attribute may have the forms First Name and Last Name.

You can use the following URL to download the Java Connector: https://service. In 328 Connecting to SAP BW servers © 2007 MicroStrategy.dll Locate the Path environment variable from your machine’s System Properties dialog (right-click on My Computer and select Properties).” Depending on your system and SAP BW setup. on the Advanced tab. For more information.dll Sapjcorfc. you may have to perform some extra configuration and troubleshooting steps to connect to SAP BW servers.1. 3 Place the following SAP Java Connector files in any directory that is referenced in the Path environment variable: • • Librfc32.11.B Connecting to OLAP Cube Sources Project Design Guide Connecting to SAP BW servers on Windows Important note from SAP: “Starting with JCo 2. you are required to install the new Visual Studio .3 and also supports more recent versions. refer to the Tech Note TN5800-800-0559.4 and JCo 2. select Environment Variables.1.com/~form/sapnet?_SHOR TKEY=01100035870000463649 MicroStrategy certifies version 2. Take the following steps to connect to SAP BW servers in Windows.NET C/C++ run-time libraries on Windows platforms. . 2 Install the SAP Java Connector.0. To connect to SAP BW servers on Windows 1 Open the SAP Service Marketplace and download the SAP Java Connector. See SAP Note 684106 for details on how to install them. Inc.sap.

© 2007 MicroStrategy. Verify that the directory is included in the value for the Path variable. The Database Instance editor opens. 6 From the folder list. select Database Instance Manager.Project Design Guide Connecting to OLAP Cube Sources B the list of System Variables. SAP Router String if you use an SAP Router. Connecting to SAP BW servers 329 . and then Database Instance from the File menu. as shown below. select a database connection or create a new database connection that provides the following information as required: • • • • Application Server is the name of the SAP BW Server or IP address. open a project source and expand Administration from the folder list. System Number from the SAP BW system. For example. C:\Program files\Common files\MicroStrategy. 4 Place the Sapjco. 8 Create a database instance with SAP BW as the database connection type. Inc.jar in the Common Files MicroStrategy folder. To specify database connection parameters 9 For the database instance. Client Number from the SAP BW system. 7 Select New. locate Path. To create a database instance for your SAP BW connection 5 In Desktop.

Note the following: • • You can get the above information from your SAP Logon. Depending on your system and SAP BW setup. refer to the MicroStrategy Tech Note TN5300-802-0734. For more detailed steps on creating a database instance and related components to connect to SAP BW. you may have to perform some extra configuration and troubleshooting steps to connect to SAP BW servers. For example. Inc.com/~form/sapnet?_SHOR TKEY=01100035870000463649 330 Connecting to SAP BW servers © 2007 MicroStrategy.B Connecting to OLAP Cube Sources Project Design Guide • Language is the language code provided by your SAP administrator. . For more information. To connect to SAP BW servers on UNIX/Linux 1 Open the SAP Service Marketplace and download the SAP Java Connector. For more information. refer to the MicroStrategy online help. refer to the MicroStrategy Desktop online help.sap. You can use either the Database Instances Editor or the Database Instance Wizard to create a database instance for SAP BW. To specify a database login 10 Create a database login with the user and password to use to connect to SAP BW. EN is the language code for English. You can use the following URL to download the Java Connector: https://service. Connecting to SAP BW servers on UNIX and Linux Take the following steps to connect to SAP BW servers in UNIX.

sh by doing the following: • Add the Write and Execute privileges to this file.Project Design Guide Connecting to OLAP Cube Sources B • MicroStrategy certifies version 2.1. /opt/var/MicroStrategy/SAP.jar Linux librfccm. then xxxx_append_path LD_LIBRARY_PATH "${XXXX_SAP_LIBRARY_PATH:?}" export LD_LIBRARY_PATH fi • © 2007 MicroStrategy.sh file in the MicroStrategy installation directory [INSTALL_PATH]/env/SAP. copy them onto your machine. Inc. use the command gunzip [file name] or gzip [file name].so sapjco.so sapjco.sh” in the UNIX/Linux console. AIX librfccm. for AIX: # # set up the environment for SAP # XXXX_SAP_LIBRARY_PATH='/opt/var/MicroStr ategy/SAP' if [ -n "${XXXX_SAP_LIBRARY_PATH}" ]. 3 Search for the files listed in the following table. You can type the command “chmod+wx SAP.so sapjco. For example. and create a new directory for them.o libsapjcorfc.jar 4 Edit the SAP. Open the SAP. For example. This information indicates where the server needs to point to use the downloaded files.3 and also supports more recent versions.so libsapjcorfc. 2 Select the zip file for the platform you want to use and unzip it.sh file and enter the information for XXXX_SAP_LIBRARY_PATH=’’.so libsapjcorfc. Connecting to SAP BW servers 331 .jar SUN librfccm. For example. The default is Read Only.

The Database Instance editor opens. select Database Instance Manager. 6 Restart the server to get the latest updates.B Connecting to OLAP Cube Sources Project Design Guide For example. To create a database instance for your SAP BW connection 7 In Desktop (available only in Windows). then xxxx_append_path LIBPATH "${XXXX_SAP_LIBRARY_PATH:?}" export LIBPATH fi • Save the file. open a project source and expand Administration from the folder list. 332 Connecting to SAP BW servers © 2007 MicroStrategy. 5 Add sapjco. Make sure you have Write privilege to this directory.jar to the installation directory. for Solaris: # # set up the environment for SAP # XXXX_SAP_LIBRARY_PATH='/opt/var/MicroStr ategy/SAP’ if [ -n "${XXXX_SAP_LIBRARY_PATH}" ]. 8 From the folder list. and then Database Instance from the File menu. 9 Select New. /install/jar. Inc. .

© 2007 MicroStrategy. For more information. To specify database connection parameters 11 For the database instance. if you use an SAP Router System Number from the SAP BW system Client Number from the SAP BW system Language: the language code provided by your SAP administrator. EN for English Note the following: • • You can get the above information from your SAP Logon. as shown below. refer to the MicroStrategy Desktop online help. You can also refer to Tech Note TN5300-802-0734 for more information on setting up SAP BW with Intelligence Server Universal. select a database connection or create a new database connection that provides the following information as required: • • • • • Application Server: name of the SAP BW Server or IP address SAP Router String. You can use either the Database Instances Editor or the Database Instance Wizard to create a database instance for SAP BW. for example.Project Design Guide Connecting to OLAP Cube Sources B 10 Create a database instance with SAP BW as the database connection type. Connecting to SAP BW servers 333 . Inc.

You can think of XMLA as a Web Service that supports metadata and data queries against an OLAP Cube source. refer to the MicroStrategy online help. MicroStrategy can also use Essbase as a data source to conduct enterprise reporting and analysis. For more detailed steps on creating a database instance and related components to connect to SAP BW. This section discusses how to connect to Essbase servers in the Windows or UNIX/Linux environment. Configuring the XMLA Provider The material in this section assumes familiarity with the XMLA 1. Connecting to Essbase servers In addition to relational databases. The Execute request queries cube data and results are returned in an ExecuteResponse message. A Discover request supports queries to metadata and the results are packaged in a DiscoverResponse message. Before creating any reports using the Essbase data. 334 Connecting to Essbase servers © 2007 MicroStrategy.xmla.B Connecting to OLAP Cube Sources Project Design Guide To specify a database login 12 Create a database login with the user and password to use to connect to SAP BW. Inc. and the configuration of the XMLA provider for each of these products. you need to establish a connection to the Essbase servers.1 specification found at www. You can perform a test of the XMLA connection to your OLAP cube servers completely separate of any MicroStrategy dependencies with the XMLA Connectivity Test Tool provided with your MicroStrategy installation.org. For information on how to use the XMLA Connectivity Test Tool. . refer to MicroStrategy Tech Note TN1100-000-0635.

The web application server may be installed on a different machine from the Essbase server. For information on installation procedures. The Hyperion XMLA provider supports BEA WebLogic 6.Project Design Guide Connecting to OLAP Cube Sources B Make sure the XMLA 1. • • • • Creating a database instance Perform the following steps to connect to Hyperion Essbase servers.1 on the application server machine to verify that access is available to the Essbase server via the Service Console. Install Hyperion Enterprise Deployment Services 7.1 and Apache Tomcat. © 2007 MicroStrategy. refer to your 3rd-party documentation. see MicroStrategy Tech Note TN5300-802-0794.1 provider is correctly deployed and security settings are configured correctly. Inc. Connecting to Essbase servers 335 . You should receive a confirmation from the provider that includes a display of currently configured properties. Information for correctly installing the XMLA provider can be found in the 3rd-party documentation for Hyperion’s Enterprise Deployment Services product. Note the following: • For the latest information on the 3rd-party connection prerequisites given below. The application server that hosts the Hyperion XMLA provider must enable anonymous access to the XMLA application. You can verify it is working by connecting to the provider URL from your browser. The Hyperion XMLA Provider must be installed and configured on a compatible web application server. Consult your 3rd-party documentation for further details on system requirements and the latest updates.

B Connecting to OLAP Cube Sources Project Design Guide To create a database instance for Essbase 1 From the Desktop Folder List. 4 Create a database instance with Hyperion Essbase as the database connection type. 3 From the File menu. You can also use the IP address as the fully-qualified-machinename.domain. The Database Instance editor opens. and then Database Instance. . For Essbase the URL is most likely case sensitive. http://fully-qualified-machinename:8080/ xmla/EssbaseXmlForAnalysis.company. 2 Expand Administration from the Folder List and select Database Instance Manager. For example. select New. • DSI: The DataSourceInfo (DSI) value is of the form: 336 Connecting to Essbase servers © 2007 MicroStrategy.com. as shown below. Inc. The fully-qualified-machinename is usually of the form machine. select a database connection or create a new database connection that provides the following information as required: • URL: This is the URL of the XMLA Provider that was configured for HTTP access. To specify database connection parameters 5 For the database instance. connect to a project source.

Note the following: • Before connecting to your Analysis Services 2000 servers. MicroStrategy can also use Analysis Services 2000 as a data source to conduct enterprise reporting and analysis. You can perform a test of the XMLA connection to your OLAP cube servers completely separate of any MicroStrategy dependencies with the XMLA 337 • © 2007 MicroStrategy. Connecting to Analysis Services 2000 servers In addition to relational databases. A cube in XMLA is a database in Essbase. • Catalog: The Essbase Catalog value is the Essbase Application containing the database you want to work with in MicroStrategy. Inc. Before creating any reports using the Analysis Services 2000 data. Connecting to Analysis Services 2000 servers .Project Design Guide Connecting to OLAP Cube Sources B Provider=Essbase. refer to the MicroStrategy online help. For more detailed steps on creating a database instance and related components to connect to Analysis Services. you need to establish a connection to the Analysis Services 2000 servers. To specify a database login 6 Create a database login with the user and password to use to connect to the Web service hosting the Essbase XML Provider. you should check that you meet all of the requirements listed in the tech note TN5200-802-0540.Data source=<machine name> The value is split between the DSI setting and an additional connection string parameters setting. Use the Essbase Administration Console to view the applications and databases available on the server. This section discusses how to connect to Analysis Services 2000 servers in the Windows or UNIX/Linux environment.

You should receive an XML response indicating that the site is available as an XMLA provider. Creating a database instance for Analysis Services 2000 1 In Desktop. select Database Instance Manager.1 specification found at www. Information for correctly installing the XMLA provider can be found in your Microsoft documentation.org. open a project source and expand Administration from the folder list.1 provider is correctly deployed and security settings are configured correctly. The Execute request queries cube data and results are returned in an ExecuteResponse message. 338 Connecting to Analysis Services 2000 servers © 2007 MicroStrategy. You can think of XMLA as a Web service that supports metadata and data queries against an OLAP Cube source.B Connecting to OLAP Cube Sources Project Design Guide Connectivity Test Tool provided with your MicroStrategy installation. You can verify Analysis Services 2000 is working by connecting to the provider URL from your browser. . 2 From the folder list. Make sure the XMLA 1. Creating a database instance Perform the following steps to connect to Microsoft Analysis Services 2000 servers.xmla. Inc. and the configuration of the XMLA provider for each of these products. Configuring the XMLA Provider The material in this section assumes familiarity with the XMLA 1. A Discover request supports queries to metadata and the results are packaged in a DiscoverResponse message. For information on how to use the XMLA Connectivity Test Tool. refer to MicroStrategy Tech Note TN1100-000-0635.

Catalog: Use Microsoft’s Analysis Manager to view the Analysis Server containing the cubes you want to work with in MicroStrategy.domain. select New. and then Database Instance. To specify database connection parameters 5 For the database instance. The Database Instance Editor opens. select a database connection or create a new database connection that provides the following information as required: • URL: This is the URL of the XMLA Provider that was configured for HTTP access. the URL is not case-sensitive. For Analysis Services XMLA running on IIS. For example. The database that contains the cube becomes the catalog for XMLA.com. Inc. • DSI: With Analysis Services 2000 the DataSourceInfo (DSI) value is the configuration setting for your data source labeled as DataSourceName in the datasources. You can also use the IP address as the fully-qualified-machinename. 4 Create a database instance with Microsoft Analysis Services as the database connection type. • © 2007 MicroStrategy. http://fully-qualified-machinename/xmla/ msxisapi.company.Project Design Guide Connecting to OLAP Cube Sources B 3 From the File menu.dll The fully-qualified-machinename is usually of the form machine.xml file. as shown below. Connecting to Analysis Services 2000 servers 339 .

This section discusses how to connect to Analysis Services 2005 servers in the Windows or UNIX/Linux environment. . • 340 Connecting to Analysis Services 2005 servers © 2007 MicroStrategy. Connecting to Analysis Services 2005 servers In addition to relational databases. For more detailed steps on creating a database instance and related components to connect to Analysis Services. you should check that you meet all of the requirements listed in the tech note TN5200-802-0542. MicroStrategy can also use Analysis Services 2005 as a data source to conduct enterprise reporting and analysis.B Connecting to OLAP Cube Sources Project Design Guide To specify a database login 6 Create a database login with the user and password to use to connect to Analysis Services. refer to the tech note TN5300-802-0755. refer to the MicroStrategy online help. Inc. refer to MicroStrategy Tech Note TN1100-000-0635. You can perform a test of the XMLA connection to your OLAP cube servers completely separate of any MicroStrategy dependencies with the XMLA Connectivity Test Tool provided with your MicroStrategy installation. you need to establish a connection to the Analysis Services 2005 servers. For information on how to use the XMLA Connectivity Test Tool. For information on setting up authentication for Intelligence Server with Analysis Services. Before creating any reports using the Analysis Services 2005 data. Note the following: • Before connecting to your Analysis Services 2005 servers.

You can think of XMLA as a Web Service that supports metadata and data queries against an OLAP Cube source. open a project source and expand Administration from the folder list. © 2007 MicroStrategy. Creating a database instance Perform the following steps to connect to Microsoft Analysis Services 2005 servers. Information for correctly installing the XMLA provider can be found in your Microsoft documentation. and then Database Instance. Creating a database instance for Analysis Services 2005 1 In Desktop. 2 From the folder list. Inc. The Execute request queries cube data and results are returned in an ExecuteResponse message. by default.xmla.1 specification found at www. A Discover request supports queries to metadata and the results are packaged in a DiscoverResponse message. which includes configuring security settings. The Database Instance Editor opens. and the configuration of the XMLA provider for each of these products. 3 From the File menu. select Database Instance Manager.Project Design Guide Connecting to OLAP Cube Sources B Configuring the XMLA Provider The material in this section assumes familiarity with the XMLA 1. select New. XMLA is the native access method for Analysis Services 2005.org. Connecting to Analysis Services 2005 servers 341 . Follow Microsoft documentation to make sure that the XMLA provider is correctly configured for HTTP access. However. only the TCP/IP transport is configured.

com.B Connecting to OLAP Cube Sources Project Design Guide 4 Create a database instance with Microsoft Analysis Services as the database connection type. For Analysis Services 2005 XMLA running on IIS. the DSI entry can be left blank. • DSI: For Analysis Services 2005. each URL will be configured to support only one data source. To specify database connection parameters 5 For the database instance. Inc. Unlike Analysis Services 2000. as shown below. You can also use the IP address as the fully-qualified-machinename. Catalog: Use Microsoft’s SQL Server Management Studio to view the Analysis Server which contains the cubes to work with in MicroStrategy. For example.dll The fully-qualified-machinename is usually of the form machine. 342 Connecting to Analysis Services 2005 servers © 2007 MicroStrategy.domain. . the URL is not case sensitive. select a database connection or create a new database connection that provides the following information as required: • URL: This is the URL of the XMLA Provider that was configured for HTTP access. http://fully-qualified-machinename/xmla/ msmdpump. The database that contains the cube becomes the catalog for XMLA. • To specify a database login 6 Create a database login with the user and password to use to connect to Analysis Services.company.

Inc. you can start working with the OLAP cube data in MicroStrategy. see Mapping OLAP cubes.Project Design Guide Connecting to OLAP Cube Sources B For information on setting up authentication for Intelligence Server with Analysis Services. For information on setting OLAP cube schema loading options for an OLAP cube source database instance. Like the Warehouse Catalog. the OLAP Cube Catalog can be accessed from the Schema menu on Desktop. where you can import OLAP cubes and remap the OLAP cubes before you create any OLAP cube reports. see one of the following sections: • – Connecting to SAP BW servers. page 337 © 2007 MicroStrategy. For more detailed steps on creating a database instance and related components to connect to Analysis Services. The OLAP Cube Catalog is available only after an OLAP cube source database instance has been created. Integrating OLAP cubes into MicroStrategy 343 . Configuring and Connecting to Intelligence Server of the MicroStrategy Installation and Configuration Guide. you can remap an OLAP cube to MicroStrategy objects and create metrics within an OLAP cube with the OLAP Cube Editor. refer to Chapter 5. page 359. page 349 and Creating metrics from OLAP cube data with MDX and compound metric techniques. refer to the tech note TN5300-802-0755. The best place to start is with the OLAP Cube Catalog. Integrating OLAP cubes into MicroStrategy Once you understand the relationships among the objects in an OLAP cube source and MicroStrategy and connect to your OLAP cube source. For more information. To learn how to create a database instance for an OLAP cube source. Note the following: • Once an OLAP cube is imported. page 327 – Connecting to Analysis Services 2000 servers. refer to the MicroStrategy online help.

Configuring and Connecting to Intelligence Server of the MicroStrategy Installation and Configuration Guide. Using the plus (+) or minus (-) sign next to a catalog name. refer to Chapter 5. page 340 – Connecting to Essbase servers. OLAP cubes can be imported into a MicroStrategy project only by an architect with the “Import OLAP cube” privilege. all the OLAP cubes are displayed. When you open the OLAP Cube Catalog. page 334 This section discusses how you can use the OLAP Cube Catalog to bring the OLAP cube data into a MicroStrategy project and what functions you can perform once the data is brought into MicroStrategy. . under their respective catalog names in the Available Cubes pane. you can expand or hide the cubes contained in this catalog. Inc. by default. For details on how to use the OLAP Cube Catalog. Importing OLAP cubes OLAP cube importing is performed on the Cube Selection tab. For information on setting OLAP cube schema loading options for an OLAP cube source database instance. SAP BW is used as the OLAP cube source but the procedure is similar for Analysis Services and Essbase.B Connecting to OLAP Cube Sources Project Design Guide – Connecting to Analysis Services 2005 servers. 344 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. You can choose to load the schema for imported OLAP cubes when Intelligence Server starts or during OLAP cube report execution. as shown in the image below. refer to the MicroStrategy Desktop online help (search for “OLAP Cube Catalog”).

Project Design Guide Connecting to OLAP Cube Sources B A catalog is marked with an icon showing a folder containing a cube. To import OLAP cubes 1 In Desktop. © 2007 MicroStrategy. If you create new cubes in Analysis Services and the cubes are not being displayed in the OLAP Cube Catalog. 2 From the Schema menu. and a query cube is marked with a cube icon in green. select OLAP Cube Catalog. log in to a project that is connected to an OLAP cube source. an InfoCube is marked with a cube icon in blue. Inc. you may have to modify some permissions in Analysis Services. Integrating OLAP cubes into MicroStrategy 345 . see MicroStrategy Tech Note TN4100-802-1879. For details on how to make Analysis Services cubes available for import in the OLAP Cube Catalog.

select the OLAP cube to import. and select an OLAP cube source database instance to connect to. click OK. click the single arrow (>). you can build reports that access the imported OLAP cubes. 4 From the Catalog drop-down list. Once you select a valid OLAP cube source database instance. Inc. a Database Instance dialog box opens. • 3 Select the Cube Selection tab.) Once the data is mapped to MicroStrategy objects. create. You can edit. click the double arrows (>>). you can use the OLAP Cube Catalog to map the OLAP cube data to MicroStrategy objects (see Mapping OLAP cubes. the imported OLAP cubes are displayed in the Selected Cubes pane on the right. page 349. If you have multiple OLAP cube source database instances created for the project. Select Find from the Edit menu or click the Find icon on the toolbar to open the Find dialog box to search for a specific OLAP cube that you want to import. 5 Click the plus (+) sign to expand the catalog folder and display the OLAP cubes in the Available Cubes pane on the left.B Connecting to OLAP Cube Sources Project Design Guide • If you have a single OLAP cube source database instance created for the project. The catalog contains all the OLAP cubes associated with it. After importing OLAP cubes. using this dialog box. and the OLAP Cube Catalog opens. To import all OLAP cubes. . You can also select All to display the OLAP cubes for all catalogs. 7 Once imported. 346 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. 8 Click Save to save your progress. the OLAP Cube Catalog opens. 6 Use one of the following methods to import the OLAP cubes: • • To import the selected OLAP cubes.

and select Remove [cube name]. Once the first OLAP cube for an OLAP cube source is imported into MicroStrategy. For example. Importing OLAP cubes during report creation When you create an OLAP cube report. Using the right-mouse click. This dialog box can also be used by an architect with the “Import OLAP cubes” privilege to import cubes by using the Retrieve cubes option. This option is available only after a database © 2007 MicroStrategy. you can right-click any OLAP cube in the Selected Cubes pane.Project Design Guide Connecting to OLAP Cube Sources B To remove an OLAP cube. you choose OLAP cubes for your report from the Select Cube dialog box. you can also select the Update Structure option to synchronize with the updated definition of cube structures in the OLAP cube source. a Data Explorer for that OLAP cube source is added to the MicroStrategy project. Inc. under the associated MicroStrategy project. You can find the Data Explorer in the Folder List of Desktop. when a new characteristic or key figure has been added to the InfoCube in SAP BW you can use the Update Structure option to update the MicroStrategy OLAP cube to include these modifications. Integrating OLAP cubes into MicroStrategy 347 .

where you can search for a specific cube for your report by the cube’s name. Inc. A managed object is just like a normal object except that it is created by the system and is stored in a special system folder that is hidden from users. see the related sections above on connecting to the different OLAP cube sources. refer to the MicroStrategy Desktop online help. Managed objects When an OLAP cube is imported into a project. managed objects (attributes. columns. and so on) are created to describe the OLAP cube. For detailed information. and then select the Display Managed Objects option so that managed objects are displayed in the 348 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. In the Search for Objects dialog box. You can click Find at the bottom of this dialog box to open the Find dialog box. . metrics. tables.B Connecting to OLAP Cube Sources Project Design Guide instance has been defined. one way to access managed objects is by using the Search for Objects function from the Tools menu on Desktop. For details. from the Tools menu select Options. However.

the architect can then define a logical and physical model in the MicroStrategy metadata. a MicroStrategy OLAP cube is created that maps to the definition of the source cube in the OLAP cube source. In the context of OLAP cube sources. To do this. By default. much of the process centers on identifying logical entities. you can perform the same mapping tasks available in the Cube Mapping tab of the OLAP Cube Catalog by editing the OLAP cube with the OLAP Cube Editor. as described in Importing OLAP cubes. contains all the metadata information necessary to define a logical model and physical model. Inc. Integrating OLAP cubes into MicroStrategy 349 . such as attributes and facts. right-click an OLAP cube in Desktop and select Edit. they © 2007 MicroStrategy. and hierarchies that reflect the data and levels of the imported OLAP cube. Although these objects. as the architect. Once the managed objects are listed in the search result. After you have imported an OLAP cube. an architect might identify that the key for the Customer attribute exists in the table LU_CUSTOMER. that exist in physical tables. Mapping OLAP cubes When an architect defines a project. you can simply select a cube by using the OLAP Cube Catalog or Select Cube dialog box. For more information on removing a database instance and its related managed objects. Once the logical entities are identified. Intelligence Server creates new attributes. referred to as managed objects. you can rename or edit any of them by right-clicking its name. A managed object can be removed once it is no longer referenced by another object in the project. When an OLAP cube is imported into MicroStrategy. page 344. an OLAP cube. When you.Project Design Guide Connecting to OLAP Cube Sources B search result. are new and are part of the project. see the Managing Your Applications chapter of the MicroStrategy System Administration Guide. For example. need to add an OLAP cube to a project in MicroStrategy. metrics. instead of a single table. The removal of unused managed objects is usually performed by an administrator. This model is referenced by the SQL Engine to generate SQL at run time. such as SAP BW.

a new managed object named Year has no relation to the Year attribute in the Tutorial project connected to the data warehouse. 350 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. see Why do you need to remap OLAP cubes?.B Connecting to OLAP Cube Sources Project Design Guide are not related to the project’s schema and schema objects (see Managed objects above. For more information on the benefits of remapping OLAP cube data to project attributes. In addition. This allows data to be joined across sources in Report Services documents. it can be used to build reports and documents in MicroStrategy. page 356. For more information on managed objects in OLAP cube reports. see the Managing Your Applications chapter of the MicroStrategy System Administration Guide. see the Reporting on External Data Sources: OLAP Cube Reports chapter of the MicroStrategy Advanced Reporting Guide. Inc.) For example. which ensures that a consistent logical model is maintained. For steps on how to perform these schema cleanup tasks. Remapping OLAP cube data to existing attributes can also facilitate the use of MicroStrategy features such as security filters. you can remove the OLAP cube source database instance and all of its associated managed objects. . If you decide to discontinue the use of OLAP cube reports. you can remap OLAP cube data to existing attributes in a MicroStrategy project rather than new managed objects. Once an OLAP cube is mapped. A new schema is created for each OLAP cube source database instance used in a MicroStrategy project.

and attributes are represented by a green symbol with two side-by-side rectangles. the characteristic (dimension) is located at the very top with a green chart and box symbol. you can use the plus (+) sign next to the attribute levels to display the attribute forms. • In the Physical View column. you can map attribute forms for each attribute contained in the imported cube. © 2007 MicroStrategy. with the same symbols for hierarchies and attributes as in standard reports. For SAP BW. As shown in the image above: • The Physical View in the left-hand column represents the cube structure in the OLAP Cube Source.Project Design Guide Connecting to OLAP Cube Sources B Using the Cube Mapping feature in the OLAP Cube Catalog shown below. Integrating OLAP cubes into MicroStrategy 351 . Inc. hierarchy is below the dimension with a green stacked boxes symbol. only the ID and DESC forms are automatically mapped for each attribute. By default. The Logical View in the right-hand column represents the equivalent structure in MicroStrategy.

The Show Technical Names option applies to SAP BW OLAP cubes only. Rename the attribute or metric so it has a different name in the MicroStrategy project from the name of the characteristic or key figure it is mapped to in SAP BW. you can perform the following manipulations by right-clicking the name in the Logical view column: • Edit the attribute or metric. • • • For variables. and Description in SAP BW. Check the Properties of the characteristic or key figure. MicroStrategy retrieves the column data type through MDX. note that when you select Edit. refer to Supporting SAP BW variables. This can be the case even with ID columns of data that are of a 352 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. However. the Prompt Generation Wizard is displayed. In the case of OLAP cube data that is mapped to attributes. Use the Display All Columns icon on the toolbar to show additional attribute forms in the Physical View column and then map each one to an attribute form in the Logical View pane. An ID form must be mapped for each attribute. page 308. For MicroStrategy attributes and metrics. you can view the information on its Name. the columns are often returned as a string of characters. This is because variables in SAP BW are represented as prompts in MicroStrategy. Map the characteristic or key figure to an existing attribute or metric in the MicroStrategy project. . For more information. In the Properties dialog box. Technical Name. you can also perform the above-mentioned manipulations. only the ID and DESC forms are displayed. Manually setting column data types for OLAP cube data When OLAP cube data is mapped to MicroStrategy objects.B Connecting to OLAP Cube Sources Project Design Guide By default. This option opens the Attribute Editor to edit attributes and the Metric Editor to edit metrics. You can also use the Show Technical Names icon on the toolbar to display the SAP BW terms for each attribute and its attribute forms. Inc.

0 you can manually select the column data type that is applied to a column of OLAP cube data mapped to an attribute. Returning data such as ID columns of attributes as strings can make it impossible to group attributes with common data as the same attribute in Report Services documents. you can then include the two OLAP cube reports as datasets of a Report Services document and group the two Product attributes.Project Design Guide Connecting to OLAP Cube Sources B numeric type such as integer. The following procedure uses the OLAP Cube Catalog. you have OLAP cube data that is mapped to a Product attribute in MicroStrategy. This allows the OLAP cube data to be correctly represented in MicroStrategy and facilitates the grouping of related attributes as the same attribute in a Report Services document. You can do this same mapping for another OLAP cube and create reports including the Product attribute. Integrating OLAP cubes into MicroStrategy 353 . but you know that its associated OLAP cube column is of type integer. For example. You can perform this task during the initial import and mapping procedure for an OLAP cube with the OLAP Cube Catalog. but the same steps apply for the OLAP Cube Editor. starting with the step to expand data in the Physical view column. or as a later modification with the OLAP Cube Editor. © 2007 MicroStrategy. Inc.1. Starting in MicroStrategy 8. You can access the OLAP Cube Editor by right-clicking an imported OLAP cube and selecting Edit. To manually set column data types for OLAP cube data You manually set column data types for OLAP cube data when you are mapping OLAP cube data to MicroStrategy objects. By setting the Product ID attribute form to read the OLAP cube data as an integer. OLAP cube data that is mapped to MicroStrategy metrics is automatically converted to a numeric data type and thus does not need its column data type to be manually set. The ID attribute form for Product is returned as a string.

4 Select the Cube Mapping tab. select the OLAP cube source database instance you want to connect to and click OK. 7 Right-click the OLAP cube column data and select Data Type. 6 In the Physical view column. For information on connecting to an OLAP cube source. expand the OLAP cube data until you find the OLAP cube column data for which to manually set the data type. see one of the following sections depending on your OLAP cube source: • • • • Connecting to SAP BW servers. From the Select the Database Instance drop-down list. The Column Editor — Definition dialog box opens. 5 From the Catalog\Cube drop-down list. select the OLAP cube you want to map to MicroStrategy objects. page 340 2 From the Schema menu. . The Cube Mapping tab opens. the OLAP Cube Catalog: Cube Selection tab opens. page 334 Connecting to Analysis Services 2000 servers. 3 Move all OLAP cubes you want to import from the Available Cubes pane to the Selected Cubes pane by using the > button. Inc. If the project connects to more than one OLAP cube source the Database Instance dialog box opens. • • If the project connects to only one OLAP cube source. 8 Clear the Use default from source check box.B Connecting to OLAP Cube Sources Project Design Guide 1 Log in to a project that is connected to an OLAP cube source. page 327 Connecting to Essbase servers. page 337 Connecting to Analysis Services 2005 servers. The OLAP cube data is displayed in the pane below. 354 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. The OLAP Cube Catalog: Cube Selection tab opens. select OLAP Cube Catalog.

and Item each branch would descend to a particular item. Subcategory. and Item are displayed on the report there is an empty cell for the Subcategory of Item number 22. and Month one branch might only have data down to the Quarter level. However. precision. and Item but Item number 22 does not have a Subcategory associated with it. 10 Depending on the data type selected. a Product hierarchy may contain the levels Category. unbalanced. Inc. Integrating OLAP cubes into MicroStrategy 355 . For example. all hierarchies of an OLAP cube are treated as balanced hierarchies. • • • © 2007 MicroStrategy. in a Product hierarchy that includes Category. Unbalanced and ragged hierarchies include at least one branch that does not descend to the lowest level and one branch that includes a skipped level. specify the byte length. select which data type to map the OLAP cube data as. Quarter. When Category. if you know that the structure of a hierarchy is unbalanced or ragged you must set the hierarchy’s properties to reflect its structure. and scale for the data type. Subcategory. 12 Click Save and Close to save your changes to the OLAP cube and exit the OLAP Cube Catalog. in a Time hierarchy that includes Year. Unbalanced hierarchies have at least one branch that does not descend to the lowest level. For example. and ragged are used to describe the different set of characteristics of hierarchical sets of data. 11 Click OK to save your changes and return to the OLAP Cube Catalog. For example. Unbalanced and ragged hierarchies By default. Ragged hierarchies have at least one branch that includes a member whose logical parent is not the level above that member. Subcategory.Project Design Guide Connecting to OLAP Cube Sources B 9 From the Data type drop-down list. The terms balanced. • Balanced hierarchies have an equal number of levels in each branch of the hierarchy.

B Connecting to OLAP Cube Sources Project Design Guide The steps below are necessary for any unbalanced or ragged hierarchy to prevent inaccurate results when applying certain types of filters. select the check box This hierarchy is unbalanced or ragged and then click OK. . The Properties dialog box is displayed. Set a hierarchy as unbalanced or ragged 1 In the OLAP Cube Catalog. refer to the MicroStrategy Desktop online help (search for the “Mapping OLAP cubes” topic). Inc. This modification also allows you to perform date qualifications on the mapped MDX property data. and hierarchies you may want to remap OLAP cube data to existing attributes in the MicroStrategy project for the following reasons: 356 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. Date form support for MDX properties You can support mapping MicroStrategy date forms to MDX property data of the date data type by performing a special modification of a VLDB property. please refer to MicroStrategy Tech Note TN1100-000-0636. metrics. For information on how to support these date forms and qualifications. Why do you need to remap OLAP cubes? Although you can use the automatically generated managed object attributes. The word “(Unbalanced)” will be displayed next to the name of the hierarchy in the Logical View column. For detailed steps on mapping and remapping objects from OLAP cube sources to MicroStrategy objects. 2 On the Hierarchies tab. A hierarchy in the Physical View column is represented with a green stacked boxes symbol. right-click the hierarchy name in the Physical View column and select Properties.

When should you remap cubes? Although you can remap the columns either when an OLAP cube is first imported or later on after you have created a project. For example. MicroStrategy security filters can be applied to attributes in OLAP cube reports. but the nature of the cube is not changed. In the case of attributes. Remapping simply replaces the managed object attributes that are used to represent the OLAP cube’s structure with attributes in an existing MicroStrategy project. thus creating a relation between the two sets of data. three OLAP cubes can share the same managed object metric named Revenue. the security filter on Year is applied. they can be remapped to project attributes that participate in the ROLAP schema. metrics and hierarchies can only be remapped to other managed object metrics and hierarchies that are mapped to OLAP cube source data. This also prevents maintenance issues because reports need to be modified if an OLAP cube is remapped after the report is created. Administrators can search for dependents and manage access control lists (ACLs) for attributes that map both to the data warehouse and an OLAP cube source. For example. © 2007 MicroStrategy. if an OLAP cube report and a standard report both use the Year attribute. However. Integrating OLAP cubes into MicroStrategy 357 . • • • You can remap the levels of an OLAP cube.Project Design Guide Connecting to OLAP Cube Sources B • Report designers can integrate the logical model of the project with the data in the imported OLAP cube. it is recommended that you do the remapping initially so that subsequent users can take advantage of the mapping. Data can be joined across sources within a Report Services document. you can map an OLAP cube level to the Year attribute in your project. If a user with a security filter on Year runs the OLAP cube report that contains Year. then Year can be used to group the data within a document. For example. Inc.

Since this relation is not created. The diagram below shows two logical models. This feature allows you to quickly start creating reports for your OLAP cube data. The one on the left exists in a specific OLAP cube. . Quarter. you can map the attributes within the OLAP cube to existing project attributes. none of the individual attributes are shared. C u b e A ttr ib u te s C u s to m e r R e g io n P r o je c t A ttr ib u te s R e g io n Ye a r C u b e Ye a r Q u a r te r M onth of Ye a r C u s to m e r S ta te C u b e Q u a r te r C a ll C e n te r M onth C ube M o nth C u s to m e r C ity E m p lo ye e Da y Example 2: Partially mapped cube After an OLAP cube source has been included in MicroStrategy as an OLAP cube. Inc. Quarter. also shows two logical models. and Month.B Connecting to OLAP Cube Sources Project Design Guide Example 1: Unmapped cube You can map managed object attributes for your OLAP cubes instead of using project attributes. and Month information for both your 358 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. shown in the diagram below. you cannot join data from these different sources in a Report Services document and you cannot support project security filters in OLAP cube reports. The drawback with this setup is that you cannot create a relation between your OLAP cube data and your project data. you can create a Report Services document that contains Year. The difference between the two examples is that the OLAP cube has been partially remapped so that it shares the attributes Year. and the one on the right exists in a MicroStrategy project. Example 2. With this technique. Although both models have a Time hierarchy.

when a level is remapped. except by using calculated expressions in Report Services documents. and Month are applied to OLAP cube reports that include these mapped attributes. changes to the Time dimension apply to OLAP cubes in the project that contain this dimension. Cu b e A ttrib u te s C usto m e r R e gio n Proje c t A ttrib u te s R e gio n Ye a r Ye a r Q ua rte r M o nt h o f Ye a r C usto m e r S ta te Q ua rte r C a ll C e nte r M o nt h M o nt h C usto m e r C ity Em plo ye e Da y The dimensions of OLAP cubes are always shared. Inc. For information on creating calculated expressions. that change applies to all the OLAP cubes that share that dimension. Metrics created to map to your OLAP cube data are related only to their associated OLAP cube. Metrics created with MDX combine the robust set of MDX functions and expressions with MicroStrategy analytical tools such as prompts. Quarter. Creating metrics from OLAP cube data with MDX and compound metric techniques When you map your OLAP cube data into MicroStrategy.Project Design Guide Connecting to OLAP Cube Sources B data warehouse and OLAP cube sources. Integrating OLAP cubes into MicroStrategy 359 . Therefore. you can take advantage of MDX (MultiDimensional eXpressions) to create advanced metrics. see the Designing Documents chapter of the MicroStrategy Report Services Document Creation Guide. any security filters for Year. Therefore. In this case. In addition. © 2007 MicroStrategy. You can also use basic arithmetic expressions to create these advanced metrics from OLAP cube data. these metrics cannot be directly integrated with data from a separate relational data source.

where Discount is a metric mapped to data in the OLAP cube. You can reference one or more MicroStrategy metrics mapped to OLAP cube data using custom MDX just as you can with a standard arithmetic expression. To use MDX to create your calculated measures you must enclose MDX in double quotes (“”).-. If you do not make the metric a smart metric you can only use basic operators (+. where Revenue and Total Expenses are both metrics.Total Expenses. You can also use prompts in these compound and custom MDX metrics (see Using prompts within OLAP cube metrics. This technique allows you to use MDX functions and flexibility to query and report on your OLAP cube data. you can create your own custom MDX to return data for a metric. For general information on smart metrics. • MDX customization: Rather than relying only on MicroStrategy to create MDX to return data from your OLAP cube source. see the MicroStrategy Basic Reporting Guide. and so on).*. such as Discount * 1. These metrics can also reference multiple MicroStrategy metrics within the OLAP cube with an expression such as Revenue . page 366). to build a Profit metric.B Connecting to OLAP Cube Sources Project Design Guide You can create metrics that map to OLAP cube data using either of the following techniques: • Compound metrics: A compound metric is any MicroStrategy metric with an expression that includes a MicroStrategy metric and an arithmetic expression. For tips and insights on how to build analysis with MDX in MicroStrategy. Once you create metrics using these techniques you can include them in your MicroStrategy reports and report filters in the same ways that you can include any MicroStrategy metric. The metrics created in this way for an OLAP cube are stored in a Compound Metrics folder within the Metrics folder for the OLAP cube. see How to build analysis into metrics with custom MDX. The expression can be as simple as a metric multiplied by a constant value. page 363. You can use MicroStrategy analytical and aggregation functions with metrics mapped to OLAP cube data only if the metric you create is defined as a smart metric.5. 360 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. see the MicroStrategy Advanced Reporting Guide. For examples of smart metrics. Inc./. The MDX you create is passed to your OLAP cube source to be executed and to return the data. .

© 2007 MicroStrategy. 4 Select the Cube Mapping tab. The OLAP Cube Catalog: Cube Selection tab opens. starting with the step to access the Edit menu. After right-clicking an OLAP cube and selecting Edit to access the OLAP Cube Editor. For information on connecting to an OLAP cube source. page 327 Connecting to Essbase servers. Integrating OLAP cubes into MicroStrategy 361 . select the OLAP cube source database instance to connect to and click OK. The following procedure uses the OLAP Cube Catalog. To create a metric from OLAP cube data with MDX and compound metric techniques 1 Log in to a project that is connected to an OLAP cube source. page 340 2 From the Schema menu. select OLAP Cube Catalog. the steps below apply for the OLAP Cube Editor.Project Design Guide Connecting to OLAP Cube Sources B You can create these metrics during the initial importing and mapping procedure of your OLAP cube data with the OLAP Cube Catalog. see one of the following sections. page 334 Connecting to Analysis Services 2000 servers. Inc. 3 Move all the OLAP cubes to import from the Available Cubes pane to the Selected Cubes pane by using the > button. If the project connects to more than one OLAP cube source the Database Instance dialog box opens. depending on your OLAP cube source: • • • • Connecting to SAP BW servers. These metrics can also be created as a later modification to an OLAP cube with the OLAP Cube Editor. • • If the project connects to only one OLAP cube source. the OLAP Cube Catalog: Cube Selection tab opens. From the Select the Database Instance drop-down list. page 337 Connecting to Analysis Services 2005 servers.

page 366. 9 In the Object name text field. while also including any required constants. . enter your custom MDX in the Definition pane of the Metric Editor. For example. Make sure to enclose the entire expression in double quotes. Validating MDX verifies that the entire expression is enclosed in double quotes. you can simply drag and drop metrics from the OLAP cube’s Metrics folder. and MicroStrategy analytical and aggregation functions. 362 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy.5” You cannot validate MDX in the Metric Editor as you can for a standard expression that is not enclosed by double quotes. 10 Click Save to save your metric. select the OLAP cube to map to MicroStrategy objects. 7 Create the expression for your metric: • If you are creating a compound metric. select Add New Compound Metric. You can use MicroStrategy analytical and aggregation functions with metrics mapped to OLAP cube data only if the metric you create is defined as a smart metric.[Discount Amount] * 1. The Metric Editor opens. 8 Click Save and Close. it does not validate the syntax of the expression. enter a name for your metric. if you have Revenue and Cost metrics in your OLAP cube you can create the expression Revenue . Inc. The OLAP cube data is displayed in the pane below. arithmetic operators. The Save As dialog box opens. For example.B Connecting to OLAP Cube Sources Project Design Guide 5 From the Catalog\Cube drop-down list. see Using prompts within OLAP cube metrics. For an example of creating a metric that includes a prompt. 6 From the Edit menu. you can enter the following: “[Measures].Cost to create a Profit metric. • If you are creating a metric using custom MDX.

Integrating OLAP cubes into MicroStrategy 363 . refer to the following MicroStrategy Tech Notes: • • TN5200-81x-2345—How to create customized metric expressions for OLAP cube sources in MicroStrategy 8. • • Basics Creating your own custom MDX allows you to draw further analysis from your OLAP cube source into MicroStrategy. Be aware that MicroStrategy does not validate any custom MDX created by users to build metrics for OLAP cubes.Project Design Guide Connecting to OLAP Cube Sources B 11 Click Save and Close to save your changes to the OLAP cube.1. Inc. MDX syntax and functionality is not described in depth in this section. TN5200-81x-2342—How to write a custom metric formula in MDX to ignore grouping on a cube dimension in MicroStrategy 8. For additional best practices and examples.x Creating such analysis requires appropriate knowledge of both MDX and MicroStrategy. How to build analysis into metrics with custom MDX You can build sophisticated analysis into your OLAP cube metrics by creating your own custom MDX.[Total Sales]” is valid syntax for a metric defined with MDX.1.x TN5200-81x-2344—How to write a custom metric formula in MDX to implement a transformation in MicroStrategy 8. only basic principles of analysis with the use of MDX and MicroStrategy is provided. “[Measures].1.x. To use MDX to create your metrics you must enclose MDX in double quotes (“”).1. For example. This section provides some tips and best practices on how to build analysis into metrics with custom MDX. © 2007 MicroStrategy. This allows you to further combine the analysis capabilities of MDX and MicroStrategy.x TN5200-81x-2343—How to write a custom metric formula in MDX to filter on an attribute in MicroStrategy 8.

For example.[Profit])” This expression returns year-to-date values by quarter for profit data. Conditional metrics Using MDX. you can also display revenue for a certain category such as electronics. Report designers can include these metrics on reports to view multiple perspectives of data on the same report. the function is passed to the OLAP cube source and processed as a pass-through function. the following expression applies a multiplier to the Total Sales data: “[Measures]. . For example.[Total Sales] * . For example. Inc. You can also perform basic arithmetic in your MDX. you can use the MDX year-to-date (YTD) function to create transformation-style analysis on your OLAP cube data. as shown in the report below. along with viewing your total revenue on a report. as shown below: “sum(YTD([Quarter]. you can create conditional metrics in MicroStrategy from your OLAP cube data. [Measures].06” Along with these simple expressions. In 364 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. When you include an MDX function in your custom MDX. A conditional metric allows you to apply a filter to only one metric on a report while not affecting the other metrics.CurrentMember). you can also utilize MDX functions to create more advanced analysis.B Connecting to OLAP Cube Sources Project Design Guide The expression shown above is a simple expression that returns the Total Sales data from an OLAP cube.

[Year]. 2 identifies the electronics category.[2]. For example. a second condition on the year is included by adding another comma and conditional expression: “([Measures].[Revenue]. Using the ApplySimple function.[Revenue]. The example below shows the basic structure of an ApplySimple statement to create metrics with custom MDX. Prompts are objects in MicroStrategy that provide users the ability to dynamically select what data is returned to their report to analyze.[Category].[2])” In the example above.Project Design Guide Connecting to OLAP Cube Sources B the example expression below. you can create the same metric to return electronics revenue for only the year 2006. The values that identify data depend on how you have defined data in your OLAP cube source. In the example expression below. The report shown below uses this metric to compare total revenue with electronics revenue. Inc. © 2007 MicroStrategy.[Category]. meaning they will produce the same MDX every time. bold highlights the part of the expression (including the comma) that applies the condition to the revenue data: “([Measures]. you can include prompts in your MDX to provide dynamic analysis on your OLAP cube data. You can include more than one condition for each metric. [2006])” Prompts All of the MDX examples in the sections above are static expressions. Integrating OLAP cubes into MicroStrategy 365 .

see the Using prompts within OLAP cube metrics section below. . you must use the ApplySimple function to 366 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. This adds flexibility to your queries. You can also use this technique with the conditional metrics techniques described in Conditional metrics. you can allow users to choose what category to view revenue for. ApplySimple(“([Measures]. ?elementlistprompt) For more information on and a procedure for creating metrics in OLAP cubes with prompts.?valueprompt) In the example syntax above.. allowing users to determine the data to see on the report. you can also include MicroStrategy prompts with the metrics.[Total Sales] / #0)” .B Connecting to OLAP Cube Sources Project Design Guide ApplySimple(“MDX expression with placeholders for objects”. For example. rather than always returning the revenue data for electronics. #0 is a placeholder in the MDX expression for the value prompt. you can include an element list prompt on the Category attribute of the OLAP cube as shown below. For metrics created with compound metric techniques without any custom MDX. The syntax for including a prompt as an object to replace a placeholder is ?promptname. ApplySimple(“([Measures]. Inc.objectN) A simple application of this technique is to use a constant value prompt in your project as a multiplier of metric data as shown below.. Using prompts within OLAP cube metrics If you are creating new metrics in your OLAP cube..object1.object0. For metrics created using MDX expressions.[Revenue].. To provide this analysis to users. When the metrics are included on a report and the report is run. the prompts are displayed to the user for completion. page 364.#0)”. you can simply include a prompt in the metric definition.

page 361) until the step to create an expression for the metric. 2 Enter your expression in the Definition pane of the Metric Editor. The following types of prompts can be included with metrics built from custom expressions: • • • Element list prompts defined on an attribute of the associated OLAP cube Value prompts Object prompts defined on objects of the associated OLAP cube To use prompts within OLAP cube metrics 1 Follow the steps in the procedure above (To create a metric from OLAP cube data with MDX and compound metric techniques. Make sure to enclose the entire expression in double quotes. you can enter expressions similar to the following: • ([Discount Amount] * ?constantprompt) This expression applies a special discount amount. © 2007 MicroStrategy.Project Design Guide Connecting to OLAP Cube Sources B include prompts in the metric definition. • ApplySimple(“([Measures]. The Save As dialog box opens. ?CategoryElementPrompt) This expression creates a Revenue metric.#0)”. entered by the user running the report. Users can then choose to view revenue data for different categories such as Books or Music. Inc. For example. Integrating OLAP cubes into MicroStrategy 367 . In this example it is assumed that CategoryElementPrompt is the name of an element list prompt in the project that references a Category attribute within the OLAP cube. which is conditional on an element list prompt answered by the user running the report.[Revenue]. 3 Click Save and Close. In this example it is assumed that constantprompt is the name of a value prompt in the project and Discount Amount is a metric within the OLAP cube.

and the Profit Margin metric is returned. Inc.B Connecting to OLAP Cube Sources Project Design Guide 4 In the Object name text field. If you try to remove the Profit metric. you import an OLAP cube. a list of metrics that are dependent on the metric you are removing is returned. dependencies may need to be resolved before you can remove the metric. This makes the Profit Margin metric dependent on the Profit metric. You must remove all of the metrics and reports which depend on the metric you are trying to remove. 6 Click Save and Close to save your changes to the OLAP cube and exit the OLAP Cube Catalog. enter a name for your metric. you need to also delete those reports or remove the Profit metric from the reports before you can remove the Profit metric from the OLAP cube. When you try to remove a metric with dependent metrics. you must first remove the Profit Margin metric. and you can then remove the metric from the OLAP cube. 5 Click Save to save your metric and return to the OLAP Cube Catalog. . Then you can remove the metric. and its data is automatically mapped to MicroStrategy metrics. If a compound metric of an OLAP cube has been added to any reports. You can remove the compound metric from the report rather than deleting the report. This removes the dependency between the metric and the report. a list of reports that depend on the metric is also returned. Once this metric is created in your OLAP cube. 368 Integrating OLAP cubes into MicroStrategy © 2007 MicroStrategy. If the Profit metric is included on any reports. To remove the Profit metric. a search for dependent objects is automatically triggered. you create a Profit Margin metric that uses the Profit metric you just created. You then create a new compound metric named Profit within the OLAP cube by subtracting the OLAP cube’s cost data from its revenue data. For example. Removing compound metrics from OLAP cubes When you remove metrics based on multiple metrics of an OLAP cube.

369 . with a focus on how you can use the logical view feature to take advantage of the enhanced schema support in MicroStrategy. and logical views. logical views are defined using SQL queries against the data warehouse. logical views are created using the Table Editor. table aliases. Inc. Different from the logical tables. This chapter introduces you to the different types of logical tables.C C. © 2007 MicroStrategy. which point to physical tables in the data warehouse. LOGICAL TABLES Introduction Logical tables represent tables in the data warehouse. While logical tables are set up in a project by using the Warehouse Catalog. There are three types of logical tables in the MicroStrategy environment: logical tables.

Using the Logical Table Editor. based on which attributes. Logical views are created using the Table Editor. These attributes and facts are part of the report definition that the MicroStrategy Engine refers to when a report is executed. A table alias can have a different name from the physical table. using the Warehouse Catalog. There are three types of logical tables: 1 Logical table: is a logical representation of a table that the Engine uses to generate SQL. 370 Logical tables © 2007 MicroStrategy. The logical view is also referenced in the SQL that is generated for the report. Once created. It does not point directly to a physical table and is defined using a SQL query against the warehouse. 3 Logical view: is a logical table that points to a SQL statement instead of directly to a physical table. Inc. logical tables and all the other schema objects are stored in the Schema Objects folder.C Logical Tables Project Design Guide Logical tables Logical tables are MicroStrategy objects that form the foundation of a schema. In the MicroStrategy Tutorial. page 175). logical tables in the MicroStrategy schema consist of attributes and facts. and other schema objects can be defined. 2 Table alias: is an additional logical table that points directly to an existing physical table. facts. the logical view can be used in the same way as the Type 1 logical table. A logical table is created for each physical table that is imported into a project. One physical table can have more than one table aliases. A table alias is created outside of the Warehouse Catalog. Table aliasing is used to create attribute roles (see Attributes that use the same lookup table: Attribute roles. . the whole SQL query is displayed in the place of physical tables as for Type 1 logical tables. you can define your logical view using the SQL statement as well as view the content of all the logical tables and their associated warehouse tables. While physical tables in a data warehouse consist of columns. These physical tables are referenced in the SQL that is generated for the report. This type of logical table maps directly to physical tables in the data warehouse.

To create a table alias. please refer to Attributes that use the same lookup table: Attribute roles. you create multiple logical tables pointing to the same physical table and define those logical tables as the lookup tables for the attributes in different roles. How should I use logical tables? 371 . First. if the Customer table is used to represent both Ship to Customer and Bill to Customer. please refer to the MicroStrategy online help (search for “Warehouse Catalog”). you can create a table alias to resolve the double usage case. When an attribute plays more than one role. Basically. © 2007 MicroStrategy. Inc. page 175. One way to do this is to create explicit table aliases. you can create MicroStrategy schema objects. For example. Logical views are a little different from the above-mentioned logical tables and table aliases for the following reasons: • • • Logical views do not map directly to physical tables in the data warehouse. you need to create an attribute in the logical model for each of the roles. Based on these tables. instead of being imported from a data warehouse or duplicated from existing logical tables. For more information on how to use the Warehouse Catalog. such as attributes and facts. right-click the logical table name and select Create Table Alias. please refer to the MicroStrategy online help (search for “Step-by-step instructions to create a table alias”). then define the new attributes using the appropriate tables. which is accessed from the Schema menu. create a table alias by copying an existing logical table and giving it a new or different name. Logical views are created from scratch. For detailed information on attribute roles.Project Design Guide Logical Tables C How should I use logical tables? The most common logical tables are the ones that are imported into the project from the data warehouse using the Warehouse Catalog. Logical views are defined using SQL queries. For step-by-step instructions.

they can be used in the same way as the regular logical tables (brought into the project using the Warehouse Catalog). There are many common modeling scenarios that are easier to manage with the use of logical views. 372 How should I use logical tables? © 2007 MicroStrategy.C Logical Tables Project Design Guide However. or logical views to the project. . such as the following: • • • • Slowly-changing dimensions Attribute form expressions from multiple tables Consolidated dimension tables Recursive hierarchies For common usage examples. please refer to Logical view examples. The biggest benefit of using logical views is that you can model a MicroStrategy schema that cannot be supported with only the physical database structures in the warehouse. The Update Schema option can be accessed from the Schema menu. table aliases. Whenever you create or add logical tables. page 376. once logical views are created. This means that you can use the logical views to build attributes and facts and that you can also create table aliases for the logical views. you need to update the schema. Inc.

One way to access the Table Editor is to select New from the File menu and choose Logical Table. Object Browser lists all tables and columns that have been imported into the project. Creating logical tables 373 . Creating a Logical View involves a few simple steps that require you to provide your own SQL statement and map the columns in the statement to the correct data types (see the following information). Inc. and table aliases are created by duplicating existing logical tables. Any physical table in the project database instance can be used in the SELECT statement. while the Mapping panel is where you map for the columns returned by the SQL query. © 2007 MicroStrategy. Logical views. on the other hand. please refer to the online help (search for “Creating logical views”). As illustrated in the following image. For detailed instructions. The SQL statement panel is where you type in your SQL query.Project Design Guide Logical Tables C Creating logical tables Most logical tables are brought into the project by using the Warehouse Catalog. Detailed instructions on how to create them are provided in the online help (search for “Tables”). are created in MicroStrategy Desktop using the Table Editor.

Although common table expressions (CTEs) are also supported for some databases.C Logical Tables Project Design Guide To create a logical table in the Table Editor 1 From the File menu. If you used an existing column in the mapping in Step 5. The names of the columns must match exactly the column aliases defined in the SQL statement. these expressions cannot be nested in the SQL because this would result in invalid SQL syntax. Alternatively. you map an existing column to the logical view. Keep in mind that if you change the data type. . Inc. 3 Click Add to map columns returned by the SQL statement. the change will affect all the tables with that column. 2 In the SQL Statement panel. the order of the columns does not have to match the order in which the column aliases appear in the SQL statement. It is recommended that you use derived tables to define logical views because the logical view SQL syntax becomes nested inside SQL statements generated by the Engine. Please check your database for best usage. select New and then Logical Table. you can also drag and drop columns from the Object Browser to the Column Object cell. This creates a new column. By doing this. type in your SQL statement. The Table Editor is displayed with the Physical View tab selected by default. you inherited the data type of that column. However. You can drag and drop columns from the Object Browser to insert into the statement). 5 Select a Data Type for the column by using the drop-down list. 374 Creating logical tables © 2007 MicroStrategy. 4 Type in the column name under Column Object.

Therefore. © 2007 MicroStrategy. however. the logical view is logged instead. Derived tables are advantageous because they are nested in the SQL generated by the Engine. The Engine generates derived table syntax to represent the logical view. For a logical view—which maps to a SQL statement—the Engine inserts the SQL syntax in the FROM clause. you should also understand that the SQL query entered for logical views is not modified in any way by MicroStrategy. In the SQL generated for a report. It is your responsibility to ensure the accuracy and validity of your SQL statements. if applicable. CTEs. Because the MicroStrategy Engine does not parse through the SQL syntax. Using SQL for logical views Since SQL queries are the key to creating logical views. The same holds true if you use a view in the database. please check your database. It is recommended that you use derived tables to define logical views. 8 From the Schema menu. Creating logical tables 375 .Project Design Guide Logical Tables C 6 Modify the Precision and Scale of the column. 7 Save and close the logical table. Inc. logical views are generated as either a derived table or a common table expression (CTE) depending on the type of database that you use. For best usage. In addition. make sure that your RDBMS is optimized to answer the query that you create. the statistics log does not contain any information about the actual physical tables accessed. it inserts the name of the table into the FROM clause. select Update Schema to ensure that the new logical table is loaded into the project. although CTEs are also supported by some databases. When the Engine needs to use a logical table that maps directly to a physical database table. in which case table objects accessed would are not logged either. are not nested in the SQL because this would result in invalid SQL syntax. you should be experienced with using SQL before you use the logical view feature.

C Logical Tables Project Design Guide The results of logical views are not cached. Logical view examples The following business cases are intended to help you understand how you can use the logical view feature in your applications. often two problems arise: • The model cannot support fact tables at the level of attributes that are not keys. and Region. This restriction applies to summary tables as well as to intermediate results that may be generated by the SQL Engine. Lookup_store Store_ID Store_Name Market_ID Market_Name Region_ID Region_Name Level 376 Logical view examples © 2007 MicroStrategy. . the MicroStrategy Engine joins the fact table with one lookup table and does the aggregation. Market. The following is an example lookup table for Store. Usually. when populating pick lists for prompts. thus affecting element browsing requests that display a list of attribute elements. • Too many rows in the dimension table may slow down the SELECT DISTINCT query. you may double count if you have to join to a table where that attribute is part of the key. If there is no distinct list of attribute elements. Business case 1: Distinct attribute lookup table Many star schemas feature a single lookup table that is shared by all the attributes in one dimension (see the following example). Inc. for example. in one-SQL-pass reports. the logical view simply appears as additional syntax in the report SQL generated by MicroStrategy. While it is possible to model a schema with such a dimension table.

Region_ID from Lookup_Store where level=1) a11. Usually. When it is joined with a Market-level fact table (Market_Sales). Market_Name.a11.Market_ID.Market_Desc.Project Design Guide Logical Tables C In this table. Market and Region are not the keys.Sales) From (select Market_ID. you can use the Logical View feature to define another logical table Lookup_Market as follows: Select Market_ID. the case is on Date columns. a11. Therefore. you want to define an attribute based on the Date difference between two Date columns (Ship_Date and Order_Date) in two different tables as follows.Market_ID = a12. a direct join between the fact table and the above lookup table may result in double-counting. SUM(a12. if the requested fact table is at the Market or Region level.Market_ID Group by a11. Inc. Logical view examples 377 . the following report SQL is generated: Select a11. To avoid that.Market_Name Business case 2: Attribute form expression across multiple tables Customers often request the ability to generate an attribute form expression across multiple tables. F_Table1 Ship_Date Order_ID Fact1 © 2007 MicroStrategy.Region_ID From Lookup_store Where level=1 Then use this table as the lookup table for Market. Market_Sales a12 Where a11. Market_Name. For example.Market_ID.

For example.Order_ID. a Type I SCD 378 Logical view examples © 2007 MicroStrategy. Usually.Order_ID The new logical table (logical view) looks like the following table. Indeed. Inc. Fact1. Kimball has further coined different distinctions among ways to handle SCDs in a dimensional model. For example. a company may annually reorganize their sales organization or recast their product hierarchy for each retail season. if dimensional relationships change more frequently. dimensional hierarchies are presented as independent of time. you can use the following SQL query to create a logical table to calculate the Date difference and then define the attribute on that new column: Select Ship_Date-Order_Date Cycle_time. it may be better to model separate dimensions. Logical view Cycle_Time Order_ID Fact1 Fact2 Business case 3: Slowly changing dimensions Slowly changing dimensions (SCDs) are a common characteristic in many business intelligence environments. F_table2 Where F_table1. SCDs are well documented in the data warehousing literature. “Slowly” typically means after several months or even years.Fact2 From F_table1.C Logical Tables Project Design Guide F_Table2 Order_Date Order_ID Fact2 Using the Logical View feature. . F_table1.Order_ID=F_table2. and a new attribute can be defined on the Cycle_Time column. for instance). Ralph Kimball has been particularly influential in describing dimensional modeling techniques for SCDs (see The Data Warehouse Toolkit.

for example. Example 1: Compound key with Effective Date and End Date One way to physically store an SCD is to employ Effective Date and End Date columns that capture the period of time during which each element relationship existed. The discussion below is based on an example sales organization that changes slowly in time as the territories are reorganized.Project Design Guide Logical Tables C presents only the current view of a dimensional relationship. Inc. page 43. © 2007 MicroStrategy. Sales Rep Jones moved from District 37 to District 39 on 1/1/2004. For example. Logical view examples 379 . as-was analysis One of the capabilities available with slowly changing dimensions is the ability to perform either “as-is” analysis or “as-was” analysis: • “As-is” analysis presents a current view of the slowly changing relationships. show me sales by District according to the way Districts were organized at the time the sales transactions occurred. They also provide you an easy way to specify which type of analysis you would like to perform. In the example below. show me sales by District according to the way Districts are organized today. • The techniques described here provide the flexibility to perform either type of analysis. As-is vs. and so forth. For example. sales representatives switch districts in time. a Type II SCD preserves the history of a dimensional relationship. please refer to Lookup tables: Attribute storage. For information on compound keys. and Kelly moved from District 38 to 39 on 7/1/2004. “As-was” analysis presents a historical view of the slowly changing relationships.

LVW_CURRENT_ORG 380 Logical view examples © 2007 MicroStrategy.C Logical Tables Project Design Guide LU_SALES_REP Sales_Rep_ID 1 2 3 4 1 3 Sales_Rep_Name Jones Smith Kelly Madison Jones Kelly District_ID 37 37 38 38 39 39 Eff_Dt 1/1/1900 1/1/1900 1/1/1900 1/1/1900 1/1/2004 7/1/2004 End_Dt 12/31/2003 12/31/2099 6/30/2004 12/31/2099 12/31/2099 12/31/2099 When using this type of dimensional lookup table. FACT_TABLE Sales_Rep_ID 1 2 3 1 2 3 2 3 4 Trans_Dt 9/1/2003 9/10/2003 9/15/2003 3/1/2004 3/10/2004 3/15/2004 9/5/2004 9/15/2004 9/20/2004 Sales 100 200 150 200 250 300 125 275 150 To specify the MicroStrategy schema 1 Create a logical view to represent just the current District-Sales Rep relationships. . such as a transaction date. the fact table must include a date field. Inc.

Inc. LVW_CURRENT_ORG. Trans_Dt 3 Create a table alias LU_CURRENT_DISTRICT for LU_DISTRICT. resulting in a fact view at the District level. The resulting view is an “as-was” or historical view.Sales_Rep_ID) where F. which captures the Sales Rep-District relationships that existed at the time the transactions occurred. 4 Define the following attributes: • Sales Rep: – @ID = sales_rep_id. LVW_CURRENT_ORG – Child: Sales Rep • Historical District: – @ID = district_id. Logical view examples 381 . FACT_TABLE • Current District: – @ID = district_id.Sales_Rep_ID = F. @Desc = district_name – Tables: LU_CURRENT_DISTRICT (lookup).Project Design Guide Logical Tables C select Sales_Rep_ID. @Desc = district_name © 2007 MicroStrategy.Trans_Dt between L. @Desc = sales_rep_name – Tables: LU_SALES_REP (lookup).End_Dt group by District_ID. District_ID from LU_SALES_REP where End_Dt = '12/31/2099' 2 Create another logical view that performs the “as-was” join between the lookup table and fact table. sum(sales) sales from LU_SALES_REP L join FACT_TABLE F on(L.Eff_Dt and L. LVW_HIST_DISTRICT_SALES select District_ID. Trans_Dt.

C Logical Tables Project Design Guide – Tables: LU_DISTRICT (lookup). LVW_HIST_DISTRICT_SALES • Month: – @ID = MONTH_ID – Tables: LU_TIME (lookup) 5 Define the Sales fact: • • Expression: sales Tables: FACT_TABLE. . FACT_TABLE. LU_SALES_REP. LVW_HIST_DISTRICT_SALES 6 Define the metric as required: • Sales: SUM(sales) The result of this is a logical schema that looks like the following: LU_CURRENT_DISTRICT LU_CURRENT_ORG LU_SALES_REP FACT_TABLE Current District Sales Rep Current District Sales Rep Historical District Sales Rep Date Sales LU_TIME Date LVW_HISTORICAL_ DISTRICT_SALES Month Historical District Date Sales 382 Logical view examples © 2007 MicroStrategy. Inc. trans_dt – Tables: LU_TIME (lookup) . LVW_HIST_DISTRICT_SALES – Child: Sales Rep • Date: – @ID = date_id.

Sales_rep_ID) where F.Project Design Guide Logical Tables C As-was analysis Specify the “as-was” analysis by using the Historical District attribute on reports: • • Report definition: Historical District. Inc. Month.Sales_rep_ID = F.EFF_DT and L.END_DT group by District_ID.trans_dt between L. sum(a11.Trans_dt = a12.District_ID =a13. Month.Distrcit_ID.SALES) WJXBFS1 From (select District_ID. Trans_dt.District_Name) District_Name.Month_ID Month_ID. Sales Resulting SQL Logical view examples 383 . a12.sum(sales) sales from LU_SALES_REP L join FACT_TABLE F on (L.Month_ID • Report results As-is analysis Specify the “as-is” analysis by using the Current District attribute on reports: • • © 2007 MicroStrategy.District_ID District_ID. a12.District_ID) group by a11. Trans_dt) a11 join LU_TIME a12 on (a11. Report definition: Current District.Date_ID) join LU_DISTRICT a13 on (a11. Sales Resulting SQL Select a11. max(a13.

C Logical Tables Project Design Guide select a12.Sales_Rep_ID = a12. a13.District_ID) group by a12. District_ID from LU_SALES_REP where END_DT = '12/31/2099')a12 on (a11. An example set of records is shown below. a13.Month_ID Month_ID.District_ID = a14.District_Name) District_Name. max (a14.Sales_Rep_ID) join LU_TIME a13 on (a11.District_ID District_ID.Date_ID) join LU_DISTRICT a14 on (a12.SALES) WJXBFS1 from FACT_TABLE a11 join (select Sales_rep_ID. .Month_ID • Report result Example 2: New surrogate key for each changing element A more flexible way to physically store a SCD is to employ surrogate keys and introduce new rows in the dimension table whenever a dimensional relationship changes. Inc. Another common characteristic is to include an indicator field that identifies the current relationship records. sum(a11. LU_SALES_REP Sales_Rep_CD 1 2 3 Sales_Rep_ID 1 2 3 Sales_Rep_Name Jones Smith Kelly District_ID 37 37 38 Current_Flag 0 1 0 384 Logical view examples © 2007 MicroStrategy.Trans_dt = a13.District_ID.

A transaction date field may or may not exist. LVW_CURRENT_ORG select Sales_rep_ID. Logical view examples 385 . FACT_TABLE Sale-Rep_CD 1 2 3 5 2 3 2 6 4 Sale 100 200 150 200 250 300 125 275 150 Specifying the MicroStrategy schema 1 Create a logical view to represent just the current District-Sales Rep relationship. © 2007 MicroStrategy. Inc.Project Design Guide Logical Tables C Sales_Rep_CD 4 5 6 Sales_Rep_ID 4 1 3 Sales_Rep_Name Madison Jones Kelly District_ID 38 39 39 Current_Flag 1 1 1 When using this type of dimensional lookup table. the fact table must also include the surrogate key. District_ID from LU_SALES_REP where Current_flag = 1 2 Create a table alias LU_CURRENT_DISTRICT for LU_DISTRICT.

Inc. LVW_CURRENT_ORG – Child: Sales Rep • Historical District: – @ID = district_id. trans_dt – Tables: LU_TIME (lookup).C Logical Tables Project Design Guide 3 Define the following attributes: • Sales Rep Surrogate: – @ID = sales_rep_cd – Tables: LU_SALES_REP (lookup). LVW_CURRENT_ORG – Child: Sales Rep Surrogate • Current District: – @ID = district_id. LU_SALES_REP – Child: Sales Rep • Date: – @ID = date_id. FACT_TABLE • Month: – @ID = MONTH_ID – Tables: LU_TIME (lookup) – Child: Date 4 Define the Sales fact: • Expression: sales 386 Logical view examples © 2007 MicroStrategy. @Desc = district_name – Tables: LU_CURRENT_DISTRICT (lookup). @Desc = sales_rep_name – Tables: LU_SALES_REP (lookup). . @Desc = district_name – Tables: LU_DISTRICT (lookup). FACT_TABLE • Sales Rep: – @ID = sales_rep_id.

Month_ID Month_ID.Sales_Rep_CD = a12. max(a14. a13. Inc.Trans_dt = a13.Date_ID) join LU_DISTRICT a14 on (a12.Distrcit_Name) Distrcit_Name. LVW_HIST_DISTRICT_SALES 5 Define the metric as required: • Sales: SUM(sales) The result is a logical schema as follows: LU_CURRENT_DISTRICT LU_CURRENT_ORG LU_SALES_REP FACT_TABLE LU_TIME Current District Sales Rep Current District Sales Rep Surrogate Sale rep Historical District Sales Rep Surrogate Date Sales Date Month LVW_HISTORICAL_ DISTRICT_SALES Historical District As-was analysis Specify the “as-was” analysis by using the Historical District attribute on reports: • • Report definition: Historical District.Project Design Guide Logical Tables C • Tables: FACT_TABLE.District_ID = © 2007 MicroStrategy. sum(a11. Logical view examples 387 .District_ID District_ID.Sales_Rep_CD) join LU_TIME a13 on (a11.SALES) WJXBFS1 from FACT_TABLE a11 join LU_SALES_REP a12 on (a11. Month. Sales Resulting SQL select a12.

District_ID) group by a12.SALES) WJXBFS1 from FACT_TABLE a11 join LU_SALES_REP a12 on (a11.Distrcit_Name) District_Name.District_ID) group by a13.Sales_Rep_CD) join (select Sales_rep_ID.District_ID.Month_ID • Report results As-is analysis Specify the “as-is” analysis by using the Current District attribute on reports: • • Report definition: Current District.Date_ID) join LU_DISTRICT a15 on (a13.C Logical Tables Project Design Guide a14. a14. sum(a11.District_ID = a15.Month_ID 388 Logical view examples © 2007 MicroStrategy.Sales_Rep_CD = a12.Month_ID Month_ID. District_ID from LU_SALES_REP where current_flag = 1) a13 on (a12.District_ID.Sales_Rep_ID = a13. Inc. a14. .Sales_Rep_ID) join LU_TIME a14 on (a11. max(a15. Month. Sales Resulting SQL: select a13. a13.District_ID District_ID.Trans_dt = a14.

day_date >= B. Select day_date day_date.day_date) The same technique can be used to define a year-t0-date transformation. Logical view examples 389 . lu_day B Where A. one-to-many transformations require tables in the database that map each date to all the previous dates that make up “month-to-date”. The MTD transformation can then be defined using the MTD_DATE column.day_date)= MONTH(B.day_date mtd_date From lu_day A. If you do not already have such a table in the warehouse and your circumstances do not allow you to add additional tables to the database.day_date And YEAR(A. lu_day B Where A. which contains the Day attribute.day_date And MONTH(A. you need to define transformations. B. Although one-to-one transformations. The SQL below can be used to define a logical MTD_DATE table. B.day_date) © 2007 MicroStrategy.day_date day_date.day_date) = YEAR(B. Select A. such as month-to-date and year-to-date calculations.Project Design Guide Logical Tables C • Report result Business case 4: One-to-many transformation tables In order to support time-series analysis. then you can use the logical view approach to address this issue as long as you already have a lookup table for the Day attribute. can be defined in terms of an expression. such as Last Month. Inc.day_date >= B.day_date ytd_date From lu_day A.

Emergency Contact Phone Number NULLS are displayed for employees who do not have emergency contacts. Inc. which means not all employees have contacts on record.. John Larkins. James Dawson. Martha . Abraham Walker. Mary Walker.C Logical Tables Project Design Guide Business case 5: Outer joins between attribute lookup tables A common request is the ability to generate an outer join between attribute lookup tables for a report that contains only attributes (that is. George .. Dawson. EMPLOYEE EMP_ID FIRST_NAME LAST_NAME HIRE_DATE DEPT_ID EMERGENCY CONTACT EMP_ID CONTACT_FIRST_NAME CONTACT_LAST_NAME CONTACT_PHONE_NUMBER DEPARTMENT DEPT_ID DEPT_NAME BUS_UNIT_ID Given this structure. For example.. consider the tables below.. Jane Taylor. Department Marketing Finance R&D Finance . 390 Logical view examples © 2007 MicroStrategy.. One of the reports you probably would like to create may look like the following: Employee Gonzalez. no metrics). . the relationship between Employees and Emergency Contacts is such that each employee may have up to one contact.... 555-1212 555-3456 555-9876 . you could model an attribute hierarchy as follows: • • • Business Unit -< Department -< Employee Hire Date -< Employee Emergency Contact -< Employee In addition.

the SQL generated would join the EMPLOYEE table to the EMERGENCY_CONTACT table. you can perform an outer join using a logical view. @[First Name] = CONTACT_FIRST_NAME. Inc. EMERGENCY_CONTACT • Department: @ID = DEPT_ID Tables: DEPARTMENT (lookup). and only those employees who have emergency contacts would appear in the final result. @[First Name] = FIRST_NAME. if you model the attributes as described below. @[Last Name] = LAST_NAME Tables: EMPLOYEE (lookup).Project Design Guide Logical Tables C However. Logical view examples 391 . you would not get the desired output: • Employee: @ID = EMP_ID. In order to see all employees. @[Last Name] = CONTACT_LAST_NAME Tables: EMERGENCY_CONTACT (lookup) Child: Employee Using the above model. EMPLOYEE Child: Employee • Hire Date: @ID = HIRE_DATE Tables: EMPLOYEE (lookup) Child: Employee • Emergency Contact: @ID = CONTACT_PHONE_NUMBER. © 2007 MicroStrategy. described as follows.

DEPT_ID. you can use the following SQL and the list of columns to map to the view: select E.CONTACT_FIRST_NAME. C. C. LVW_EMERGENCY_CONTACT 392 Logical view examples © 2007 MicroStrategy. E. . E.LAST_NAME. @[First Name] = FIRST_NAME.EMP_ID) LVW_EMERGENCY_CONTACT EMP_ID FIRST_NAME LAST_NAME HIRE_DATE DEPT_ID CONTACT_FIRST_NAME CONTACT_LAST_NAME CONTACT_PHONE_NUMBER Make sure to include all columns from the original child table (for example.EMP_ID. EMPLOYEE). E.CONTACT_LAST_NAME.FIRST_NAME.HIRE_DATE. C.C Logical Tables Project Design Guide Using a logical view for an outer join To perform an outer join for the case described above.EMP_ID = C. @[Last Name] = LAST_NAME Tables: EMPLOYEE (lookup).CONTACT_PHONE_NUMBER from EMPLOYEE E left outer join EMERGENCY_CONTACT C on (E. The new logical table LVW_EMERGENCY_CONTACT can then be used to define attributes as follows: • Employee: @ID = EMP_ID. E. Inc.

LVW_EMERGENCY_CONTACT Child: Employee • Emergency Contact: @ID = CONTACT_PHONE_NUMBER. and NULLs will be returned for any employees who do not have emergency contacts. This technique is applicable any time that the lookup tables should always be outer joined. LVW_EMERGENCY_CONTACT Child: Employee The Employee attribute is not represented in the original EMERGENCY_CONTACT table and all attributes represented in the EMPLOYEE table are also represented in the LVW_EMERGENCY_CONTACT table. EMPLOYEE. The technique does not work when the lookup tables should sometimes be outer joined and sometimes be inner joined. LVW_EMERGENCY_CONTACT Child: Employee • Hire Date: @ID = HIRE_DATE Tables: EMPLOYEE (lookup). @[Last Name] = CONTACT_LAST_NAME Tables: EMERGENCY_CONTACT (lookup). the EMPLOYEE table will be outer joined to the EMERGENCY_CONTACT table.Project Design Guide Logical Tables C • Department: @ID = DEPT_ID Tables: DEPARTMENT (lookup). it will be executed against the EMPLOYEE table. Now if we run a report with Employee and Emergency Contact attributes. the EMERGENCY_CONTACT table will be joined only when necessary. Logical view examples 393 . @[First Name] = CONTACT_FIRST_NAME. Inc. Also note that if we run a report that includes only the Employee attribute. © 2007 MicroStrategy.

C Logical Tables Project Design Guide 394 Logical view examples © 2007 MicroStrategy. Inc. .

Mapping of external data types to MicroStrategy data types 395 . DATA TYPES Introduction To generate SQL or retrieve data from data sources.D D. © 2007 MicroStrategy. Inc. MicroStrategy generalizes them into a set of MicroStrategy-specific data types. MicroStrategy automatically maps the columns within those tables to MicroStrategy-specific data types. MicroStrategy must be aware of the data types that exist in your database. Mapping of external data types to MicroStrategy data types When you create a project and add tables from your data warehouse to the MicroStrategy Warehouse Catalog. Each column from your database becomes associated with a MicroStrategy data type. As each RDBMS supports a different set of data types.

“INTEGER. 396 Mapping of external data types to MicroStrategy data types © 2007 MicroStrategy. The data type is also used whenever multi-pass SQL is used. a column within that table has a data type of “SMALLINT.” This allows MicroStrategy to maintain a consistent SQL generation process. in part. In your relational database. and data mart tables. MicroStrategy must map every column brought into the project schema to an internal data type. Data types that may be conceptually the same can have different names. and generating the correct syntax for literals. Suppose you add a table to the Warehouse Catalog. Inc.” MicroStrategy maps this column to a MicroStrategy-specific data type. refer to MicroStrategy Technical Note TN5200-7X0-0166. The MicroStrategy data type stores data values internally and in the metadata repository and is later used during SQL generation when defining intermediate tables. . see the MicroStrategy Advanced Reporting Guide. For more information about data marts and custom groups. as with custom groups. for example. For information about how your relational database’s data types are mapped to MicroStrategy data types and the specific mappings that pertain to your RDBMS.D Data Types Project Design Guide This external-to-internal mapping is necessary. It is strongly recommended that you do not alter the mapping file (DTMAPPING.pds) in any way. Therefore. because each database names data types in different ways.

Project Design Guide Data Types D MicroStrategy data types When the data warehouse catalog is read from the Warehouse Catalog. Unsigned Unsigned integer values. Similar to ANSI DOUBLE PRECISION. Date Calendar dates. MicroStrategy data types 397 . Data Type Big Decimal Binary Description High-precision fixed point numbers. Fixed-length bit strings. © 2007 MicroStrategy. Double 8-byte floating point numbers. LongVarChar Large strings of characters. Similar to ANSI REAL. Inc. Char Fixed-length character strings. Real 4-byte floating point numbers. LongVarBin Large strings of bits. Similar to ANSI TIME. Similar to ANSI BLOB. Numeric Fixed point numbers up to 15 digits of precision. Similar to ANSI TIMESTAMP. Integer Signed integer values. Similar to ANSI DECIMAL. Similar to ANSI BIT. Time Time of day. Similar to ANSI CLOB. Timestamp Combinations of calendar date and time of day. Decimal Fixed point numbers up to 15 digits of precision. all columns in the database are automatically mapped to one of the following MicroStrategy data types. Float 4-byte floating point numbers. Similar to ANSI NUMERIC. Similar to ANSI CHAR. Similar to ANSI INTEGER. Similar to ANSI DATE. Similar to ANSI FLOAT.

which represents high-precision fixed point numbers. You specify the format type of an attribute form in the Form Format: Type drop-down menu in the Attribute Editor. Date Datetime Email HTML Tag Number 398 Format types © 2007 MicroStrategy. Information is stored and displayed as an HTML tag. Information is stored and displayed both as date and time in the format specific to the data. which specifies how attribute form values should be displayed on MicroStrategy interfaces. page 400. it implies that the data type in the database has not mapped to one of the MicroStrategy data types. Information is stored and displayed in the form of an e-mail address. Information is stored and displayed as dates in a sequential form to perform calculations on the dates. see Big Decimal. Similar to ANSI VARCHAR. Format Type Big Decimal Description Information is stored and displayed in the Big Decimal form. If the Warehouse Catalog displays a column with data type as Unknown. Format types Attribute forms are also associated with a MicroStrategy format type. The attribute form format types are described in the following table. For more information about Big Decimal. Similar to ANSI BIT VARYING. Information is stored and displayed in a number format.D Data Types Project Design Guide Data Type Varbin Description Variable-length bit strings. It represents dates in the MM/DD/YYYY format. Inc. Varchar Variable-length character strings. The date follows the MM/DD/YYYY format and time follows the HH:MM:SS format. .

If you select a format type that is incompatible with the data type and click OK to exit the Attribute Editor. you must select an appropriate format type from the Form Format: Type drop-down menu. doing so can still result in SQL generation issues. or GIF. This displays only the time and not the date. for example—you must also change the format type of the attribute. Although you have the option to continue by clicking Yes. In the Column Alias tab. URL Data type and format type compatibility If you change the MicroStrategy data type of one of the columns in your project—using a column alias. such as bitmap. Inc. The data type of your column must be consistent with the format type you select because SQL generation issues can occur if the format type and data type are incompatible. This format type must be compatible with the data type you assigned in the Column Alias tab. Information is stored and displayed as time in the HH:MM:SS format. JPG. you edit the ID form of the Year attribute in the Attribute Editor. you notice that the Year attribute is assigned an “Integer” data type. However. Data type and format type compatibility 399 . Information is stored and displayed in a text format. For example.Project Design Guide Data Types D Format Type Picture Text Time Description stored and displayed the form of an image file. © 2007 MicroStrategy. a warning message appears notifying you of the incompatibility. You are warned in the Attribute Editor whenever you have selected a format type that is incompatible with the data type of your column. When you return to the Definition pane in the Attribute Editor. you create a new column alias and assign it the “Date” data type. Information is stored and displayed as either an absolute or a relative Universal Resource Locator.

some of the data type-format type combinations below may not work with your specific data. HTML Tag. Text Number Number Time. Datetime Datetime. Datetime Number Number Number Number Picture. Data Type Big Decimal Binary Char Date Decimal Double Float Integer LongVarBin LongVarChar Numeric Real Time Timestamp Unsigned Varbin Varchar Compatible Format Types Big Decimal Number. Text depending on data Picture. E-mail. Different format types are compatible with different data types given the specific data in your column. URL. Picture Big Decimal Big Decimal is a MicroStrategy-specific data type that allows users to support high-precision attribute ID values that have more than 15 digits of precision. Therefore. Date or Time depending on data Number Picture. Text. Text Text. HTML Tag Date.D Data Types Project Design Guide The following chart is intended to guide you in assigning format types that are compatible with the data type you have assigned to a column. Inc. such as BIGINT and 400 Big Decimal © 2007 MicroStrategy. E-mail. . URL. Picture Text.

Big Decimal 401 . For more information about these operations. Attribute form: If you change the column data type to Big Decimal on the Column Alias tab in the Attribute Editor. If you do not associate high-precision database fields with the Big Decimal data type. even though 12345678 does not necessarily require the Big Decimal data type. such as account numbers and other long integers. you may see numbers truncated starting with the 16th digit. you can define a filter as "Customer@ID exactly #12345678#". Attribute ID: Follow the steps in the topic Defining attributes with high-precision ID forms in the MicroStrategy Desktop online help. These numeric columns can have more than 15 digits of precision. and long integers. For example. • • © 2007 MicroStrategy. Examples of such attribute ID values are account numbers. see the MicroStrategy Basic Reporting Guide. drilling. The WHERE clause in the report SQL statement in drill reports may truncate numbers starting from the 16th digit. and page-by may not return results. When using the Big Decimal data type. MicroStrategy preserves the precision of attribute ID values and attribute ID forms when displaying IDs and performing operations such as filtering. you must also select Big Decimal as the form format type in the Form format: Type drop-down menu in the Definition tab. Inc. because these data values have higher precision and cannot be stored in normal numeric data types. You can define attributes that are identified by numeric columns in the database. credit card numbers. Using the Big Decimal data type With the Big Decimal data type. and page-by. follow the rules listed below: • Constant: You can force a constant to be stored as a Big Decimal value by enclosing it in hash marks. You must use the Big Decimal data type to handle these values.Project Design Guide Data Types D DECIMAL (precision. scale) data types.

s) columns to the Big Decimal MicroStrategy data type even when the precision is greater than 15. you must explicitly identify high-precision constants by enclosing the value within hash (#) symbols. 402 Big Decimal © 2007 MicroStrategy. Some number formatting strings are not supported in MicroStrategy Desktop. s) or NUMERIC(p. #1234567890123456#. This is because Big Decimal should only be used when the column is used as an attribute ID form. When qualifying on a Big Decimal metric. For example. Note that the Warehouse Catalog does not automatically map DECIMAL(p. Number formatting strings are not supported on the Web.D Data Types Project Design Guide • Metric: Although it is possible to define Big Decimal as the data type for metric values. . the metric is used in a calculated field in a document. Inc. consider the following drawbacks: Precision is lost when any Analytical Engine calculation is performed. the metric is subtotaled. or metric values are displayed in Graph view.

All of these objects can be built and manipulated in MicroStrategy Desktop.GLOSSARY aggregate function A numeric function that acts on a column of data and produces a single result. metrics. application object An object used to provide analysis of and insight into relevant data. The definition of application objects such as reports. Reports and documents can also be created and manipulated in MicroStrategy Web. See pre-aggregation. custom groups. aggregate table A fact table that stores data that has been aggregated along one or more dimensions. © 2007 MicroStrategy. Inc. and AVG. documents. COUNT. Examples include SUM. Compare database-level partition. MAX. templates. and prompts are derived from schema objects. application-level In application-level partitioning. aggregate function 403 . the application rather than partition the database server manages the partition tables. MIN. filters. MicroStrategy supports two methods of application-level partitioning: metadata partition mapping and warehouse partition mapping.

Inc. City. . February. attribute role A database column that is used to define more than one attribute. defined by the attribute forms. January. Attributes include data classifications like Region. See also: • • • • • • attribute element attribute form child attribute constant attribute derived attribute parent attribute attribute element A unique set of information for an attribute. Every attribute supports its own collection of forms. ID. and Abbreviation could be forms of the attribute Customer. Long Description. Order. Age. 404 attribute © 2007 MicroStrategy. Item. Name. For example. and March are elements of the attribute Month. For example. attribute form One of several columns associated with an attribute that are different aspects of the same thing. Billing City and Shipping City are two attributes that have the same table and columns defined as a lookup table.Glossary Project Design Guide attribute A data level defined by the system architect and associated with one or more columns in a data warehouse lookup table. attribute form A mapping to the columns in the warehouse that are used to expression represent a specific attribute form in SQL. and Year. Last Name. They provide a means for aggregating and filtering at a given level. attribute relationship See relationship. Customer. New York and Dallas are elements of the attribute City.

metrics. he places template units—attributes. cardinality The number of unique elements for an attribute. cache A special data store holding recently accessed information for quick future access. the job is submitted to the database for processing. and custom groups—along each axis. browse attribute An attribute a user can directly browse to from a given attribute in a user hierarchy. whose execution is faster because they need not run against the database. business intelligence A system that facilitates the analysis of volumes of complex (BI) system data by providing the ability to view data from multiple perspectives. Column. when a user runs a report for the first time.Project Design Guide Glossary axis A vector along which data is displayed. Results from the data warehouse are stored separately and can be used by new job requests that require the same data. and Page. When a user defines a template for a report. Inc. There are three axes—Row. if the results of that report are cached. dimensions. See also: • • column row base fact column A fact column represented by a single column in a fact table. the results can be returned immediately without having to wait for the database to process the job the next time the report is run. axis 405 . However. This is normally done for frequently requested reports. © 2007 MicroStrategy. consolidations. In the MicroStrategy environment.

3) MicroStrategy object in the schema layer that can represent one or more physical table columns or no columns.Glossary Project Design Guide child attribute The lower-level attribute in an attribute relationship. See also: • • axis row column alias In a fact definition. 406 child attribute © 2007 MicroStrategy. Column aliases also include the data type to be used for the fact and allow you to modify the names of existing metrics for use in data mart reports without affecting the original metric. The larger the compression ratio between two attributes. Inc. compound attribute An attribute that has more than one key (ID) form. . This is used to determine where aggregate tables would have the greatest impact. the specific name of the column to be used in temporary tables and SQL statements. the compression of ratio between monthly data and yearly data is 12:1. For example. 2) The set of fields of a given name and data type in all the rows of a given table. the more you stand to gain by creating an aggregate table that pre-calculates the higher-level data. See also: • • parent attribute relationship column 1) A one-dimensional vertical array of values in a table. compression ratio The average number of child records combined to calculate one parent record. compound key In a relational database. a primary key consisting of more than one database column.

which refers more specifically to using a database as your data source. conditionality 407 . and analysis. and OLAP cube sources such as SAP BW. configuration object A MicroStrategy object appearing in the system layer and usable across multiple projects. Inc. 2) A copy of transaction data specifically structured for query. it organizes data and allows coordinated updates and loads. Used for decision support or business intelligence. or storage location which stores data that is to be used in MicroStrategy for query. database instances. reporting. Excel files. Users can navigate through hierarchies of attributes that are defined by the administrator to find the data they need. Data Explorer A portion of the interface used to browse through data contained in the warehouse. A data warehouse can be thought of as one type of data source. typically very large. Microsoft Analysis Services 2000 and 2005. See also data source. See also: • • data warehouse OLAP cube source data warehouse 1) A database. database login IDs. constant attribute See implicit attribute.Project Design Guide Glossary conditionality Conditionality of a metric enables you to associate an existing filter object with the metric so that only data that meets the filter conditions is included in the calculation. Other data sources include text files. data source A data source is any file. containing the historical data of an enterprise. reporting. and analysis. schedules. system. © 2007 MicroStrategy. and Hyperion Essbase. Configuration objects include these object types: users.

degradation A type of fact extension in which values at one level of aggregation are reported at a second. description column Optional columns that contain text descriptions of attribute elements. not in the database. Although it is technically possible to have more than one instance running on a machine. on report data after it has been returned from the database. lower attribute level. Login ID and password. Inc. calculations on other metrics. derived fact column A fact column created through a mathematical combination of other existing fact columns. Use a derived metric to perform column math. Age might be calculated from this expression: Current Date–Birth Date Compare implicit attribute. and other data warehouse specific information. . such as the data warehouse DSN. Compare allocation. derived metric A metric based on data already available in a report. A MicroStrategy object created in MicroStrategy Desktop that represents a connection to the warehouse. that is. Database server software running on a particular machine. 2. It is calculated by Intelligence Server.Glossary Project Design Guide database instance 1. A database instance specifies warehouse connection information. For example. there is usually only one instance per machine. 408 database instance © 2007 MicroStrategy. derived attribute An attribute calculated from a mathematical operation on columns in a warehouse table.

viewing the list of months in a year. a shortcut to an attribute in the Data Explorer which is helpful in allowing users to more easily access frequently-used attributes in the Data Explorer. or the addition. entry point In a user hierarchy. a store may decide to reclassify the department to which items belong. element browsing Navigating through hierarchies of attribute elements. For example. See also: • • • • • page-by pivot sort subtotal surf dynamic relationship When the relationship between elements of parent and child attributes changes. which lets you easily recognize tables and columns and the data stored in those columns. or discontinuation of items or services.Project Design Guide Glossary drill A method of obtaining supplementary information after a report has been executed. drill 409 . reclassification. For example. entity relationship A diagram that provides a graphical representation of the diagram (ERD) physical structure of the data in the source system. geographical realignment. These changes often occur because of organizational restructuring. entry level The lowest level set of attributes at which a fact is available for analysis. © 2007 MicroStrategy. Inc. The new data is retrieved by re-querying the Intelligent Cube or database at a different attribute or fact level.

. filter A MicroStrategy object that specifies the conditions that the data must meet to be included in the report results. since a report queries the database against all the data stored in the data warehouse. Using a filter on a report narrows the data to consider only the information that is relevant to answer your business question. stored in a data warehouse. Inc. fact column A column in a database table that contains fact data. loading (ETL) 2) Third-party software used to facilitate such a process. which is the actual condition that must be met for the data to be included on a report. and disparate existing database systems. Multiple qualifications in a single filter are combined using logical operators. transformation. or inventory quantities in counts. A filter is normally implemented in the SQL WHERE clause. 410 extraction. Facts can have multiple fact expressions. fact 1) A measurement value. See also metric. fact table A database table containing numeric data that can be aggregated along one or more dimensions. often numeric and typically aggregatable. A filter is composed of at least one qualification. or sales in dollars. 2) A schema object representing a column in a data warehouse table and containing basic or aggregated numbers—usually prices. Fact tables can contain atomic or summarized data. Examples include "Region = Northeast" or "Revenue > $1 million". 1) The process used to populate a data warehouse from transformation. and loading (ETL) © 2007 MicroStrategy.Glossary Project Design Guide extraction. fact expression A mapping of facts to physical columns in the warehouse. Fact expressions can be as simple as a fact column name from the warehouse or as sophisticated as a formula containing fact columns and numeric constants.

but the description columns are present as well. because in the Attribute Editor. one column named Customer in one table and one named Customer Name in a different table. See also compound key. ID column A column that contains attribute element identification codes. both containing customer names. . form group 411 © 2007 MicroStrategy. homogeneous column Columns in different tables of a database that contain the naming same data and have the same column name. which identifies that an attribute form requires more than one ID column to uniquely identify its elements. though. For example. though nothing is saved in a column. Inc. highly denormalized Schema type where not only are higher-level attribute ID schema columns present within all related tables. hierarchy A set of attributes defining a meaningful path for element browsing or drilling. Such an attribute has its expression defined as a constant value. All attributes must have an ID column.Project Design Guide Glossary form group A grouping of attribute forms that are related in a way that justifies combining the forms into a single form. For example. heterogeneous column Columns in different tables in a database that store the same naming data but have different names. You do not have to actually create the column. you may wish to create columns in the database with a value of 1 for every row to get around COUNT limitations. implicit attribute An attribute that does not physically exist in the database because it is created at the application level. The order of the attributes is typically—though not always—defined such that a higher attribute has a one-to-many relationship with its child attributes. highly normalized Schema type where lookup tables contain unique schema developer-designed attribute keys. A form group must be created to create a compound key.

item. which arranges data for efficient database use. In this case. Implicit attributes are useful in analyzing and retrieving information.For example. You can use constant attributes when building metrics.Glossary Project Design Guide you can just enter a “1” in the expression to create a count. . Inc. locked hierarchy A hierarchy that has at least one attribute that may not be browsed by end users. where you can sum the column holding the constant to create a COUNT. These relationships can be modeled and conceptualized like traditional attributes. Hierarchies are usually locked if there are so many attribute elements that element browsing is not usable. A business might run this promotion around Valentine's Day (Q1) and again at Christmas time (Q4). They typically consist of descriptions of dimensions. consider the relationship between three attributes: promotion. An example of a promotion might be a “Red Sale” where all red items are on sale. and quarter. 412 joint children © 2007 MicroStrategy. but like facts. Lookup tables are usually joined to fact tables to group the numeric facts in the fact table by dimensional attributes in the lookup tables. joint children Joint child relationships are another type of many-to-many relationship where one attribute has a many-to-many relationship to two otherwise unrelated attributes. promotion has a many-to-many relationship to both item and quarter. lookup table A database table used to uniquely identify attribute elements. you can use constant attributes to create a COUNT to keep track of the number of rows returned. Compare derived attribute. Any constant is acceptable. logical data model A graphical representation of data that is arranged logically for the general user. as opposed to the physical data model or warehouse schema. they exist at the intersection of multiple attribute levels. When analyzing data.

which is created by the system and stored in a separate system folder. and vice versa. and OLAP cube reports. See also metadata shell. Managed objects are used to map data to attributes. metrics. Query Builder.Project Design Guide Glossary managed object A schema object unrelated to the project schema. hierarchies and other schema objects for Freeform SQL. and needs to the underlying database structure. terms. and (2) every element of the child attribute can relate to multiple elements of the parent. Metadata can reside on the same server as the data warehouse or on a different database server. See also: • • • • one-to-one one-to-many many-to-one relationship many-to-one An attribute relationship in which (1) multiple elements of a parent attribute relate to only one element of a child attribute. Inc. It can even be held in a different RDBMS. See also: • • • • one-to-one one-to-many many-to-many relationship metadata A repository whose data associates the tables and columns of a data warehouse with user-defined attributes and facts to enable the mapping of the business view. many-to-many An attribute relationship in which multiple elements of a parent attribute can relate to multiple elements of a child attribute. © 2007 MicroStrategy. managed object 413 .

The startup code initiates the primary thread of a process by passing the main function address to the operating system. moderately normalized Schema type having the same basic structure as the highly schema normalized schema. and so on. attributes. See also metadata. multithreaded Characteristic of a process that supports the simultaneous execution of multiple threads. Inc. MOLAP Multidimensional online analytical processing. file services. object Conceptually. and mobile devices. including folders. or other metrics. facts. metric 1) A business calculation defined by an expression built with functions.[Cost] 2) The MicroStrategy object that contains the metric definition. In MicroStrategy. Narrowcast Server is a proactive information delivery server that allows for this distribution of information through e-mail. facts. See also fact. printers. When the primary thread terminates. used by the user to achieve the goal of specified data analysis. but here the higher-level attribute ID columns are present within all related tables. . an application that allows for the distribution of personalized business information to subscribed users. metrics. More concretely. reports. narrowcast application In a business intelligence environment. SMS. an object is the highest grouping level of information about one concept. the process terminates.Glossary Project Design Guide metadata shell A set of blank tables that are created when you initially implement a MicroStrategy business intelligence environment. For example: sum(dollar_sales) or [Sales] . 414 metadata shell © 2007 MicroStrategy. an object is any item that can be selected and manipulated.

the third-party tools SAP BW. while every element of the child attribute relates to only one element of the parent. See also OLAP cube source. and analysis on the data. Inc. and Hyperion Essbase are referred to as OLAP cube sources. and analyze data with MicroStrategy. See also: • • • • one-to-one many-to-many many-to-one relationship © 2007 MicroStrategy. The one-to-many attribute relationship is the most common in data models.Project Design Guide Glossary OLAP cube An OLAP cube is a collection or set of data retrieved from an OLAP cube source. MicroStrategy can integrate with OLAP cube source data as well as access data from a relational database concurrently. OLAP cube 415 . You can import and map data from these different OLAP cube sources in MicroStrategy to query. which is imported into MicroStrategy and mapped to various objects to allow query. See also: • • OLAP cube data source one-to-many An attribute relationship in which every element of a parent attribute can relate to multiple elements of a child attribute. OLAP cube source When integrated with MicroStrategy. Microsoft Analysis Services. report on. reporting.

Transactional processing involves the simple recording of transactions such as sales. and profit analysis. growth patterns.Glossary Project Design Guide one-to-one An attribute relationship in which every element of the parent attribute relates to exactly one element of the child attribute. Inc. percent to total contributions. The slice is characterized by the choice of elements on the Page axis. and vice versa. databases or mainframes that store transactional processing (OTLP) data. online transaction Typically. and metrics on a third axis called the Page axis. or deposits. inventory. page-by Segmenting data in a grid report by placing available attributes. By varying the selection of elements. withdrawals. only a slice of the cube can be seen at any one time. the user can page through the cube. Since a grid is two-dimensional. . See also: • • • • one-to-many many-to-one many-to-many relationship online analytical A system with analytical processing that involves activities processing (OLAP) such as manipulating transaction records to calculate sales trends. consolidations. See also: • • • • • drill pivot sort subtotal surf 416 one-to-one © 2007 MicroStrategy. trend reporting.

partition mapping The division of large logical tables into smaller physical tables based on a definable data level.Project Design Guide Glossary parent attribute The higher-level attribute in an attribute relationship with one or more children. such as month or department. Partition tables are usually divided along logical lines. partitions improve the speed and efficiency of database queries. while the opposite is not necessarily true. such as time or geography. See also partition mapping. parent attribute 417 . See also: • • • • relationship one-to-many many-to-one many-to-many partition base table A warehouse table that contains one part of a larger set of data. Also referred to as a PBT. Partitions minimize the number of tables and records within a table that must be read to satisfy queries issued against the warehouse. © 2007 MicroStrategy. By distributing usage across multiple tables. Inc. See also: • • child attribute relationship partial relationship An attribute relationship in which elements of one attribute relate to elements of a second attribute.

Glossary Project Design Guide partition mapping table A warehouse table that contains information used to identify the partitioned base tables as part of a logical whole. it knows to forward those calls to the Intelligence Server port number that is specified in the call. . to reconfigure a grid report by interchanging row and column headers. Inc. For example. consolidations) on different axes. Subset of cross-tab. and hence the associated data. when the Intelligence Server machine receives a network call from a client (Desktop. It organizes the logical data model in a method that make sense from a database perspective. 418 partition mapping table © 2007 MicroStrategy. pivot To reconfigure data on a grid report by placing report objects (attributes. Also. See also: • • partition base table partition mapping physical warehouse A detailed graphic representation of your business data as it schema is stored in the data warehouse. Also referred to as a PMT. Web. Narrowcast Server. Command Manager. and so on). metrics. See also: • • • • • drill page-by sort subtotal surf port number The port number is how a server process identifies itself on the machine on which it is running. See also schema.

and synchronization objects. pre-aggregation 419 . that is completed before reports are run. metrics. Also. project source Defines a connection to the metadata repository and is used by various MicroStrategy products to access projects. Processes use temporary private address spaces and control operating system resources such as files. A direct project source is a two-tier connection directly to a metadata repository. metadata repository. See also table name space. dynamic memory allocations. © 2007 MicroStrategy. 2) An object containing the definition of a project. Prefixes can be defined and modified from the Warehouse Catalog interface.Project Design Guide Glossary pre-aggregation Aggregation. as defined in (1). the Catalog Server uses it to obtain table sample values and row counts. and functions. containing reports. In most cases. process An executing application comprising one or more threads. Inc. A server project source is a 3-tier connection to a MicroStrategy Intelligence Server. See also: • • aggregate table aggregation prefix A prefix is stored in the project metadata associated with a table or tables and is used by the Engine to generate SQL. One project source can contain many projects and the administration tools found at the project source level are used to monitor and administer all projects in the project source. and user community. it should match the name space field since it is used to qualify on a specific table belonging to a certain owner or name space. with the results stored in an aggregate table. or the calculation of numeric data at a specific attribute level. filters. The project object is specified when requesting the establishment of a session. pipes. project 1) The highest-level intersection of a data warehouse.

and then set how to combine the qualifications using the logical operators AND. or size between the cardinalities of related attributes. quality relationship The relationship between a parent attribute and two or more “joint child” attributes. relate table A table containing the ID columns of two or more attributes. relational database A relational database management system (RDBMS) is a management system program that lets you create. The user is asked during the resolution phase of report execution to provide an answer that completes the information. . A relational database is a collection of data items organized as a set of formally-described tables from which data can be accessed or reassembled in many different ways without having to reorganize the database tables. 420 prompt © 2007 MicroStrategy. a window requesting user input. and OR NOT. The leading RDBMS products are Oracle. and administer a relational database. thus defining associations between them. amount. See also cardinality.Glossary Project Design Guide prompt 1) MicroStrategy object in the report definition that is incomplete by design. The parent attribute is referred to as a “quality” because its definition is complete only with the intersection of its joint children. 2) In general. A typical example with a filter is choosing a specific attribute on which to qualify. update. IBM DB2 and Microsoft SQL Server. as in “type login ID and password at the prompt. OR. Examples include "Region = Northeast" or "Revenue > $1 million". AND NOT. Inc. You can create multiple qualifications for a single filter or custom group. ratio The relationship in quantity. Qualifications are used in filters and custom groups.” qualification The actual condition that must be met for data to be included on a report.

City is a child attribute of State. analyze that data. and then present it in a visually pleasing manner. For example. See also: • • filter template report creation The process of building reports from existing. © 2007 MicroStrategy. predesigned reports in MicroStrategy Desktop or in MicroStrategy Web. See also: • • • • • • • • parent attribute child attribute partial relationship quality relationship one-to-one one-to-many many-to-one many-to-many report The central focus of any decision support investigation.Project Design Guide Glossary relationship An association specifying the nature of the connection between one attribute (the parent) and one or more other attributes (the children). a report allows users to query for data. Inc. report design The process of building reports from basic report components using the Report Editor in MicroStrategy Desktop or MicroStrategy Web. relationship 421 .

and transformations. hierarchies. In relational databases. metric. operators. facts. server definition A MicroStrategy object stored in the metadata containing information about the configuration of an Intelligence Server. filter. functions. usually by a project designer. tables.Glossary Project Design Guide row The horizontal axis of a report. and the relationships between fields and tables. . schema object A MicroStrategy object created. partition mappings. The attribute and fact columns in those tables are considered part of the schema itself. See also: • • axis column schema 1) The set of tables in a data warehouse associated with a logical data model. and so forth. 2) The layout or structure of a database system. Schema objects directly reflect the warehouse structure and include attributes. 422 row © 2007 MicroStrategy. shortcut object A MicroStrategy object that represents a link to any other MicroStrategy object such as report. the fields in each table. Inc. that relates the information in the logical data model and physical warehouse schema to the MicroStrategy environment. simple key In a relational database. server instance The combination of an Intelligence Server running with a particular server definition. which can be accessed from MicroStrategy Desktop. These objects are developed in MicroStrategy Architect. the schema defines the tables. a primary key that requires only one column to uniquely identify a record within a table.

numeric ascending. Structured Query The query language standardized in 1986 by the American Language (SQL) National Standards Institute (ANSI) and used to request information from tables in a relational database and to manipulate the tables’ structure and data. drill page-by pivot sort surf sort 423 .Project Design Guide Glossary sort Arranging data according to some characteristic of the data itself (alphabetical descending. star schema A highly denormalized physical warehouse schema in which lookup tables are consolidated so that every attribute ID and description column for a given hierarchy exists in one table. See also: • • • • • © 2007 MicroStrategy. See also: • • • • • drill page-by pivot subtotal surf source system Any system or file that captures or holds data of interest. Inc. subtotal A totaling operation performed for a portion of a result set. and so forth). statistics tables Tables that are used to record a variety of statistical information about the usage and performance of a MicroStrategy system.

attribute elements. table name space A field that is read from the warehouse catalog and used to organize databases. This is needed to uniquely identify each table saved in the project when comparing table information in the metadata to the real one in the warehouse. it is not explicitly created but is automatically deduced by the MicroStrategy platform from all information available to it.Glossary Project Design Guide surf To add filters. . Each table object in the metadata stores the name space or owner from which it came. Inc. 424 surf © 2007 MicroStrategy. metrics. metrics. The layout and format of these objects are defined within the template's view definition. Unlike a browse hierarchy. table size The estimated size of a database table in terms of number of rows. attributes. and functions to existing analysis objects. and so on) that defines the columns of data to be included in the result set. This field cannot be modified from the product since it is actually stored in the warehouse. template The data definition portion of the template consists of the group of objects (attribute. Compare user hierarchy. See also: • • • • • drill page-by pivot sort subtotal system hierarchy The superset hierarchy containing all attributes in a project. custom groups.

such as current month minus one month. Add a transformation for last year and the metric now calculates last year’s total sales. virtual cube 1) In an OLAP data model. format that cell to have a blue background with bold type. Although the vast majority are based on time. A virtual cube maps MicroStrategy objects such as hierarchies and metrics to OLE DB for OLAP objects. They are user-defined and are used to define the browse and drill relationships between attributes. applying an offset value. Unlike a physical cube. a transformation can also map different objects. transformation 425 . such as this year versus last year or current date versus month-to-date. 2) The result of mapping a logical data model to an OLE DB for OLAP multidimensional model after hierarchies and metrics have been selected from a project. Inc. arranged in specific sequences for a logical business organization. threshold Used to create conditional formatting for metric values. transformation metric An otherwise simple metric that takes the properties of the transformation applied to it. a conceptual. For example. such as defunct product codes to new ones. No physical cube is created or loaded.Project Design Guide Glossary transformation A schema object that maps a specified time period to another time period. multidimensional representation of data. but a definition of the virtual cube structure is stored in MicroStrategy metadata. a metric calculates total sales. a virtual cube does not perform data retrieval and consequently lacks the performance problems and size limitations associated with a physical cube. © 2007 MicroStrategy. Time transformations are used in metrics to compare values at different times. For example. if revenue is greater than $200. user hierarchy A named set of attributes and their relationships.

Glossary Project Design Guide 426 virtual cube © 2007 MicroStrategy. . Inc.

212 aggregate function defined on 247 aggregate table defined on 241 advantages 242 base table 244 compression ratio 248 effectiveness 248 integrate into project 249 logical table size 249 parent-child relationship 246 pre-aggregation 243 query frequency 246 aggregate-aware 249 aggregation defined on 243 degree of 244 dense 244 dynamic 243 sparse 244 alias attribute column 156 © 2007 MicroStrategy. fact column 96. 320 level 321 member property 321 relating objects 317 Analysis Services 2005 catalog 342 connecting to 340 DSI 342 hierarchy 326 relating objects to MicroStrategy 322 URL 342 427 . 180 allocation expression 121 Analysis Services 2000 catalog 339 connecting to 337 DSI 339 metadata models 317 relating objects to MicroStrategy 317 URL 339 Analysis Services 2000 to MicroStrategy cube 319 database 318 database instance 338 dimension 319. Inc. 105 table 178.INDEX A accessing Project Creation Assistant 78 Warehouse Catalog 219 adding tables to a project 79 aerial perspective of hierarchy 200.

MicroStrategy 294 atomic defined on 244 attribute defined on 10 Attribute Creation Wizard 129 Attribute Editor 135 browse form 190 cardinality 35 child 24 column alias 156 component. attribute constant 155 in hierarchy 25 joint child relationship 171 many-to-many relationship 160. report display form 190 role. 428 . See joint-child relationship. time-series 257 application for Essbase 313 application-level partition defined on 251 architecture. See report display form and browse form. derived attribute 150 derived expression 150 display 189 element. simple expression 148 system hierarchy 159 attribute component. Attribute Creation Wizard about 129 using 130 Attribute Editor about 135 creating attribute forms 146 creating attributes 136 updating hierarchies 197 attribute element defined on 23 about 140 © 2007 MicroStrategy. Inc. 128 qualification 253 ratio 35 relationship. See attribute role. expression 127 filtering in a hierarchy 203 form. See attribute element. 164 MicroStrategy to Analysis Services 2000 321 MicroStrategy to Analysis Services 2005 326 MicroStrategy to Essbase 315 MicroStrategy to SAP BW 307 multiple counting in relationship 166 nonrelated 161 one-to-many relationship 160 one-to-one relationship 160 overview 22 parent 24 properties 127.Index Project Design Guide Analysis Services 2005 to MicroStrategy cube 322 database 323 database instance 341 dimension 325 level 326 member 326 member property 327 perspective 324 relating objects 322 analysis. See attribute relationship. See report display form and browse form. See attribute form. heterogeneous mapping 153 identifying 30 implicit. compound 183 compound key 184 creating in Project Creation Assistant 130 creating using Attribute Editor 136 cross-dimensional.

. characteristic attribute vs. Inc. 223 base fact column 47 data type. derived fact 47 description 41 fact 41 heterogeneous naming 49 homogeneous naming 50 ID 41 physical warehouse schema 40. See hierarchy. attribute form 307 characteristic value 307 characteristics. column defined on 41. 41 column alias attribute 156 429 B base fact column 47 base table defined on 244 pre-aggregation 243 BI architecture 2 browse attribute 207 form 190 browsing © 2007 MicroStrategy. 180 authenticating OLAP cube reports 297 automatic attribute role recognition 177 about 207 enabling in a hierarchy 209 building a logical data model 26 business intelligence (BI) system defined on 1 C calculating growth percentage 257 variance 257 calculating logical table sizes 231 cardinality for an attribute 35 Cartesian join 159 catalog for Analysis Services 2000 318 for Analysis Services 2005 323 for Essbase 313 for SAP BW 304 SQL 234 category. See column data type. See hierarchy.Project Design Guide Index for Analysis Services 2000 321 for Analysis Services 2005 326 for Essbase 316 for SAP BW 307 overview 23 attribute form defined on 37 creating using Attribute Editor 146 display 189 expression 147 for Analysis Services 2000 321 for Analysis Services 2005 327 for Essbase 316 for SAP BW 307 group 186 qualification 253 attribute relationship defined on 24 about 159 as property of attribute 127 identifying 31 in lookup table 44 overview 24 attribute role defined on 175 automatic recognition 179 automatic recognition of 177 explicit table alias 178. SAP BW 300 child attribute 24 class.

Inc. See logical data model. creating for OLAP cube 359 compression ratio defined on 248 Configuration Wizard 71 connecting to a database 227 to Analysis Services 2000 337 to Analysis Services 2005 340 to Essbase 334 to SAP BW 327 consolidating lookup tables 58 constant attribute 155 creating attributes 136 compound attributes 184 compound metric for OLAP cube 359 facts 87 logical data model 26 project 75 creating hierarchies 194 cross product join 116 cross-dimensional attribute. 209 data model. cube 319 for Analysis Services 2000 319 for Analysis Services 2005 324 for Essbase 314 for SAP BW 304 mapping 349 customizing catalog SQL 233 D Data Explorer defined on 209 about 209 enabling hierarchy browsing 196. See joint child relationship. . data slice 253 data source defined on 6 data type and mapping 395 Big Decimal 400 changed in column 240 high-precision 400 warehouse catalog 397 data warehouse defined on 5 and physical schema 39 connecting to 72 schema type 51 structure 51 Warehouse Catalog 218 database 323 connection operations 227 custom login 227 gateway support 225 instance. See project source. 105 column data type changed 240 manually setting for OLAP cube 352 compound attribute defined on 183 creating 184 compound key defined on 42 and compound attributes 184 compound metric. read operations 227 secondary 225 database instance defined on 67 for Analysis Services 2000 338 for Analysis Services 2005 341 for Essbase 335 for SAP BW 329 for SAP BW (UNIX/Linux) 333 database management system 233 degradation defined on 118 dense aggregation 244 derived 430 © 2007 MicroStrategy. See database instance.Index Project Design Guide fact 96. data provider.

level 107 extraction. attribute 140 entity relationship diagram (ERD) defined on 29 entity. transformation. and loading (ETL) process defined on 4. 315 for SAP BW 306 See also hierarchy. member 316 relating objects 311 ETL. 105 creating 87 cross product join 116 degradation defined on 118 derived 99 derived fact column 47 disallowing 122 expression 98 extension 107 Fact Creation Wizard 88 fact definition 96. Essbase catalog 337 connecting to 334 database instance 335 DSI (DataSourceInfo) 336 metadata models 311 relating objects to MicroStrategy 311 URL 336 Essbase to MicroStrategy application 313 database 313 dimension 314. direct access approach 292 disallowing fact entry level 122 drilling using hierarchies 209 dynamic aggregation 243 dynamic relationship defined on 247 E element. 97 Fact Editor 88. 92 fact entry level 87 431 . 180 expression map 98 expression. See hierarchy. See extraction. dimension for Analysis Services 2000 319. See MicroStrategy Desktop. and loading.Project Design Guide Index attribute 150 fact 99 fact column 47 description column defined on 41 Desktop. example data model sample 26 physical schema 289 project 267 table data sample 225 explicit table alias 178. See entity relationship diagram. 6 F fact defined on 85 allocation expression 121 base fact column 47 column defined on 41 column alias 96. Inc. transformation. 315 level 315 © 2007 MicroStrategy. entry level defined on 87 entry point 205 ERD. 320 for Analysis Services 2005 325 for Essbase 314. fact 98 expression-based transformation 259 creating 261 member expressions 264 member tables 263 extension.

See fact table. 210 Hierarchy Viewer 200 © 2007 MicroStrategy. fact column defined on 41 base 47 derived 47 heterogeneous 102 Fact Creation Wizard 88 Fact Editor 88. 107 overview 21 table 46 table relation 110 table. structure 199 system hierarchy 197 unbalanced 355 user hierarchy 197 Hierarchy Editor 198. 200.Index Project Design Guide fact relation 114 heterogeneous fact column 102 identifying 29 implicit 99 in hierarchy 25 level extension 96. 93 fact expression 98 fact table defined on 86 column naming 51 in a warehouse 46 level 48 overview 21 filtered hierarchy 203 flag 172 form attribute form 143 expression 147 group 186 G gateway support for database 225 growth percentage calculation 257 H heterogeneous attribute mapping 153 column naming defined on 49 432 fact column 102 partition mapping 252 hierarchy defined on 193 aerial perspective 212 and the Data Explorer 196. . 210 Hierarchy Viewer 200 in a logical data model 25 in SAP BW 300 limited 202 locked 201 organization 198 Project Creation Assistant 197 ragged 355 See also dimension. 200. 209 Attribute Editor 197 attribute filter 203 attributes in 25 browse attribute 207 browsing 207 browsing. enabling 209 creating 194 defining 32 displaying 201 drilling 209 entry point 205 facts in 25 filtering attributes in 203 for Analysis Services 2000 320 for Analysis Services 2005 326 for Essbase 315 for SAP BW 306 Hierarchy Editor 198. Inc.

See Essbase. 280 ratio 35 sample 26 schema type 51 source of structure 29 unique identifier 34 Logical Table Editor 250 logical table size 249 login. 344 InfoCube 303. 254 Hyperion Essbase. cross product 116 joint child attribute transformation metrics 265 joint child relationship 171 joint children defined on 171 for Analysis Services 2005 326 for Essbase 315 virtual 306 limited hierarchy 202 locating OLAP cubes 348 locked hierarchy defined on 201 logical data model defined on 17 attributes in 24 building 26 cardinality 35 conventions 33 design factors 59 for MicroStrategy Tutorial 271. . 304 InfoObjects 299 InfoProviders 299 international technical support xxiii J Java Connector 328.Project Design Guide Index highly denormalized schema 57 higher level lookup tables 58 highly normalized schema 52 homogeneous column naming 50 partition mapping 252. Inc. custom 227 lookup table defined on 43 attribute relationships and 44 consolidating 58 many-to-many relationship 44 one-to-one relationship 44 K key compound 42 figures 300 simple 42 M managed object 349 managed objects OLAP cubes 348 many-to-many relationship defined on 160 design considerations 164 example 32 lookup table 44 relate table 45 many-to-many transformation 433 L level extension 107 for Analysis Services 2000 321 © 2007 MicroStrategy. I implicit attribute 155 fact 99 importing OLAP cubes 343. 330 join.

Index Project Design Guide and table-based transformations 259 double-counting 264 mapping OLAP cubes 343 OLAP cubes examples 358 schema objects in Warehouse Catalog 231 mapping type about 264 many-to-many 264 one-to-one 264 MDX. MicroStrategy architecture 294 object model 7i 295 object model 8 296 MicroStrategy Desktop 11 MicroStrategy metadata. See member property. See MultiDimensional Expressions. tables 263 member property for Analysis Services 2000 321 for Analysis Services 2005 327 metadata defined on 8 connecting to 72 shell 65 table 71 metadata model Analysis Services 2000 317 Essbase 311 SAP BW 302 metadata partition mapping attribute qualification 253 data slice 253 overview 251 versus warehouse partition mapping 255 metadata shell defined on 65 metric creating compound metrics for OLAP cube data 359 creating with custom MDX 359 prompts within custom MDX 366 removing compound metrics from OLAP cubes 368 transformations 258 Microsoft Analysis Services 2000. Inc. See Analysis Services 2005. MicroStrategy to Analysis Services 2000 317 attribute 321 attribute element 321 attribute form 321 catalog 318 cube 319 dimension 320 hierarchy 320 MicroStrategy to Analysis Services 2005 322 attribute 326 attribute element 326 attribute form 327 catalog 323 cube 324 dimension 325 hierarchy 326 MicroStrategy to Essbase 311 434 © 2007 MicroStrategy. member attributes 263 expressions 263 for Analysis Services 2000 321 for Analysis Services 2005 326 for Essbase 316 property. See Project Builder. See metadata. . See Analysis Services 2000. MicroStrategy Project Builder. Microsoft Analysis Services 2005.

user 10 ODS object 299 OLAP BAPI certification 293 Cube Catalog 309 Cube Editor 349 cube. MultiDimensional Expressions about 291 remapping objects 356 multiple counting 164 MultiProviders 299 O object models in MicroStrategy 7i 295 in MicroStrategy 8 296 using SAP direct access 296 object. 435 . 55 © 2007 MicroStrategy. See OLAP cube. 280 physical warehouse schema 281 schema. Inc.Project Design Guide Index attribute 315 attribute element 316 attribute form 316 catalog 313 cube 314 dimension 314 hierarchy 315 MicroStrategy to SAP BW 302 attribute 307 attribute element 307 attribute form 307 catalog 304 cube 304 dimension 306 hierarchy 306 MicroStrategy Tutorial 267 data model. OLAP cube defined on 343 creating compound metrics 359 creating metrics with custom MDX 359 importing 344 integration 292 manually setting column data type 352 mapping 349 prompts within custom MDX metrics 366 remapping 356 removing 347 removing compound metrics 368 searching for 348 source 291 unbalanced and ragged hierarchies 355 OLAP Cube Catalog 309. general 280 view physical schema 289 MicroStrategy Web Universal 13 migrating tables 232 moderately normalized schema 54 MOLAP defined on 242 multidimensional data model. 343 OLAP Cube Editor 349 OLAP cube reports authentication 297 managed objects 348 OLTP 3 one-to-many relationship defined on 160 example 31 relate table 45 N nonrelated attributes 161 normalized schema 53. viewing 279 logical data model 271. See logical data model.

. 80 removing tables from 80 sample project 267 schema 216 source. in metrics with custom MDX 366 properties for SAP BW 311 Q qualification for an attribute form 253 quality. 197 project source defined on 65 connecting to 72 creating 77 prompt. defined on 255 types 251 warehouse 254. 255 partition mapping defined on 250 application-level 251 attribute qualification 253 data slice 253 heterogeneous 252 homogeneous 252. Inc. 436 pre-aggregation defined on 243 aggregate table 241 base table 244 compression ratio 248 integrate aggregate table 249 logical table size 249 parent-child relationship 246 query frequency 246 prefix 230 project defined on 14 adding tables to 79. See OLTP. See OLAP. 80 aggregate table. perspective 324 physical warehouse schema defined on 39 design factors 59 for MicroStrategy Tutorial 281 sample 289 planning a project 76 PMT.See ODS object. P parent attribute 24 parent-child relationship 246 dynamic 247 overview 25 static 247 partition base table defined on 251. 255 partition base table 255 server-level 251 table 222. managing 220 Warehouse Catalog 79 warehouse tables in 79 Project Builder 74 Project Creation Assistant 77. © 2007 MicroStrategy. 255 PBT. integrating 248 creating 75 data warehouse 79 integrating aggregate tables 248 managing tables for 220 planning 76 Project Builder 74 Project Creation Assistant 78. opening Project Creation Assistant 78 Warehouse Catalog 219 Operational Data Store object. online transaction processing. 254 metadata 251. See project source tables. See joint child relationship.Index Project Design Guide one-to-one relationship defined on 160 lookup table 44 online analytical processing. See partition base table. See partition mapping table.

304 relating objects 302 virtual level 306 SAP.sh 331 structures 311 terminology 298 variable properties 309 variables 300. 333 hierarchies 300 InfoObjects 299 InfoProviders 299 Java Connector 328. relationship dynamic 247 many-to-many 164 parent-child 246 relate table 45 static 247 remapping OLAP cubes 356 removing compound metric from OLAP cube 368 OLAP cube 347 table from project 80 report display form 190 row count for table 230 S SAP BW characteristics 300 connecting to 327 on UNIX/Linux 330 on Windows 328 database instance 329.sh.Project Design Guide Index query cubes 299 query frequency 246 R ragged hierarchy 355 ratio for an attribute 35 RDBMS defined on 5 server-level partitioning 251 read operations for database 227 relate table 45 related attributes. fact 114 relational database management system. configuring 331 schema for project 216 highly denormalized 57 highly normalized 53 MicroStrategy Tutorial project 280 moderately normalized 55 object 14 physical warehouse defined on 39 star 58 © 2007 MicroStrategy. 308 SAP BW to MicroStrategy characteristic attribute 307 characteristic value 307 characteristics 305 hierarchy 306 InfoCube 303. See attribute relationship. See RDBMS. 330 key figures 300 mapping cubes 349 metadata models 302 OLAP Cube Catalog 309. 343 query cubes 299 relating objects to MicroStrategy 302 SAP. 437 . Inc. relating objects to MicroStrategy from Analysis Services 2000 317 from Analysis Services 2005 322 from Essbase 311 from SAP BW 302 relation.

86 key 42 Logical Table Editor 250 lookup 43. 28 sparse aggregation 244 SQL defined on 5 attributes and columns in 22 catalog 233 default catalog SQL 239 facts and columns in 21 star schema 58 static relationship defined on 247 structure in SAP BW query cube 311 of hierarchy 199 of table 222 Structured Query Language. 180 calculating logical sizes 231 calculating size 231 compound key 42 fact table defined on 46. time-series analysis 257 transformation defined on 258 components 263 double-counting 264 expression-based 259. 44 managing for a project 221 migrating 232 name space 222. system hierarchy 159.Index Project Design Guide type. Inc. See technical support. See joint child relationship. updating 217 schema type 51 comparison 60 searching for OLAP cubes 348 server-level partitioning 251 simple expression 148 key 42 source system defined on 3. 5. . summary table 241 support. 228 name spaces 230 physical warehouse schema 40 prefixes 230 primary key 42 relation 110 row counts 230 sample data 225 simple key 42 size defined on 249 summary 241 transformation 259 updating structure 223 viewing structure 222 warehouse tables in Project Creation Assistant 79 table-based member expressions 264 transformations 259 creating 260 member tables 263 technical support xxv international xxiii text fact. 261 many-to-many 259 mapping types 264 member attributes 263 member expressions 263 member tables 263 438 © 2007 MicroStrategy. See SQL. See schema type. defined on 197 T table adding to a project 79 aggregate 241 alias 178.

Inc. 260 transformation metric defined on 258 joint child attributes 265 troubleshooting column data type changed 240 column missing 241 data warehouse connection 239 tables missing 240 V variables overview 300 properties. See transformation metric. metrics 258 one-to-one mapping types 264 table-based 259. enabling 209 creating 194 displaying 201 drilling 209 entry point 205 filtering attributes in 203 limited 202 locked 201 structure 199 user object 10 using attribute form vs characteristic attribute 158 © 2007 MicroStrategy. user hierarchy defined on 197 browse attribute 207 browsing 207 browsing. See fact expression.Project Design Guide Index metric. W Warehouse Catalog accessing 219 column missing 241 connection operations 227 data types 240 database gateway support 225 default catalog SQL 239 displaying information 230 managing 221 mapping schema objects 231 read operations 227 troubleshooting 239 updating table structure 223 usage and settings 218 viewing table structure 222 warehouse partition mapping overview 254 partition base table 255 partition mapping table 255 versus metadata partition mapping 255 warehouse table in Project Creation Assistant 79 439 . setting 311 supporting 308 variance calculation 257 viewing sample data model 279 sample table data 225 sample warehouse schema 289 table structure 222 virtual level 306 U unbalanced and ragged hierarchy 355 unique identifier 34 UNIX/Linux. connecting to SAP BW 330 updating project schema 217 updating table structure 223 URL for Analysis Services 2000 339 for Analysis Services 2005 342 for Essbase 336 user defined object.

connecting to SAP BW 327 X XMLA 293 Analysis Services 2000 317 Analysis Services 2005 322 Essbase 312 provider for Analysis Services 2000 338 provider for Analysis Services 2005 341 provider for Essbase 335 440 © 2007 MicroStrategy. physical schema defined on 39. . Inc.Index Project Design Guide warehouse. 281 Windows.

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.