Book Image

SQL Server Analysis Services 2012 Cube Development Cookbook

Book Image

SQL Server Analysis Services 2012 Cube Development Cookbook

Overview of this book

Microsoft SQL Server is a relational database management system. As a database, it is a software product whose primary function is to store and retrieve data as requested by other software applications. SQL Server Analysis Services adds OLAP and data mining capabilities for SQL Server databases. OLAP (online analytical processing) is a technique for analyzing business data for effective business intelligence. This practical guide teaches you how to build business intelligence solutions using Microsoft’s core product – SQL Server Analysis Services. The book covers the traditional multi-dimensional model which has been around for over a decade as well as the tabular model introduced with SQL Server 2012. Starting with comparing MultiDimensional and tabular models – discussing the values and limitations of each, you will then cover the essential techniques for building dimensions and cubes. Following on from this, you will be introduced to more advanced topics, such as designing partitions and aggregations, implementing security, and synchronizing databases for solutions serving many users. The book also covers administrative material, such as database backups, server configuration options, and monitoring and tuning performance. We also provide a primer on MultiDimensional eXpressions (MDX) as well as Data Analysis expressions (DAX) languages. This book provides you with data cube development techniques, and also the ongoing monitoring and tuning for Analysis Services.
Table of Contents (19 chapters)
SQL Server Analysis Services 2012 Cube Development Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Managing database-level security


Each SSAS instance could be shared for multiple projects. As long as databases can fit on the data drive and SSAS can handle processing and querying requests efficiently, there is no reason why you couldn't have many databases on a single instance. This is particularly true in development and quality assurance environments. Since each instance could be shared by multiple developers, it's generally best to provide each developer with the necessary permissions for the database that he/she is responsible for instead of granting unlimited server-wide permissions.

Database-level security is implemented through roles within each SSAS database. Each database can have many roles, normally one role per group of users that needs a specific level of access. Keep in mind that SSAS permissions are additive; if a user belongs to multiple groups, he/she will have all permissions available to each of the groups that he/she is a part of.

How to do it...

To define database-level...