THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

SQLBI - Marco Russo

Please visit the same blog at - comments are now disabled here but you can comment on the new blog (all blog posts available here are available there, too).
You can follow me on Twitter: @marcorus

Microsoft updates its BI Roadmap - #ssas #bism #teched #powerpivot

During TechEd 2011, Microsoft announced an important update to its BI roadmap. The reason why this is important is related to the previous announcement, which I discussed in November 2010 by including links to several sources and comments. At PASS Summit 2010 the announcement regarding the next version of SQL Server, codenamed "Denali", caused a lot of discussions because it seemed that there would have been a "competitive" version of Analysis Services that would have been required existing projects made in UDM to be not upgradable to the "new model". And someone wondered if the lifecycle of UDM (Unified Dimensional Model, which is run by the MOLAP engine) started a descending curve.

In these months, I've been involved in many discussions with the development team with other partners, influencers and MVPs. What was a perception at that time was founded on some concrete facts: there was no plan about merging these technologies or providing any type of migration paths. Many worries about a possible end of UDM was not based on reality (the number of SSAS adopters is still growing every day) but the perception of a lack of commitment by Microsoft on UDM was the real issue. Many people asked for a change in this direction, looking for a converging path between these two technologies.

Based on my experience, I know that there are BI problems that need a multidimensional approach, but there are other problems that better feet with a more "traditional" relational approach. In the middle, a very large number of problems can be solved by both approaches at the same cost and with similar performances. These two worlds were separate: each one had its own tools, languages, data models and so on. And they would have been separated also in the future, based on the understanding everyone had with the previous roadmap.

Now, Microsoft is raising the bet on its Business Intelligence platform. These two worlds will grow together and we'll see a convergence towards a componentized approach where every technology for every layer of the solution will be able to interact with the other components. In other words, the same client tool will be able to query any model, regarding of the technology used to implement it (either relational or multidimensional). From the user perspective, this means that Excel will be able to query any relational or multidimensional model, and the same will be true for the new shining Crescent tool! From the architectural perspective, any existing investment on any technology will be preserved. For the large number of scenarios where either models can be used, you don't have to choose between a mature technology (UDM) that is not supported by modern tools (Crescent) and a new technology (Vertipaq) that misses some advanced feature (tool dimensions?) your user might expect in the solution because it was present in other solution he used in the past.

Thus, we'll have a single unified model, called BI Semantic Model (BISM). BISM will have two technologies to model data: the Multidimensional one (formerly known as UDM) and the Tabular one (that will be an enhancement of the current PowerPivot data model experience). You will have two languages, MDX and DAX, to define business logic and to query the model. And you will have two engines, MOLAP and Vertipaq (with their corresponding counterpart for accessing data in passthrough mode, ROLAP and Direct Query). The great and wonderful big news is that in BISM it will be possible to combine these components as you need: DAX query over a multidimensional model, MDX Script over a Tabular, and any client able to access to any model.

This is a great and ambitious vision. It might seem complex. But there is no silver bullet in this world, when you have to implement a real solution, you have to face different requirements and up to day nobody found a single technology that can be used for any needs. Implementing this vision in its completeness will require several years and its first release in Denali will not offer the full flexibility that has been promised. But the new commitment stated by Microsoft about this vision is what many partners were looking for. Their investments, and the investments made by their customer, will be preserved with this roadmap and any data model created in the past (and also today) will benefit in the future by the appearance of new tools and new products. Without requiring a complete rewrite of the solution and a complete retraining of their resources. In a competitive world and in a complex economy phase, this is definitely the most important message of this announcement.

As usual, we'll have to wait for the concrete bits of Denali and of the following releases to see if facts confirm the words. But I have many signs confirming that also the facts are really going in that direction. I will write more technical posts about the implication of this announcement in the future, especially after I'll be able to talk publicly about technical details that are now under NDA. In the meantime, you can also read this very interesting comment written by Chris Webb. And, of course, you can comment my post with sharing your perception - I'm interested in getting your feedback!

Published Wednesday, May 18, 2011 5:56 PM by Marco Russo (SQLBI)



Thiago Zavaschi said:

"and the same will be true for the new shining Crescent tool" and "The great and wonderful big news is that in BISM it will be possible to combine these components as you need: DAX query over a multidimensional model, MDX Script over a Tabular, and any client able to access to any model."

Wonderful! Great! :)

(sometimes is hard to be under NDA :-)

May 18, 2011 2:04 PM

Anthony Sammartino said:

Very good information Marco and thank you for sharing. I, like many others, rely on you, Vidas, Chris Webb and others for great information like this.  Its going to be very interesting on which model to use for clients as requirements for a project's first releases are usually not so complex, but that intensifies over time and wondering if you go down the tabular road will it become limiting and ultimately have to be switched to UDM (Complex Calculations Come to Mind).

Thanks again.

May 18, 2011 2:06 PM

Siddharth Mehta said:

Hi Marco,

You have mentioned " DAX query over a multidimensional model, MDX Script over a Tabular"

I feel it should be the other way round. DAX over tabular and MDX over Multi dimensional.


Siddharth Mehta

May 18, 2011 3:28 PM

Alan Whitehouse said:


I think the goal of Microsoft is to let you use DAX over a multidimensional model and MDX over a tabular model.  Basically the vision is to let you whatever "language" you know against whatever "model" you have.

It is an ambitious goal and I hope they can pull it off.

May 18, 2011 3:34 PM

Marco Russo (SQLBI) said:

Siddharth, I'm not wrong, Alan is right.

For this reason this is a big news.

However, don't expect all the combinations to be available in the Denali release.


May 18, 2011 6:04 PM

Siddharth Mehta said:

What can be in the future is just a speculation. MDX over a tabular model still seems possible due to Vertipaq, but using DAX over dimensional model is a real challenge in terms of roll out from MS and adoption by users.

Anyways, thanks for sharing your views.

May 19, 2011 11:29 AM

Marco Russo said:


this is not a speculation but a precise Microsoft statement.

Look at slide 11 of DBI206 presentation from T.K. Anand -

It is a dedicated slide just for this scenario. DAX query over a finance model running on MOLAP engine.


May 19, 2011 6:51 PM

SQLBI - Marco Russo said:

As Chris announced in his blog, some of the sessions from the SQLBits 8 in Brighton are already available

May 28, 2011 12:17 PM

SQLBI - Marco Russo said:

The Analysis Services team just posted a blog entry with a few useful links to jumpstart your experience

July 14, 2011 12:47 AM

Jörgen Hasselgren said:

This shift away from UDM will really rock my BI world. I'm still in shock :)

Have you heard of any tools for converting UDM to BISM?

October 12, 2011 2:43 PM

Marco Russo (SQLBI) said:

If you have a working model in UDM, keep in in UDM.


October 13, 2011 1:44 AM

John Thompson said:

I attended a Denali Community Info session the other day where the speaker asserted that Crescent tool will only work with the Tabular verison of BISM, initially at least, and that Multidimensional function is on the roadmap, but without a timetable - any word on this?

November 9, 2011 7:46 AM

Marco Russo (SQLBI) said:

Microsoft announced that BISM Multidimensional will support query made with DAX. This will enable Crescent (now called Power View) to query existing multidimensional models.

They said that this support will be enabled after RTM but before next SQL Server release (usually 18 months). But I hope it will happen very soon after RTM!

November 9, 2011 5:24 PM
New Comments to this post are disabled

About Marco Russo (SQLBI)

Marco Russo is a consultant, writer and trainer specialized in Business Intelligence with Microsoft technologies. He runs the SQLBI.COM website, which is dedicated to distribute resources useful for BI developers, like Integration Services components, Analysis Services models, tools, technical information and so on. Marco is certified as MCT, MCDBA, MCSD.NET, MCSA, MCSE+I.

This Blog



Privacy Statement