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

Chapter 9. Securing the Cube

Security, for an Analysis Services cube, is a very important issue and one that needs to be properly understood and implemented. It's almost always the case that some form of security needs to be in place: the data in the cube may be extremely sensitive. For example, if a cube contains sales data for a whole company, we may need to make sure that each sales person can only view his or her own sales and no-one else's; equally, if a cube contains data regarding the profitability of a company it's likely we'll need to ensure that only the finance department and the board have access to it.

Ignoring security during the initial analysis phase will inevitably lead to problems during the deployment of the solution. We can't stress this enough: security must be planned for in advance; it is such a complex issue that it cannot simply be left until the cube is in production.

In this chapter we will discuss the Analysis Services security model, exploring the different ways...