Technical Training
Analysis Services TrainingTable of Contents
MSAS: Defining Cube Properties
MSAS: Defining Cube Properties - Page 2
MSAS: Defining Cube Properties - Page 3MSAS: Defining Cube Properties Page - 3
MSAS: Defining Cube Properties
Enabling write-back for a cube
Aggregation values of a cube cannot be changed without making the cube internally inconsistent. Values can be written only to the lowest levels of a cube. Incremental change values are written either to the client cache in the PivotTable service or to a special write back table in the relational database by Analysis services. Then, the write back values are dynamically combined with any values in the fact table for the end user.
To write back values to a cube, the client application must have write back capabilities. The browsers in Analysis services and in Microsoft Office 2000 do not have write back capabilities.
Values can be written back to a cube permanently or temporarily. To write back values temporarily during a what-if analysis users may use macros with the PivotTable service. Such written back values will not be visible to other users of the cube and hence will be private. To make the write back visible to other users, the cube must be write enabled.
Write-enabling a cube means to specify a location of a relational table where the write back values will be stored. It may be noted that the user need not write the data back to the same data source as the one containing the fact table. Because the write-back values are stored in a relational table the tools of the relational database system can be used to append the values to original fact table. Then the cube can be processed in Analysis Manager and the write-back data can be deleted. We will be learning more about write back in “Actions, Drillthrough and Writeback” lesson.
Dynamically adding members to a Dimension
The Dimension browser in the Analysis Manager allows the user to add values to a dimension. Unlike writing back values to a cube—where values are stored in a relational table—the new member in the Dimension table is added directly to the original dimension table. The only condition being that the user must have write permissions. This ability to dynamically add members is useful in planning applications. The advantage is that the cube need not even be reprocessed before the new member can be used for analysis.
Removing Dimensions and measures from a cube:
This is a feature that is associated with the virtual cube in Analysis services. The virtual cube is like the view of the relational database system. It is restrictive and is intended to be used like a view in a sense. However, unlike a view, whole dimensions and measures will have to be excluded if the view of data is to be restricted. It is not possible to partially limit the view of a dimension. The advantage is that the virtual cube can be used to combine data from more than one cube. Calculated members can be imported from source cube into a virtual cube when the members used by the calculated member are contained in the cube. A virtual cube can be created using the Virtual cube editor. We will learn more about this in the lesson “Working with Virtual cubes”.
Using the Disabled Property
The disabled property is really the property of a level, but it only exists only within the cube editor. The purpose of the property is to enable the user disable a level from the dimension of a cube whenever he does not require the data in the level. The dimensions of the cube may be shared by other cubes, but the disable property disables the levels only for the cube in hand and not for the other cubes which share the data. For instance if a user does not want to have the lower levels of a product table and only needs the Quarters of a year in the time dimension he can disable the other levels and use only the top levels of the two tables for data analysis. The other levels will be available for other cubes that share the dimension. To disable a level in the dimension, the user should expand the dimension, select the level and set the disabled property to “Yes”

The cube has to then be processed for the disabled property to take effect.
In this lesson we have looked at cubes, measures and properties of cubes and measures and also learnt how to work with cubes, measures and the properties of cubes. In the next lesson we shall look at “Managing Storage and Optimization”
Analysis Services Training
- MSAS - Browsing the Dependency Network
- MSAS - Building a Relational Decision Tree Model
- MSAS - Introduction to Data Mining
- MSAS - Applying security to a Dimension
- Tutorial 65: MSAS - Managing Cube Roles
- MSAS - Understanding Database Roles
- MSAS - Securing User Authentication
- MSAS - Introducing Analysis Services Security
- MSAS - Writebacks
- MSAS - Defining and Creating Drillthrough
- MSAS - Defining and Creating Auctions
- MSAS - Creating and Maintaining Calculated Members in Virtual Cubes
- MSAS - Building a Virtual Cube
- MSAS - Understanding Virtual Cubes
- MSAS - Introducing Solve Order
- MSAS - Implementing Calculations Using MDX Part 2
- MSAS - Implementing Calculations Using MDX Part 1
- MSAS - Merging Partitions
- MSAS - Introduction and Managing Partitions
- MSAS - Troubleshooting Cube Processing
- MSAS - Optimizing Cube Processing
- MSAS - Processing Dimensions and Cubes
- MSAS - Introducing Dimension and Cube Processing
- MSAS: Optimization Tuning Part 2
- MSAS: Optimization Tuning Part 1
- MSAS: Usage-Based Optimization
- MSAS: Analysis Services Aggregations
- MSAS: The Storage Design Wizard
- MSAS: Analysis Server Cube Storage
- MSAS: Defining Cube Properties
- MSAS: Introduction and Working with Measures
- MSAS: Introduction and Working with Cubes
- MSAS: Virtual Dimensions
- MSAS: Introducing Member Properties
- MSAS: Creating Custom Rollups
- MSAS: Creating a Time Dimension
- MSAS: Understanding Hierarchies
- MSAS: Dimension Storage Modes and Levels
- MSAS: Working with Levels and Hierarchies
- MSAS: Working with Parent-Child Dimensions
- MSAS : Basics of Levels
- MSAS : Working with Standard Dimensions
- MSAS : Shared vs Private Dimensions
- Understanding Dimension Basics
- MSAS : Office 2000 OLAP Components
- MSAS : Client Architecture
- MSAS : Cube Storage options
- MSAS : Meta data Repository
- MSAS : Analysis services Tools for Extended Functionality
- MSAS : The Wizards
- MSAS : The Analysis Manager and Analysis Server
- MSAS : The Data warehousing framework of SQL Server 2000 - Part 2
- MSAS : The Data warehousing framework of SQL Server 2000 - Part 1
- MSAS : Microsoft Data Warehousing Overview
- MSAS : Browsing the Cube
- MSAS : Designing Storage and Processing the Cube
- MSAS : Building the Cube Part #3
- MSAS : Building the Cube Part #2
- MSAS : Building the Cube Part #1
- MSAS : Setting up the Database in Analysis Server
- MSAS : Preparing to Create the Cube
- MSAS : Introducing Analysis Manager Wizards
- Microsoft Analysis Services Installation
- MSAS - Applying OLAP Cubes
- Understanding OLAP Models
- Designing the Dimensional Model and Preparing the data for OLAP
- Design of the data warehouse: Kimball Vs Inmon
- Defining OLAP Solutions and Data Warehouse design
- Microsoft Analysis Services Training
- Data Warehouse database and OLTP database
- Introduction to Data Warehousing







