SSRS Multiple Values ​​- The appropriate level for filter implantation

Question

When using multivalued parameters in sql-report services, is it more expedient to implement a list filter using a filter on the data set itself, managing the data area or changing the actual query that controls the data set?

SSRS will support any scenario, so I ask if there is a reason that goes beyond the obvious, why should this be done on one level over another?

It seems to me that modifying the query itself and calling RDBMS to process filtering would be the most efficient, but maybe I am missing something about how the SSRS Data Processing Extension can handle this scenario?

Answer 1

You're right. The transfer path is to pass parameters to the database engine.

Reporting Services should be ideally used for rendering content. The less data you need to transfer back to the client web browser, the faster the report will be displayed.

You can find my answer to a similar entry on how to use the mulit-value parameters.

Passing multiple values ​​for a single parameter in Reporting Services

Hope this helps, but please feel free to ask additional questions that may arise.

Cheers, John

Answer 2

UDF - , - , , . , ( temp table eather):

DECLARE @Param (Value INT)
INSERT INTO @Param (Value) 
SELECT Param FROM dbo.fn_MVParam(@sParameterString,',')
...
where someColumn IN(SELECT Value FROM @Param)

.

, , SQL-, MVP : ...   someColumn IN (@Param) ...

Answer 3

SSRS / . ..