SQL Server 2005 Analysis Services Tutorial
Welcome to the Microsoft SQL Server 2005 Analysis Services (SSAS) Tutorial. Data warehouse developers use Business Intelligence Development Studio to develop and deploy Analysis Services projects, and use SQL Server Management Studio to manage these projects. This tutorial describes how to use BI Development Studio to develop and deploy an Analysis Services project, using the fictitious company Adventure Works Cycles for all examples.
What You Will Learn
In this tutorial, you will learn how to define data sources, data source views, dimensions, and cubes in an Analysis Services project within BI Development Studio. You will also learn how to view a cube by deploying the Analysis Services project to an instance of Analysis Services and then processing the deployed objects. You will also learn how to modify the measures, dimensions, hierarchies, attributes, and measure groups in the Analysis Services project, and how to then deploy the incremental changes to the deployed cube on the development server. Finally, you will learn how to define calculations, Key Performance Indicators (KPIs), actions, perspectives, translations, and security roles.
Requirements
The following components, samples, and tools are required to complete this tutorial:
- Microsoft SQL Server 2005 Database Engine
- Microsoft SQL Server 2005 Analysis Services (SSAS)
- Business Intelligence Development Studio
- The AdventureWorks database, which is included with SQL Server 2005. By default, the sample databases are not installed, to enhance security. For more information about installing the sample databases, see Running Setup to Install AdventureWorks Sample Databases and Samples
For information about how to install these components, samples, and
tools, see
Additionally, the following prerequisites must be met to successfully complete this tutorial:
- You must be a member of the Administrators local group on the Analysis
Services computer or be a member of the Server role in the instance of Analysis
Services.
- You must have Read permissions in the SQL Server 2005 AdventureWorks DW
database.
This tutorial is divided into ten lessons. Each lesson is intended to require approximately one hour to complete.
Note: |
|---|
| When you start Lesson 4, you will use an enhanced version of the cube that you define in Lessons 1 through 3. That project and a project completed through Lesson 6 are included when you install the Analysis Services Tutorial sample projects, so that you can start this tutorial at Lesson 4 or Lesson 7 if you do not want to start at Lesson 1. |
- Lesson 1: Defining a Data Source View within an Analysis Services Project
-
In this lesson, you define a data source view within an Analysis Services project by using BI Development Studio.
- Lesson 2: Defining and Deploying a Cube
-
In this lesson, you define a cube and its dimensions by using the Cube Wizard, and then deploy the cube to the local instance of Analysis Services.
- Lesson 3: Modifying Measures, Attributes and Hierarchies
-
In this lesson, you improve the user-friendliness of the cube and incrementally deploy the related changes, processing the cube and its dimensions as needed.
- Lesson 4: Defining Advanced Attribute and Dimension Properties
-
In this lesson, you define a referenced dimension relationship, order attribute members by using composite keys, and define custom error handling.
- Lesson 5: Defining Relationships Between Dimensions and Measure Groups
-
In this lesson, you define a fact relationship for a degenerate dimension and define a many-to-many relationship.
- Lesson 6: Defining Calculations
-
In this lesson, you define calculated members, named sets, and scripts.
- Lesson 7: Defining Key Performance Indicators (KPIs)
-
In this lesson, you define Key Performance Indicators (KPIs).
- Lesson 8: Defining Actions
-
In this lesson, you define actions.
- Lesson 9: Defining Perspectives and Translations
-
In this lesson, you define views of a cube and translations of metadata.
- Lesson 10: Defining Administrative Roles
-
In this lesson, you define administrative and user roles.
