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

Security and query performance


Applying security to a cube comes at a cost to query performance. However, since we don't usually have a choice about whether to apply security or not, we then need to understand which security features have the least impact on performance when choosing which ones to use. In this final section we'll give some details on the relative impact on query performance of each type of security.

Cell security

Cell security has by far the biggest negative impact on query performance, and for this reason alone it should only be used when there is no other option. Also remember that there are two different types of cell security, Read and Read Contingent; Read Contingent cell security has more impact on query performance than Read. The reason why cell security is so bad is because it prevents Analysis Services from using many important query optimization techniques (for example, in many cases it appears to completely prevent the use of the Formula Engine cache, so the results...