Juggling Parameters

I am reporting off a star-schema data warehouse. I have three datasets that I
use to populate parameters, and one master dataset that uses the values from
all three to populate the report. The way I have set up the master dataset
is:
SELECT *
FROM t_policy_info
WHERE month_key = @.month_key AND
paper_desc = @.paper_desc AND
unit_desc = @.unit_desc
Matching on non-key values is very time-consuming. For the @.paper_desc and
@.unit_desc datasets, I'm only pulling back the descriptions so that they
appear in the dropdowns at the top of the report.
How should I configure the datasets so that the master query matches
WHERE month_key = @.month_key AND
paper_key= @.paper_key AND
unit_key = @.unit_key ?
Should the paper and unit datasets also contain the key fields so that they
can be matched in the master dataset? How do I prevent the user from being
prompted for the keys (which they shouldn't)?
This is really a performance issue, and while I could make it work with
straight SQL, I'm not sure how to implement it with Reporting Services.
Thanks,
MikeHave you looked at the parametere Label Field/ Value Field inputs , one of
them is what is displayed to the user and other is what is passed to the
query.?
When you create your query for the main dataset along with the month also
pass the paper_key and unit_key parameters, as input by the user.
HTH
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:8549E9F8-0F83-40A6-9737-864C4C302045@.microsoft.com...
>I am reporting off a star-schema data warehouse. I have three datasets that
>I
> use to populate parameters, and one master dataset that uses the values
> from
> all three to populate the report. The way I have set up the master dataset
> is:
> SELECT *
> FROM t_policy_info
> WHERE month_key = @.month_key AND
> paper_desc = @.paper_desc AND
> unit_desc = @.unit_desc
> Matching on non-key values is very time-consuming. For the @.paper_desc and
> @.unit_desc datasets, I'm only pulling back the descriptions so that they
> appear in the dropdowns at the top of the report.
> How should I configure the datasets so that the master query matches
> WHERE month_key = @.month_key AND
> paper_key= @.paper_key AND
> unit_key = @.unit_key ?
> Should the paper and unit datasets also contain the key fields so that
> they
> can be matched in the master dataset? How do I prevent the user from being
> prompted for the keys (which they shouldn't)?
> This is really a performance issue, and while I could make it work with
> straight SQL, I'm not sure how to implement it with Reporting Services.
> Thanks,
> Mike