Introduction
SSRS Reporting parameters and SSAS cubes......There is a lot to read about on the internet about the bad performance of parameters that are generated by Reporting Services based upon a SSAS Cube. Today, I've ran into this problem too. I've a parameter with a dataset that queries a customer table of about 40000 records. Peanuts for a simple SQL query, but not for a SSAS cube (pfffff). And, I'm not the only one who has encountered this problem. You can read hundreds of blogposts, forumposts and more. This is one blogpost more about this bad cooperation between SSRS and SSAS.
The lab situation is this: we have a main report with a customer parameter and a sub report. I want to pass a Customer list via the parameter to the subreport in order to show detailrecords. In my real word example a map is shown and clicking on a area on the map shows the detail records that belong to a region.
Analyzing the parameter performance problem
The initial problem of a parameter with 40000 records is simple. It doesn't perform! I will show you what kind of issues rise when you create a parameter with 40000 records. First create a dataset with a parameter "Customer" by checking the parameter option in the query window.
A parameter dataset is created (you can't see that because it's hidden). Choose for "Show hidden datasets". If you run the report, you'll notice that the performance is bad..very bad. When you open profiler to take a look at what is happening during cube querying a lot of serialize events happen and these happen often (per 1000) and these are sloooowwww. The serialize results current is a very slow process. So processing the query is very fast but serializing the result for the Report is slow.
If you take a look at this diagram, you can see that the serialize is done from the Compute Cell data part and it's transferred to the client application.
Now, I haven't found a silver bullet unfortunately. But
Chris Webb helped me a bit further. In his blogpost, Chris Web explains this problem a bit further and he gives a solution. Well, sort of but I'll explain this later. Suppose you add a parameter to a dataset according to the following screenshot.
Then a parameter is automatically created with a dataset:
And, the query in this dataset looks like this:
WITH
MEMBER [Measures].[ParameterCaption] AS [Customer].[Customer].CURRENTMEMBER.MEMBER_CAPTION
MEMBER [Measures].[ParameterValue] AS [Customer].[Customer].CURRENTMEMBER.UNIQUENAME
MEMBER [Measures].[ParameterLevel] AS [Customer].[Customer].CURRENTMEMBER.LEVEL.ORDINAL
SELECT
{[Measures].[ParameterCaption],
[Measures].[ParameterValue],
[Measures].[ParameterLevel]} ON COLUMNS ,
[Customer].[Customer].ALLMEMBERS ON ROWS
FROM [Adventure Works]
According to
Chris Webb you can replace this query by an OLEDB query. This query performs much faster than the generated query by SSRS.
WITH
MEMBER MEASURES.DUMMY AS NULL
SELECT
{MEASURES.DUMMY}
ON COLUMNS
, [Customer].[Customer].ALLMEMBERS
DIMENSION PROPERTIES UNIQUE_NAME, MEMBER_CAPTION, LEVEL_NUMBER
ON ROWS
FROM [Adventure Works]
CELL PROPERTIES VALUE
This speeds up the loading the data into the parameter.
Invalid URI : The URI String is too long
The next problem I had was that I got an error when I call a subreport with the same parameter. It seems that there is limitation of 65520 characters that you can pass with a parameter. This is the error:
A limitation of the number of characters that can be passed through a subreport.
Theo Lachevs explains why. There are a couple of options. The best option is to limit the number of characters of the parameter that are passed to the subreport. This is not perfect because of growing the amount of the data somewhere in the future you'll run into problems again and you can't solve it anymore.
Okay, how do we limit the number of characters that are passed to the subreport? Well, Erika Bakse showed in het
blogpost a way to limit the number of members. In this example I've created a main report and a subreport. The main report has a Customer parameter that lists customers
For this blogpost I've created a simple report with a
Tablix. On the
Textbox Properties I've created an
Action with an expression.
This is the expression that is passed to the subreport:
=Join(Parameters!CustomerCustomerName.Label, "],")
This is the output of the expression:
And this expression is without the full membernames and therefore compacted. In the parameter of the subreport this is one large string:
With the following expression you can change these CSV separated string into full membernames:
="[Customer].[Customer Name].&[" + REPLACE(Parameters!Customer.Label(0) + "]", "],", "],[Customer].[Customer Name].&[")
Shown below:
The output of the expression is this:
And now we can pass this to a dataset and filter the records with this list.
Conclusion
This URI problem happens quite often. I encountered this problem on numerous environments with SQL Server 2008, SQL Server 2008 R2 and SQL Server 2012 in different situations. I've also encountered different behaviour between SSRS, Report manager and Reportbuilder.
Greetz
Hennie
