# Dynamic ABC Analysis in Power Pivot using DAX – Part 2

Almost two years ago I published the first version of an Dynamic ABC Analysis in Power Pivot and by now it is the post with the most comments among all my blog posts. This has two reason:
1) the formula was quite complex and not easy to understand or implement
2) the performance was not really great with bigger datasets

When the first of those comments flew in, I started investigating into a new, advanced formula. At about the same time Marco Russo and Alberto Ferrari published their ABC Classification pattern – a static version using calculated columns – at www.daxpatterns.com. When I had my first dynamic version ready I sent it to Marco and Alberto and asked if they are interested in the pattern and if I can publish it on their website. Long story short – this week the new pattern was released and can now be found here:

ABC Classification – Dynamic

It got some major performance improvements and was also designed towards reusability with other models. The article also contains some detailed explanations how the formula actually works but its still very hard DAX which will take some time to be fully understood. The pattern also features some extended versions to address more specific requirements but I think its best to just read the article on your own.

Hope you enjoy it!

# Happy New Year! – How about some Conferences?

2015 just started – and it is a quickstart in terms of SQL Server conferences! There is quite a lot of upcoming conferences and I am happy that most of them are in Europe.

Below you can find a short overview followed by some more details:

 What? When? Where? Am I there? German SQL Server Conference February 3-5th Darmstadt, Germany Yes, I am speaking! SQL Saturday Vienna February 27-28th Vienna, Austria Maybe, but not speaking SQLRally Nordic Copenhagen March 2-4th Copenhagen, Denmark Yes, I am speaking! SQLBits XIV Superheroes March 4-7th London, UK Yes, I am speaking!

UPDATE 2014-01-13:
I just received a confirmation that my session “Power BI on SAP HANA” was accepted for SQL Bits XIV!
It’s also the first time that I will do a session together with a Co-Speaker, my colleague Markus Begerow (b)

It starts with the German SQL Server Conference 2015 on February 3-5th

I am also very happy that my session “Load testing Analysis Services” was selected and I will be speaking the second time in a row at this awesome conference which is also the biggest German SQL Server Conference out there. And now worries, there are also a lot of English session in case you do not speak German

Up next is a true marathon of conferences starting with the SQL Saturday #374 in Vienna on 28th of February.

This year also featuring Pre-Cons on 27th of February!
Reza Rad (t, b) and Leila Etaati (t, b) will be speaking on “Power BI from Rookie to Rockstar” and Dejan Sarka (t, b) on “Advanced Data Modeling
Last year it was fully booked pretty soon and we had a long waiting list so better do your reservation now!
The schedule can be found here and features 20 sessions of well-know SQL Server professionals.

Directly after the SQL Saturday in Vienna the PASS SQLRally Nordic opens its doors in Copenhagen again on March 2-4.

The official schedule was just released today and can be found here (full PDF)!
I will deliver my session “Deep-Dive to Analysis Services Security” on Wednesday 4th.

Last but definitely not least is SQLBits Conferences, Europe’s biggest SQL Server conference, which is taking place the 13st time now on March 4-7 in London. (don’t get confused just because its SQL Bits XIV, Microsoft also skipped Windows 9 ). This year its all about Superheroes and a lot of SQL Server Superheroes will be there!

A schedule is not available yet but will be made public within the next days I guess so stay tuned!

UPDATE 2014-01-13:
The official schedule will soon be available here. Our Session is very likely to be on Friday.

Hope to see you there!

# Events-In-Progress for Time Periods in DAX

Calculating the Events-In-Progress is a very common requirement and many of my fellow bloggers like Chris Webb, Alberto Ferrari and Jason Thomas already blogged about it and came up with some really nice solutions. Alberto also wrote a white-paper summing up all their findings which is a must-read for every DAX and Tabular/PowerPivot developer.
However, I recently had a slightly different requirement where I needed to calculate the Events-In-Progress for Time Periods – e.g. the Open Orders in a given month – and not only for a single day. The calculations shown in the white-paper only work for a single day so I had to come up with my own calculation to deal with this particular problem.

Before we can start we need to identify which orders we actually want to count if a Time Period is selected. Basically we have to differentiate between 6 types of Orders for our calculation and which of them we want to filter or not:

 Order Definition Order1 (O1) Starts before the Time Period and ends after it Order2 (O2) Starts before the Time Period and ends in it Order3 (O3) Starts in the Time Period and ends after it Order4 (O4) Starts and ends in the Time Period Order5 (O5) Starts and ends after the Time Period Order6 (O6) Starts and ends before the Time Period

For my customer an order was considered as “open” if it was open within the selected Time Period, so in our case we need to count only Orders O1, O2, O3 and O4. The first calculation you would usually come up with may look like this:

1. [MyOpenOrders_FILTER] :=
2. CALCULATE (
3.     DISTINCTCOUNT ( 'Internet Sales'[Sales Order Number] ),
4.     FILTER (
5.         'Internet Sales',
6.         'Internet Sales'[Order Date]
7.             <= CALCULATE ( MAX ( 'Date'[Date] ) )
8.     ),
9.     FILTER (
10.         'Internet Sales',
11.         'Internet Sales'[Ship Date]
12.             >= CALCULATE ( MIN ( 'Date'[Date] ) )
13.     )
14. )

We apply custom filters here to get all orders that were ordered on or before the last day and were also shipped on or after the first day of the selected Time Period. This is pretty straight forward and works just fine from a business point of view. However, performance could be much better as you probably already guessed if you read Alberto’s white-paper.

So I integrate his logic into my calculation and came up with this formula (Note that I could not use the final Yoda-Solution as I am using a DISTINCTCOUNT here):

1. [MyOpenOrders_TimePeriod] :=
2. CALCULATE (
3.     DISTINCTCOUNT ( 'Internet Sales'[Sales Order Number] ),
4.     GENERATE (
5.         VALUES ( 'Date'[Date] ),
6.         FILTER (
7.             'Internet Sales',
8.             CONTAINS (
9.                 DATESBETWEEN (
10.                     'Date'[Date],
11.                     'Internet Sales'[Order Date],
12.                     'Internet Sales'[Ship Date]
13.                 ),
14.                 [Date], 'Date'[Date]
15.             )
16.         )
17.     )
18. )

To better understand the calculation you may want to rephrase the original requirement to this: “An open order is an order that was open on at least one day in the selected Time Period”.

I am not going to explain the calculations in detail again as the approach was already very well explained by Alberto and the concepts are the very same.

An alternative calculation would also be this one which of course produces the same results but performs “different”:

1. [MyOpenOrders_TimePeriod2] :=
2. CALCULATE (
3.     DISTINCTCOUNT ( 'Internet Sales'[Sales Order Number] ),
4.     FILTER (
5.         GENERATE (
6.             SUMMARIZE (
7.                 'Internet Sales',
8.                 'Internet Sales'[Order Date],
9.                 'Internet Sales'[Ship Date]
10.             ),
11.             DATESBETWEEN (
12.                 'Date'[Date],
13.                 'Internet Sales'[Order Date],
14.                 'Internet Sales'[Ship Date]
15.             )
16.         ),
17.         CONTAINS ( VALUES ( 'Date'[Date] ), [Date], 'Date'[Date] )
18.     )
19. )

I said it performs “different” as for all DAX calculations, performance also depends on your model, the data and the distribution and granularity of the data. So you should test which calculation performs best in your scenario. I did a simple comparison in terms of query performance for AdventureWorks and also my customer’s model and results are slightly different:

 Calculation (Results in ms) AdventureWorks Customer’s Model [MyOpenOrders_FILTER] 58.0 1,094.0 [MyOpenOrders_TimePeriod] 40.0 390.8 [MyOpenOrders_TimePeriod2] 35.5 448.3

As you can see, the original FILTER-calculation performs worst on both models. The last calculation performs better on the small AdventureWorks-Model whereas on my customer’s model (16 Mio rows) the calculation in the middle performs best. So it’s up to you (and your model) which calculation you should prefer.

The neat thing is that all three calculations can be used with any existing hierarchy or column in your Date-table and of course also on the Date-Level as the original calculation.

# SSAS Dynamic Named Sets in Calculated Members

Recently at one of my customers we were doing some performance tuning on a SSAS Multidimensional cube and I came across something I have not seen before yet in my lifetime as a SSAS developer. Even the simplest select queries where running for several seconds, even if executed on warm cache! So first I thought this may be related to some SCOPE assignments overwriting values etc. Using my MdxScriptDebugger I could easily identify that none of the SCOPE assignments had any impact on the actual result of the query. However, what the result of the MdxScriptDebugger trace also revealed was that the query-time increased after a calculated member was created. Important to note here is that this specific member was NOT used in the test-query at all! Investigating into the calculated member turned out that it was using a Dynamic Named Set.

Dynamic Named Sets are usually used if you want a set to be re-evaluated in the current context opposed to Static Named Sets which are only evaluated once during creation. For example you can create a Dynamic Named Set for your Top 10 customers. Changing the Year or Country would cause a re-evaluation of the set and different customers are returned for your filter selections. These type of calculated sets is usually not a problem.

Another reason to used Dynamic Named Sets is to deal with Sub-Selects. Some client tools, foremost Microsoft Excel Pivot Tables, use Sub-Selects to deal with multiple selections on the same attribute. Lets do a little example on how to use Dynamic Named Sets here. Assume you need to calculate the average yearly sales for the selected years. This may sound very trivial at first sight but can be very tricky. In order to calculated the yearly average we first need to calculated how many years are in the currently selected:

1. CREATE MEMBER CURRENTCUBE.[Measures].[CountYears_EXISTING] AS (
2. COUNT(EXISTING [Date].[Calendar Year].[Calendar Year].members)
3. );

However, this does not work if Sub-Selects are used in the query:

The calculated member returns “6” (the overall number of years) instead of “2” (the actually selected number of years). The issue here is that the calculation is not aware of any Sub-Select or filters within the Sub-Select as it is executed only outside of the Sub-Select.

To work around this issue you can create a Dynamic Name Set and refer to it in your calculated member:

1. CREATE DYNAMIC SET [ExistingYears] AS {
2. EXISTING [Date].[Calendar Year].[Calendar Year].members
3. };
4.
5. CREATE MEMBER CURRENTCUBE.[Measures].[CountYears_DynamicSet] AS (
6. COUNT([ExistingYears])
7. );

Now we get the correct results for our Count of Years calculation and could simply divide our Sales Amount by this value to get average yearly sales. The reason for this is that Dynamic Named Sets are also evaluated within the Sub-Select and therefore a COUNT() on it returns the correct results here.

So this technique is quite powerful and is also the only feasible workaround to deal with this kind of problem. But as I initially said, this can also cause some performance issues!

1. CREATE DYNAMIC SET [ExpensiveSet] AS {
2. Exists(
3.     [Product].[Category].[Category].members,
4.     Filter(
5.         Generate(
7.             CrossJoin(
8.                 {[Date].[Calendar].CURRENTMEMBER},
10.                     Order(
11.                         [Customer].[Customer].[Customer].MEMBERS,
12.                         [Measures].[Internet Sales Amount],
13.                         BDESC),
14.                     10000))),
15.         [Measures].[Internet Order Quantity] > -1
16.     ),
17.     'Internet Sales'
18. )
19. };
20.
21. CREATE MEMBER CURRENTCUBE.[Measures].[UnusedCalc] AS (
22. COUNT([ExpensiveSet])
23. );

The [ExpensiveSet] is just a Dynamic Named Set which needs some time to be evaluated and the [UnusedCalc] measure does a simple count over the [ExpensiveSet]. Having these calculations in place you can now run any query against your cube and will notice that even the simplest query now takes some seconds to execute even if the new calculated member is not used:

1. SELECT
2. [Measures].[Internet Sales Amount] ON 0

I am quite sure that this behavior is related to how Dynamic Named Sets are evaluated and why they also work for Sub-Selects. However, I also think that calculations that are not used in a query should not impact the results and/or performance of other queries!

I just created a bug on Connect in case you want to vote it:
https://connect.microsoft.com/SQLServer/feedback/details/1049569

I know that Dynamic Named Sets in combination with calculated members is a not a widely used technique as I guess most developers are not even aware of its power. For those who are, please keep in mind that these kind of calculations get evaluated for every query which can be crucial if your Dynamic Named Set is expensive to calculate! This has also impact on meta-data queries!

# MDX Script Debugger – Beta-Release

I recently built a tool which should help to debug the MDX scripts of an Analysis Services cube in order to track down formula engine related performance issues of a cube. As you probably know most of the performance issues out there are usually caused by poorly or wrong written MDX scripts. This tool allows you to execute a reference query and highlights the MDX script commands that are effectively used when the query is run. It provides the overall timings and how long each additional MDX script command extended the execution time of the reference query. The results can then either be exported to XML for further analysis in e.g. Power BI or a customized version of the MDX script can be created and used to run another set of tests.

The tool is currently in a beta state and this is the first official release – and also my first written tool that I share publicly so please don’t be too severe with your feedback   – just joking every feedback is good feedback!

Below is a little screenshot which shows the results after  the reference query is executed. The green lines are effectively used by the query whereas the others do not have any impact on the values returned by the query.

A list of all features, further information and also the source code can be found at the project page on codeplex:
https://mdxscriptdebugger.codeplex.com/
https://mdxscriptdebugger.codeplex.com/releases

Looking forward to your feedback and hope it helps you to track down performance issues of your MDX Scripts!

Recently I had to setup an Analysis Services cube and expose it to external users. This is usually done by using Internet Information Server (IIS) and creating a new WebSite which hosts msmdpump.dll. This DLL more or less wraps XMLA commands inside HTTP thus allowing external users to access the cube via HTTP. Besides Windows Authentication this setup also allows Basic Authentication and so external users can simply connect by specifying Username and Password in e.g. Excel when connecting to the cube:

There are already a lot of whitepapers out there which describe how to set things up correctly. Here are just some examples:
- MSDN: http://msdn.microsoft.com/en-us/library/gg492140.aspx

They provide very useful information and you should be familiar with the general setup before proceeding here or using the final PowerShell script.

The PowerShell script basically performs the following steps:

1. Create a local folder as base for your WebSite in IIS
2. Copy SSAS ISAPI files (incl. msmdpump.dll) to the folder
3. Create and Configure an IIS AppPool
4. Create and Configure a IIS WebSite
5. Add and enable an ISAPI entry for msmdpump.dll
6. Configure Authentication
7. Configure Default Document
8. Update connection information to SSAS server

I tested it successfully with a clean installation of IIS 8.0 (using applicationhost.config.clean.install). In case you already have other WebSites running you may still consider doing the steps manually or adopting the script if necessary. The script is written not to overwrite any existing Folders, WebSites, etc. but you never know.

So here is my final script:

1. #Import Modules
3.
4. # change these settings
5. $iisSiteName = "OLAP" 6.$iisPort = "8000"
7. $olapServerName = "server\instance" 8. 9. # optionally also change these settings 10.$isapiFiles = "c:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\bin\isapi\*"
11. $iisAbsolutePath = "C:\inetpub\wwwroot\" +$iisSiteName
12. $iisAppPoolName =$iisSiteName + "_AppPool"
13. $iisAppPoolUser = "" #default is ApplicationPoolIdentity 14.$iisAppPoolPassword = ""
15. $iisAuthAnonymousEnabled =$false
16. $iisAuthWindowsEnabled =$true
17. $iisAuthBasicEnabled =$true
18. $olapSessionTimeout = "3600" #default 19.$olapConnectionPoolSize = "100" #default
20.
21. if(!(Test-Path $iisAbsolutePath -pathType container)) 22. { 23. #Creating Directory 24. mkdir$iisAbsolutePath  | Out-Null
25.
26.     #Copying Files
27.     Write-Host -NoNewline "Copying ISAPI files to IIS Folder … "
28.     Copy -Path $isapiFiles -Destination$iisAbsolutePath -Recurse
29.     Write-Host " Done!" -ForegroundColor Green
30. }
31. else
32. {
33.     Write-Host "Path $iisAbsolutePath already exists! Please delete manually if you want to proceed!" -ForegroundColor Red 34. Exit 35. } 36. 37. #Check if AppPool already exists 38. if(!(Test-Path$("IIS:\\AppPools\" + $iisAppPoolName) -pathType container)) 39. { 40. #Creating AppPool 41. Write-Host -NoNewline "Creating ApplicationPool$iisAppPoolName if it does not exist yet … "
42.     $appPool = New-WebAppPool -Name$iisAppPoolName
43.     $appPool.managedRuntimeVersion = "v2.0" 44.$appPool.managedPipelineMode = "Classic"
45.
46.     $appPool.processModel.identityType = 4 #0=LocalSystem, 1=LocalService, 2=NetworkService, 3=SpecificUser, 4=ApplicationPoolIdentity 47. #For details see http://www.iis.net/configreference/system.applicationhost/applicationpools/add/processmodel 48. 49. if ($iisAppPoolUser -ne "" -AND $iisAppPoolPassword -ne "") { 50. Write-Host 51. Write-Host "Setting AppPool Identity to$iisAppPoolUser"
52.         $appPool.processmodel.identityType = 3 53.$appPool.processmodel.username = $iisAppPoolUser 54.$appPool.processmodel.password = $iisAppPoolPassword 55. } 56.$appPool | Set-Item
57.     Write-Host " Done!" -ForegroundColor Green
58. }
59. else
60. {
61.     Write-Host "AppPool $iisAppPoolName already exists! Please delete manually if you want to proceed!" -ForegroundColor Red 62. Exit 63. } 64. 65. #Check if WebSite already exists 66.$iisSite = Get-Website $iisSiteName 67. if ($iisSite -eq $null) 68. { 69. #Creating WebSite 70. Write-Host -NoNewline "Creating WebSite$iisSiteName if it does not exist yet … "
71.     $iisSite = New-WebSite -Name$iisSiteName -PhysicalPath $iisAbsolutePath -ApplicationPool$iisAppPoolName -Port $iisPort 72. Write-Host " Done!" -ForegroundColor Green 73. } 74. else 75. { 76. Write-Host "WebSite$iisSiteName already exists! Please delete manually if you want to proceed!" -ForegroundColor Red
77.     Exit
78. }
79.
80. #Ensuring ISAPI CGI Restriction entry exists for msmdpump.dll
81. if ((Get-WebConfiguration "/system.webServer/security/isapiCgiRestriction/add[@path='$iisAbsolutePath\msmdpump.dll']") -eq$null)
82. {
83.     Write-Host -NoNewline "Adding ISAPI CGI Restriction for $iisAbsolutePath\msmdpump.dll … " 84. Add-WebConfiguration "/system.webServer/security/isapiCgiRestriction" -PSPath:IIS:\\ -Value @{path="$iisAbsolutePath\msmdpump.dll"}
85.     Write-Host " Done!" -ForegroundColor Green
86. }
87. #Enabling ISAPI CGI Restriction for msmdpump.dll
88. Write-Host -NoNewline "Updating existing ISAPI CGI Restriction … "
89. Set-WebConfiguration "/system.webServer/security/isapiCgiRestriction/add[@path='$iisAbsolutePath\msmdpump.dll']/@allowed" -PSPath:IIS:\\ -Value "True" 90. Set-WebConfiguration "/system.webServer/security/isapiCgiRestriction/add[@path='$iisAbsolutePath\msmdpump.dll']/@description" -PSPath:IIS:\\ -Value "msmdpump.dll for SSAS"
91. Write-Host " Done!" -ForegroundColor Green
92.
93.
94. #Adding ISAPI Handler to WebSite
95. Write-Host -NoNewline "Adding ISAPI Handler … "
96. Add-WebConfiguration /system.webServer/handlers -PSPath $iisSite.PSPath -Value @{name="msmdpump"; path="*.dll"; verb="*"; modules="IsapiModule"; scriptProcessor="$iisAbsolutePath\msmdpump.dll"; resourceType="File"; preCondition="bitness64"}
97. Write-Host " Done!" -ForegroundColor Green
98.
99. #enable Windows and Basic Authentication
100. Write-Host -NoNewline "Setting Authentication Providers … "
101. #need to Unlock sections first
102. Set-WebConfiguration /system.webServer/security/authentication/anonymousAuthentication  MACHINE/WEBROOT/APPHOST -Metadata overrideMode -Value Allow
103. Set-WebConfiguration /system.webServer/security/authentication/windowsAuthentication  MACHINE/WEBROOT/APPHOST -Metadata overrideMode -Value Allow
104. Set-WebConfiguration /system.webServer/security/authentication/basicAuthentication  MACHINE/WEBROOT/APPHOST -Metadata overrideMode -Value Allow
105.
106. Set-WebConfiguration /system.webServer/security/authentication/anonymousAuthentication -PSPath $iisSite.PSPath -Value @{enabled=$iisAuthAnonymousEnabled}
107. Set-WebConfiguration /system.webServer/security/authentication/windowsAuthentication -PSPath $iisSite.PSPath -Value @{enabled=$iisAuthWindowsEnabled}
108. Set-WebConfiguration /system.webServer/security/authentication/basicAuthentication -PSPath $iisSite.PSPath -Value @{enabled=$iisAuthBasicEnabled}
109. Write-Host " Done!" -ForegroundColor Green
110.
112. Write-Host -NoNewline "Adding Default Document msmdpump.dll … "
113. Add-WebConfiguration /system.webServer/defaultDocument/files -PSPath $iisSite.PSPath -atIndex 0 -Value @{value="msmdpump.dll"} 114. Write-Host " Done!" -ForegroundColor Green 115. 116. #Updating OLAP Server Settings 117. Write-Host -NoNewline "Updating OLAP Server Settings … " 118. [xml]$msmdpump = Get-Content "$iisAbsolutePath\msmdpump.ini" 119.$msmdpump.ConfigurationSettings.ServerName = $olapServerName 120.$msmdpump.ConfigurationSettings.SessionTimeout = $olapSessionTimeout 121.$msmdpump.ConfigurationSettings.ConnectionPoolSize = $olapConnectionPoolSize 122.$msmdpump.Save("$iisAbsolutePath\msmdpump.ini") 123. Write-Host " Done!" -ForegroundColor Green 124. 125. Write-Host "Everything done! " 126. Write-Host "The SSAS server can now be accessed via http://$env:computername`:$iisPort" The script can also be downloaded here. The process of setting up HTTP connectivity is the same for Analysis Services Multidimensional and Tabular so the script works for both scenarios, just change the server name accordingly. # Using Self-Signed Certificates for your Power BI DMG In my previous post I showed how to setup a Power BI Data Management Gateway on a non-domain Azure VM. The final setup is also the starting-point for this post where we will use self-signed certificates to use HTTPS/SSL connectivity to our DMG. So make sure that you have all prerequisites up and running before you continue reading. Basically, the process to switch to HTTPS is pretty straight forward. Simply open your DMG, go to Settings and change from HTTP to HTTPS. Finally select your certificate and you are ready to go! This may work in a corporate hybrid environment where everything is set up correctly but for a non-Azure VM this is a bit more complicated and this is what this post is about. Besides the initial setup from my previous post there are some steps you need to do in advance in order for HTTPS connectivity to work: 1) Open the port that the DMG HTTPS connection uses in your Windows Firewall (default is port 8050) 2) Create an Endpoint for your Azure VM for the very same port 3) Create a self-signed certificate to be used to establish a secure connection You should already be familiar with 1) and 2) as you needed to do the same steps also for your HTTP port of your DMG (default is port 8051 here). To create a self-signed certificate you can simply follow the steps as described here. The important thing here is to use the full qualified server name: CN=myserver.cloudapp.net This is very import, otherwise the final connection will not work! Your MakeCert-command should look similar to this: makecert -r -pe -n “CN=myserver.cloudapp.net” -b 01/01/2000 -e 01/01/2050 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp “Microsoft RSA SChannel Cryptographic Provider” -sy 12 After you run the command the new certificate is automatically added to your users personal certificates and can be used when setting up HTTPS connectivity for your DMG: Once you click [OK] it takes some time (~1 Minute) until everything is updated and HTTPS connectivity can be used. Now you can use Excel and Power Query to search for your data sources that are published via OData. You will find all of them but as soon as you try to load the data you will receive the following error: That’s a bit surprising as the DMG is configured correctly using HTTPS and the very same OData feed worked just fine with HTTP. But here comes the error in my thinking that I was not aware of before talking to Benjamin Tang and Samuel Zhang from the product team. Until that point I always thought that the data is load through the cloud and there is no direct connection from my client to the server: But this is not how it works! What actually happens in the background is that the request to the Power BI OData service gets redirected to the server and the client connects directly to the server: And this is also where our PQ error originates as the certificate used is not a trusted certificate on the client. In order to make it a trusted certificate you need to install it on the client. This can be done by following these steps: 1) Launch Internet Explorer using “Run as Administrator” (I’m serious here, this only works with IE but not with e.g. Chrome!) 2) navigate to https://myserver.cloudapp.net:8050 (or whatever servername/port you used) 3) continue to the website and ignore the certificate error 4) press [Cancel] at the popup the asks for credentials 5) now click on the “Certificate error” in the menu bar and press “View certificates” 6) Now install the certificate: (Please note that this option is only available if you are using Internet Explorer launched as Administrator!!!) 7) select the location where you want to store the certificate (Current User or Local Machine depending whether it should be installed for you only or for all users) 8) whichever storage location you used, just make sure that you place the certificate in the “Trusted Root Certification Authorities” on the next page: Once you have installed the certificate to your Trusted Root Certificate Authorities store the Power Query connections works again but now it is using HTTPS! Of course this solution is only for demo and testing purposes, in a real world scenario you would already have your certificates in place and everything should indeed work out-of-the-box. # Using Power BI DMG on Non-Domain Azure VMs – August 2014 Update In one of my recent posts I explained how to use the Power BI Data Management Gateway to access data hosted in a SQL Server running on an Azure VM. At the time of writing that post the steps to establish connectivity were not quite intuitive. With the latest Update of the Data Management Gateway (Version 1.2.5303.1 and later) things got a bit easier. However, there is still a little thing that you have to configure to make everything work smoothly. First of all, I highly recommend you to read my first post on this topic to fully understand the actual issue and why it does not work out-of-the-box. When creating a new Data Source the DMG has to be reachable from the machine on which the Data Source Manager (the Click-Once application where you enter your SQL credentials) is executed. The hostname is derived from the DMG and for Azure VMs this does by default not reflect the hostname under which the VM is reachable from public. The hostname would be “MyServer” whereas the public DNS name is “MyServer.cloudapp.net”. To check what hostname the DMG is using you can execute the following Power Shell command: 1. [System.Net.Dns]::GetHostEntry("localhost") In order to change this hostname you can either join the VM to a domain (which is not what we want to do here) or use the following approach: Open the System settings of your server: You will notice that both, “Computer name” and “Full computer name” show the same name, and both without the suffix “.cloudapp.net”. In order to change this we need to click the “Change settings” button right next to the names to open the System Properties: Again, click [Change …] to open the computers domain settings: As you can see, the “Full computer name” does not show our required suffix “.cloudapp.net” yet. We can change this in the dialog available via the [More …] Button: Here we can set our “Primary DNS suffix” – we set it to “cloudapp.net” (without leading dot) to reflect our public DNS name. By clicking [OK] on all open windows you will see the new full name “MyServer.cloudapp.net” now being used as “Full computer name” everywhere. Also our Power Shell command from above now shows the correct hostname. Note that this change also requires a reboot of the VM. Once the machine is rebooted and DMG is running again you can now use any client machine to create your Data Source which was previously only possible from the server directly and required a RDP connection. Also HTTPS connectivity with self-signed certificates works with this approach which I will show in one of my next posts – so stay tuned! # Hiding Dimension Details in Analysis Services An Analysis Services cube is usually accessed by a wide variety of people all of them having different roles in the business. For example Product Managers, Sales Representatives, Key Account Managers and so on. Sometimes it is necessary to hide detailed information of a given dimension or attribute from a certain user or role. In this post I will show you how this can be accomplished. Lets take a simple example and assume we have the role “ProductManager” which must not be allowed to see any specific details of a single customer but must be able to see aggregation levels above the customer like Gender, Education, etc. This can be accomplished quite easily by changing the security settings of our Product Manager role. We navigate to “Dimension Data” > Dimension “Customer” > Attribute “Customer”. Next go to the “Advanced” tab and manually specify your Allowed Set as: {[Customer].[Customer].[All Customers]} One important thing here is to uncheck “Enable Visual Totals” as shown above, otherwise you will not see any data at all! An end-user which owns the role ProductManager would see the following result in Excel: He sees aggregated values on Education and Gender Level but can not see details of any single customer. A scenario that’s a bit more complex to achieve is to hide not only one attribute but all attributes of a given dimension. Of course, we could use the approach as described above and do it for each and every attribute in the dimension. This would technically work, but its timely to implement and also hard to maintain (e.g. if new attributes are added). Ideally we only want to define it once in a single place and it should work for all attributes, existing and also new ones. We can make use auf Auto-Exists within our security role here. Auto-Exists basically reflect the security defined on one attribute to all other attributes in the same dimension. So if you are restricted to [Country]=”Austria” you can only see Cities in Austria and for Continents you would only see Europe but not America. Having this in mind we could create a dummy-customer (which has no associated facts) on which we put our security. Instead of creating a dummy-customer manually in our relational DB we can also make use of the special UnknownMember which can be activated for any dimension. Doing this SSAS automatically creates a dummy-member for us which can be used for our security purposes: Note that we have set the UnkownMemberName to “No Details Available” to inform the user that there are no details available for him/her. The role itself would then specify the UnknownMember in the Allowed Set as: {[Customer].[Customer].UNKNOWNMEMBER} Again, make sure that “Enable Visual Totals” is unchecked! Now our Excel looks as follows: (Note: “Show items with no data on rows” was enabled in PivotTable options here) Using any attribute or hierarchy of our secured dimension in a filter would show this result: One last option you may consider is to set the Visibility of the UnknownMember to “Hidden” thus also hiding the UnknownMember and only revealing the All-members which was our initial requirement. However, I think using the UnknownMember’s name to provide some further information for the end-user makes quite sense e.g. naming it “No Details Available due to Security Restrictions” or “Restricted by Security”. This is of course not possible if you create your dummy-customer manually that’s why I prefer using the UnkownMember. Note1: During my tests I came across a bug which when you change the Visibility of the UnkownMember after you have already defined security makes you end up seeing all details. Even a redeploy or ProcessFull do not solve the problem. What you need to do is to explicitly change the definition of the role (e.g. by adding a blank to the Allowed Set) and redeploy the role afterwards. Note2: None of the above works for SSAS tabular as it does not have the concept of (disabled) VisualTotals which is essential for this solution to work! # Restoring a SSAS Tabular Model to Power Pivot It is a very common scenario to create a SSAS Tabular Model out of an Power Pivot Model contained in an Excel workbook. Microsoft even created an wizard (or actually a separate Visual Studio project) that supports you doing this. Even further, this process is also a major part of Microsoft’s strategy to cover Personal BI, Team BI and Corporate BI within one technology being xVelocity. This all works just fine but there may also be scenarios where you need to do it the other way round – converting a Tabular model to Power Pivot. Several use-cases come into my mind but I am sure that the most important one is to making data available offline for e.g. sales people to take it with them on their every day work. And in this blog post I will show how this can be done! But before taking a closer look into how this can be accomplished, lets first see how the import from Power Pivot to SSAS Tabular works. To do this start SQL Server Profiler and connect to your tabular instance. Then create a new Tabular project in Visual Studio based on an existing Power Pivot workbook. At this point you will notice a lot of events happening on our SSAS Tabular server. The most important event for us is “Command End” with the EventSubclass “9 – restore”: SSAS actually restores a backup from a “Model.abf” backup file which is located in our project directory that we just created: So far so good – but where does this file come from? Well, the origin of the file has to be our Excel workbook that we imported. Knowing that all new office formats ending with “x” (.xlsx, .docx, …) are basically ZIP files, we can inspect our original Excel workbook by simply rename it to “.zip”. This allows us to browse the Excel file structure: We will find a folder called “xl” which contains a sub-folder called “model”. This folder contains one item called “item.data”. If you take a closer look at the file size you may realize that both, the “Model.abf” file that we restored and the “item.data” file from our Excel workbook have the exact same size: A Coincidence? Not really! What happens behind the scenes when you import a Power Pivot model into SSAS Tabular is that this “item.data” file gets copied into your project directory and is renamed to “Model.abf” and then restored to the SSAS Tabular workspace instance by using an standard database restore. Having this information probably makes you think: If it works in one direction, why wouldn’t it also work the other way round? And it does! So here are the steps that you need to do in order to restore your SSAS Tabular backup into an Excel Power Pivot workbook: 1. Create a backup of your SSAS Tabular database and rename it to “item.data” 2. Create an empty Excel workbook and add a simple linked table to the Excel data model (which is actually Power Pivot). This is necessary to tell Excel that the workbook contains a Power Pivot model which has to be loaded once the file is opened. 3. Close the Excel workbook and rename it from “MyFile.xlsx” to “MyFile.xlsx.zip” 4. Open the .zip-file in Windows Explorer and locate the “\xl\model\”-folder 5. Replace the “item.data” file with the file that you created in step 1. 6. Rename the .zip-file back to “MyFile.xlsx” 7. Open the Excel Workbook 8. Voilá! You can now work with the data model as with any other Power Pivot model! I tested this with a SSAS Tabular backup from SQL Server 2012 SP1 being restored to the streamed version of Excel from Office 365 with the latest version of Power Pivot. I assume that it also works with older versions but have not tested all combinations yet. There are also some features that will not work, for example roles. If your Tabular database contains roles you will not be able to use this approach. Excel will complain that the Power Pivot model is broken. However, other Tabular features like partitions actually work with the little limitation that you cannot change them later on in the Power Pivot model or process them separately: Another thing to note here is that only up to 3 partitions are allowed, otherwise you will get the same error as for roles. I think this is related to the limitation of 3 partitions for SQL Server Analysis Services Standard Edition as Chris Webb described here. Besides these obvious features there are also some other cool things that you can do in Tabular which are not possible in Power Pivot. Most (or actually all) of them are accessible only by using BIDS Helper – a great THANK YOU to the developers of BIDS Helper at this point! BIDS Helper enables you to add classical multidimensional features also to Tabular models which is not possible using standard Visual Studio only. Those include: • DisplayFolders • Translations (metadata only) • Actions I tested it for DisplayFolders and Actions and both are working also in Power Pivot after the backup was restored and I further assume that all the other things will also work just fine. Simply keep in mind that Power Pivot is basically a fully featured Analysis Services instance running within Excel! For my (and your) convenience I also created a little PowerShell script that does all the work: 1. # Load the assembly with the ZipFile class 2. [System.Reflection.Assembly]::LoadWithPartialName("System.IO.Compression.FileSystem") | Out-Null 3. # Load the assembly to access Analysis Services 4. [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.AnalysisServices") | Out-Null 5. # Also install "Analysis Services PowerShell" according to http://technet.microsoft.com/en-us/library/hh213141.aspx 6. 7. # INPUT-Variables, change these to match your environment 8.$rootFolder = "D:\Test_PowerShell\"
9. $emptyExcelFile =$rootFolder + "EmptyExcel.xlsx"
10. $ssasServerName = "localhost\TAB2012" 11.$ssasDatabaseName = "AdventureWorks"
12.
13. # internal variables
14. $newExcelFile =$rootFolder + $ssasDatabaseName + ".xlsx" 15.$newExcelFileZip = $newExcelFile + ".zip" 16.$unzipFolder = $rootFolder + "TEMP_ExcelUnzipped" 17.$backupFile = $rootFolder +$ssasDatabaseName + ".abf"
18. $itemDestination =$unzipFolder + "\xl\model\item.data"
19.
20. # Copy the empty Excel file and rename it to ".zip"
21. Copy-Item -Path $emptyExcelFile -Destination$newExcelFileZip
22.
23. # Unzip the file using the ZipFile class
24. [System.IO.Compression.ZipFile]::ExtractToDirectory($newExcelFileZip,$unzipFolder)
25.
26. # Create a backup of the SSAS Tabular database
27. Backup-ASDatabase -Server $ssasServerName -Name$ssasDatabaseName -BackupFile $backupFile -AllowOverwrite -ApplyCompression 28. 29. # Copy the backup-file to our extracted Excel folder structure 30. Copy-Item -Path$backupFile -Destination $itemDestination -Force 31. 32. # Check if the target file exists and delete it 33. if (Test-Path -Path$newExcelFile) { Remove-Item -Path $newExcelFile } 34. 35. # Zip the folder-structure again using the ZipFile class and rename it to ".xlsx" 36. [System.IO.Compression.ZipFile]::CreateFromDirectory($unzipFolder, $newExcelFile) 37. 38. # Cleanup the unecessary files 39. Remove-Item -Path$unzipFolder -Recurse
40. Remove-Item -Path $backupFile 41. Remove-Item -Path$newExcelFileZip

The last thing to mention here is that I don’t know if this is officially supported in any way by Microsoft – actually I am pretty sure it is not – so watch out what you are doing and don’t complain if something is not working as expected.