So, I upgraded a big project for a customer to 2012 from 2008R2. Everything worked fine, except the last part, where some datamarts was loaded with SSIS from SSAS. They had worked with no problem before, but suddenly, I received the above error code. It made no sense to me, and it was hard to find out, what precisely had happen. The worst, was, that I was able to see the preview in the datasource, but not run the package.
A workaround was to create a linked server to the cube, and then just select from that like so
SELECT * FROM openquery(<ServerName>, ‘<MDX>’)
And that was, properly they way I would have implemented it myself. But having hundreds of packages, rewriting them, was not the way to go.
Instead, I found an old post on google, where a person had the same problem, in an older SQL server. The solution was, to open the connection, click the all botton, and type in “(Format=Tabular)” in the extended properties field. Se the image bellow.
So, yeah…., YIEAKS. But hey, if you find yourself having the same problem, you now know what the solution is 🙂
A common way of showing durations in SSAS, is to format them as HH:MM:SS. A common scenario is to store the durations in seconds. To display them in the HH:MM:SS format, first we have to convert the duration to hours, and then put on the format, like so
CREATE MEMBER CURRENTCUBE.[MEASURES].[someMeasure] AS
[Measures].[someMesureInSeconds]/86400,FORMAT_STRING = “HH:MM:SS”,…
However, this only works if the duration is less than 24 hours.
If it is more, then there is no out the box way to show it in the correct format. To get around that problem, you have to create a mearure as a string. First calc the hours, and then add the minutes and seconds formated as above, like so:
CREATE MEMBER CURRENTCUBE.[Measures].[MesureX]
CSTR(INT([Measures].[LongDurationInSec]/(60*60))) + “:”
– INT([Measures].[LongDurationInSec]/86400)), “mm:ss”)
FORMAT_STRING = “[HH]:MM:SS”, …
Just a short note about analysis services and its cache 🙂
One of the reasons for analysis services fast respond time is its cahce. But what if you want to test a query without using the cache? Well, just use this XMLA Script:
<DatabaseID>Your Database Goes here </DatabaseID>
<CubeID>And or cube id goes here</CubeID>
Also, if you do partial processing, the cache, can in some cases also be invalid. Therefore, after a partial processing, you also want to run the above XMLA script.