![]() ![]() This version contained better support for business dimensions, but was definitely limited by today's standards. In 2000, Microsoft released Analysis Services with SQL Server 2000.In 1998, Microsoft released OLAP Services with SQL Server 7, and along with that, released the first MDX programming language specification.Let's take a step back and look at the history of SSAS and OLAP. Item #1: Some History of the SSAS OLAP and Tabular Methodologies Virtual analytic database projects that query back to the source (ROLAP for SSAS OLAP and DirectQuery for Tabular).Using the programming languages (MDX for SSAS OLAP and DAX for SSAS Tabular).Baker's Dozen Spotlight: handling more advanced relationships (such as role-playing relationships and many-to-many relationships).Creating starter projects using SQL Server Data Tools.A brief history of the two methodologies.Here are the 13 areas that I'll compare SSAS OLAP to SSAS Tabular: Although some corporate BI databases can use the Tabular model, the larger installations will need to use the more scalable SSAS OLAP model.Īlthough some corporate BI databases can use the Tabular model, the larger installations will need to use the more scalable SSAS OLAP model. By contrast, SSAS Tabular is an in-memory solution that compresses the data but cannot exceed server memory. Remember that SSAS OLAP (also known as multidimensional OLAP) can handle extremely large datasets that exceed server memory. ( )Įven before I dive into any detail comparisons, there is one topic that must always be mentioned. Note that this article doesn't have any images, and only a few code snippets you can find the details for SSAS OLAP and SSAS Tabular in the two prior articles.Īdditionally, as experts generally recommend shaping the source of analytic databases in star-schema fact/dimension models, I wrote about Dimension Modeling tips in the March/April 2013 issue. Throughout this article, I'll reference specific sections from both articles. ![]() I also wrote about creating SSAS Tabular Databases in the January/February 2013 issue. If you want a refresher on the basic steps of either SSAS OLAP or SSAS Tabular, I wrote about creating SSAS OLAP cubes in the March/April 2011 issue of this magazine. A Refresher on SSAS OLAP and SSAS Tabularįirst, I'm assuming that you have at least basic knowledge of either methodology. If you are planning to use the Tabular model for a project, hopefully some of the items in this article will save you some research and time. This article covers these tasks and where I think one approach comes out on top. Like most developers, I view available functionality as a key context in product comparisons. To put the Tabular model to the test, I went through some of the common patterns and development tasks that many developers go through when creating SSAS OLAP databases. Sometimes a consensus can surface right away, and the initial consensus was that Tabular could produce the same or similar results with less effort?without the developer needing to get down to the “bare metal” that characterizes many SSAS development activities. When I started working with the new Tabular model in SSAS 2012, I was keenly interested in whether certain tasks in the Tabular model would be more powerful (or less powerful) and easier (or more difficult) than traditional SSAS OLAP. Yes, they take time to learn, but can produce excellent results. ![]() And I'll freely admit to being partial to SSAS OLAP and MDX. I've seen it grow into a mature, full-blown solution for creating analytic databases. I've been using SSAS for many years now to create OLAP databases for clients. Depending on how much (or how little) you've used either approach, the results might surprise you. In this article, I'll take several tasks and functionality that database developers often need to implement, and I'll compare the approaches using SSAS OLAP and SSAS Tabular. Some believe that the new Tabular model is easier to use than SSAS OLAP. The latter contains a somewhat different set of tools than SSAS OLAP and a new supporting language (DAX). SQL Server 2012 contains a new BI semantic model that allows developers to create analytic databases either by using OLAP or by using a new Tabular model. SSAS OLAP offers many powerful features, although some developers view the learning curve of OLAP (and its supporting language, MDX) as very steep. For over a decade, many Microsoft database developers have used SQL Server Analysis Services (SSAS) OLAP to create database cubes for advanced business analytics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |