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

Getting user value through self-service reporting


SQL Server Analysis Services is an application that allows you to create a semantic model that can be used to analyze very large amounts of data with great speed. The models can either be user created, or created and maintained by IT.

If the user wants to create it, they can do so, by using a component in Microsoft Excel 2010 and upwards called PowerPivot. If you run Microsoft Excel 2013, it is included in the installed product, and you just need to enable it. In Microsoft Excel 2010, you have to download it as a separate add-in that you either can find on the Microsoft homepage or on the site called http://www.powerpivot.com. PowerPivot creates and uses a client-side semantic model that runs in the context of the Microsoft Excel process; you can only use Microsoft Excel as a way of analyzing the data. If you just would like to run a user created model, you do not need SQL Server at all, you just need Microsoft Excel. On the other hand, if you would like to maintain user created models centrally then you need, both SQL Server 2012 and SharePoint.

Instead, if you would like IT to create and maintain a central semantic model, then IT need to install SQL Server Analysis Services. IT will, in most cases, not use Microsoft Excel to create the semantic models. Instead, IT will use Visual Studio as their tool. Visual Studio is much more suitable for IT compared to Microsoft Excel. Not only will they use it to create and maintain SQL Server Analysis Services semantic models, they will also use it for other database related tasks. It is a tool that can be connected to a source control system allowing several developers to work on the same project.

The semantic models that they create from Visual Studio will run on a server that several clients can connect to simultaneously. The benefit of running a server-side model is that they can use the computational power of the server, this means that you can access more data. It also means that you can use a variety of tools to display the information.

This book will focus on IT created models, but the information described in Chapter 9, In-memory, the Future, can be used to learn how to create models in PowerPivot. Both approaches enable users to do their own self-service reporting. In the case where PowerPivot is used they have complete freedom; but they also need the necessary knowledge to extract the data from the source systems and build the model themselves.

In the case where IT maintains the semantic model, the users only need the knowledge to connect an end user tool such as Microsoft Excel to query the model.

The users are, in this case, limited to the data that is available in the predefined model, but on the other hand, it is much simpler to do their own reporting. This is something that can be seen in the preceding figure that shows Microsoft Excel 2013 connected to a semantic model.

SQL Server Analysis Services is available in the Standard edition with limited functionality, and in the BI and Enterprise edition with full functionality. For smaller departmental solutions the Standard edition can be used, but in many cases you will find that you need either the BI or the Enterprise edition of SQL Server. If you would like to create in-memory models as described in Chapter 9, In-memory, the Future, then you definitely cannot run the Standard edition of the software since this functionality is not available in the Standard edition of SQL Server.