Book Image

Getting Started with SQL Server 2012 Cube Development

Book Image

Getting Started with SQL Server 2012 Cube Development

Overview of this book

Analysis Services have been the number one OLAP engine for years. With the increased focus on business intelligence solutions, there is a shortage of professionals in this area. Start your journey into becoming a BI developer using the popular tools included in every SQL Server installation. Getting Started with SQL Server 2012 Cube Development teaches you through clear step-by-step exercises to create business intelligence solutions using Analysis Services. The knowledge gained through these practical examples can immediately be applied to your real-world problems. Getting Started with SQL Server 2012 Cube Development begins with an introduction to business intelligence and Analysis Services, the world's most-used cube engine. Guiding you through easy-to-understand examples to become a cube developer. Learn how to create a cube including all the advanced features such as KPIs, calculated measures, and time intelligence. Security and performance tuning will also be explored. You will learn how to perform and automate core tasks like deployment and processing. The main focus is on multidimensional cubes, but the creation of in-memory models will also be covered. You will learn everything you need to get started with cube development using SQL Server 2012.
Table of Contents (17 chapters)
Getting Started with SQL Server 2012 Cube Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Understanding the data source view


The data source view is a very important concept in Analysis Services. You can think of it as an abstraction layer between the relational database and the multidimensional cube. You have the ability to define objects that do not exist in the database. The data source view provides a logical view of the database, so to Analysis Services, the objects appear to exist in the database. This includes new tables, columns, and even referential integrity or relationships between objects.

Tip

In many cases you do not define referential integrity down in the database layer when you work with data warehouses. The reason for this is that loading of the data is much easier without them. If you have defined foreign keys and primary keys, you need to ensure that you always load your objects in the correct order.

If your data warehouse does not contain referential integrity, it has to be created in the data source view.

You can also add calculations to existing tables. They...