Essbase11_Creating Aggregate Storage Applications

© 2005 Hyperion Solutions Corporation. All Rights Reserved.

Hyperion Essbase 7X: New Features

Creating Aggregate Storage Databases

2


Objectives

At the end of this lesson, you should be able to:

• Create a new aggregate storage database

• Create an aggregate storage database from an existing block storage database

• Apply dimension and member properties

• Describe aggregate storage hierarchy options

• Convert block storage outlines to aggregate storage outlines


Creating a New Database

• Four steps:1. Create application and database.2. Build dimensions.3. Load data to query database.4. Optional. Aggregate to query faster.

• Eight-character name restriction

• Reserved names:− default− log− metadata− temp

• One aggregate storage database per application


Application and Database Trees

• Calculation scripts

• Secondary databases

• Currency databases

Aggregate Storage Block Storage


Directory Structures

• Different directory structures

• Principal database objects− .OTL− .RUL− .CSC− .REP

• CSC: Similar purpose,different structure

Block StorageAggregate Storage


Creating Outline with Rules Files

• Rules files support:−File-based−SQL-based

• Only define ASO properties−BSO properties ignored if selected

• Converting BSO −Open and validate before use


Hierarchy Options Overview

Aggregate storage databases support:

• Stored hierarchies

• Dynamic hierarchies

• Multiple hierarchies

• Alternate hierarchies−Attribute dimensions−Hierarchies of shared members


Stored Hierarchies

• Members are aggregated according to the dimension hierarchy.

• Restriction types:−Dimension−Member−Label Only member

• You cannot specify the Accounts dimension as a stored hierarchy.

Dimension

Level_1_2

Level_0_3

Level_2_1

Level_1_1

Level_0_1

Level_0_2

Label Only

Label Only

Stored

+

~

Label Only

+

+

+

~

Level_0_4 +

Label Only


Dynamic Hierarchies

• Members are calculated based on the value of the member solve order property.

• Advantages:−Any consolidation operator−Member formulas−Label Only members at any level

Years

Curr Year

Prev Year

Variance

Dynamic

~

~

+

Variance % ~

[20: [Curr Year]-[Prev Year]]

[20: ([Curr Year]-[Prev Year])/[Prev Year]*100]

Label Only


Multiple Hierarchies

You can combine stored and dynamic hierarchies into one dimension.

Time

QTD

QTD(Jan)

MTD

Jan

Label Only

Multiple Hierarchies Enabled

+

+

+

Dynamic

QTD(Feb) ~

Label Only

Feb +

~

[0: [Jan]]

[0: [Jan] + [Feb]]

Stored


Setting Hierarchy Types

Assigned Hierarchy Type

Hierarchy TypeButtons


Attribute Dimensions

• You can build alternate hierarchies by creating attribute dimensions.

• Restrictions:−Attribute Calculations dimension

contains only the Sum member.−Attribute dimensions do not

have hierarchy types.−The base members must be at

the same level.

Stores

Great Buys

Radio Hut

Stored

+

+

{Square Footage}

{Square Footage: 1500}

{Square Footage: 450}

Square Footage

450

750

Attribute [Type: Numeric]

1500

2500


Hierarchies of Shared Members

• You can build alternate hierarchies by creating hierarchies that include shared members.

• Rules:−Common−Stored hierarchies−Multiple hierarchies


Specifying the Accounts Dimension

• The Accounts dimension−Can be one per database− Is considered a dynamic hierarchy−Supports

−All unary operators−MDX-based member formulas

• Guidelines to select an Accounts dimension:−Choose flat dimension that has less than 3 levels−Of two equally flat dimensions, select the denser−Of two equally flat, dense dimensions, select the larger dimension

• Consider an outline with no Accounts dimension if:−Low probability that data exists−All dimensions have hierarchies of more than two levels


Understanding Database Restructuring

Restructureand Clear

Restructure Only

Add/delete/move, dimension/member Add or delete a formula, level 0 Add/delete/move, attribute dimension Add/delete/move, attribute member Add/delete a formula upper level Add/delete alias, comment or UDA Rename a member or dimension Associate/disassociate, attribute dimension


Converting Block to Aggregate

1. Convert block outline using wizard

2. Load data into new aggregate application

3. Query ASO application

4. Optional. Expand functionality with a transparent block partition


Using the Outline Conversion Wizard

• Select source outline

• Verify corrections to outline

• Select destination

• Correction modes

• Confirm completion


Creating Databases Using MaxL

• Create a new aggregate storage application and database:

• Convert a block storage application to an aggregate storage application

create application Sample2 using aggregate_storage;

create or replace outline on aggregate_storage database Sample2.Basic2 as outline on database sample.basic;


Summary

In this lesson, you should havelearned how to:

• Create a new aggregate storage database

• Create an aggregate storage database from an existing block storage database

• Apply dimension and member properties

• Describe aggregate storage hierarchy options

• Convert block storage outlines to aggregate storage outlines

Essbase11_Creating Aggregate Storage Applications

Documents