This blog has been moved to http://www.t-sql.dk
In regards to this article about named calculations in SSAS, I had the perculiar finding today, that NULLs are handled somewhat differently than I would have expected.
In my case I had constructed a named calculation, just as in the article, by concatenating two columns, both of type string and allowing NULLs.
The perculiar part was, that when the second value was NULL, the whole expression would result in a NULL.
So, in order for the concatenation to succeed, the expression should be as follows:
[Marital Status] + CASE WHEN LEN([Has Children]) > 0 THEN ‘ ‘ + [Has Children] ELSE ” END
SQL Server Analysis Services offers the possibility to create roles, whereby you can manage the access certain users will have to data in the cube(s) on the database. The following is a basic tutorial on how to create a role Limited Access, used to limit the access to the Product dimension of the Adventure Works cube.
First we right-click the Roles collection on the database and select New Role:
Then we give the role a meaningfull name and perhaps a description to distinguish it even more:
Next we add the members of the role, eg. the users:
We can add as many users as we like, even groups to let he IT Administration handle the permissions:
We then need to decide which cube(s) the role is granted access to:
We jump a few steps here in order to get to the basic part of setting dimension security in SSAS 20008.
Select the Dimension Data tab, and select which dimension(s) the role is to be restricted on:
This particullar role is limited to seeing only members Accessories and Bikes, hence Clothing and Components are prohibited:
In order for us to test this newly created role, we can select to browse the cube using the credentials of the role.
This is done in the browse cube dialog:
We then select our new role:
And voilà, the permissions show up as expected:
For more advanced stuff on security in cubes, please refer to: http://www.ssas-info.com/analysis-services-articles/51-security
Although setting the language and collation correctly, it’s not easy to see why a specific MDX would not return the right formatting, in regards to monetary, thousands seperator etc.
There is however a way of forcing the language, through a property available on the calculated measure. In the following example, I’ll show that even though the server settings are da-DK (Danish), the results are displayed as en-US.
First, a screenshot of the server settings:
Then the query, that returns en-US formatting:
For this to work, we need to add: Language=1030 as property to the calculated member, then we get:
See more on FORMAT_STRING and LANGUAGE @ http://msdn.microsoft.com/en-us/library/cc879322.aspx
In general, this can be used to find the port of any service that you might be interested in.
In my case I needed to setup a small testing scenario, involving a PC and a laptop. The PC containing an instance of SSAS that contains the data for the application.
So I needed to setup the firewall to allow the connection to SSAS from the laptop.
In order for me to do that, I needed the port number that the Analysis Services service is listening at. This can be found in two/three easy steps (should be almost the same on Windows 7 and Windows Server 2008 R2)
First you fire up your Task Manager:
From there launch the Resource Monitor and select the Network tab, then look at the TCP connections section:
Tror Ekstra Bladet har fået stavepladen galt i halsen…