Book Image

Expert Cube Development with Microsoft SQL Server 2008 Analysis Services

Book Image

Expert Cube Development with Microsoft SQL Server 2008 Analysis Services

Overview of this book

Microsoft's SQL Server Analysis Services 2008 is an OLAP server that allows users to analyze business data quickly and easily. However, designing cubes in Analysis Services can be a complex task: it's all too easy to make mistakes early on in development that lead to serious problems when the cube is in production. Learning the best practices for cube design before you start your project will help you avoid these problems and ensure that your project is a success. This book offers practical advice on how to go about designing and building fast, scalable, and maintainable cubes that will meet your users' requirements and help make your Business Intelligence project a success. This book gives readers insight into the best practices for designing and building Microsoft Analysis Services 2008 cubes. It also provides details about server architecture, performance tuning, security, and administration of an Analysis Services solution. In this book, you will learn how to design and implement Analysis Services cubes. Starting from designing a data mart for Analysis Services, through the creation of dimensions and measure groups, to putting the cube into production, we'll explore the whole of the development lifecycle. This book is an invaluable guide for anyone who is planning to use Microsoft Analysis Services 2008 in a Business Intelligence project.
Table of Contents (17 chapters)
Expert Cube Development with Microsoft SQL Server 2008 Analysis Services
Credits
About the Authors
About the Reviewers
Preface
Index

Sample security requirements


Before diving into technical details, let's outline the sample set of security requirements that we will use in this chapter to illustrate how security can be implemented.

Imagine we are building a BI solution for a multinational company, and we want to give employees and partner companies all over the world access to our cube. Here's what we will need to do:

  • We need to restrict access by Country: Canadian users will be able to see only Canadian data, French users will only be able to see data for France, and so on.

  • We need to restrict access by Reseller. So if users from the "Roadway Bicycle Supply" reseller query the cube, they will only be able to see their sales and will have no access to other resellers' information. We will demonstrate two different ways to handle this requirement.

  • We need to restrict access to certain Measures, both real and calculated.

In a real-world project the security requirements must be agreed with the customer and they should be specified...