Pains of a lazy user

I've only been using SSRS for a short period, but I've already found myself
on the verge of throwing my computer out of the office window (would be less
spectacular than it sounds - the window's are toughened glass and invariably
shut).
My beef is with the way that the parameter list is deleted from the dataset
when the stored procedure is changed. Why does this happen? Surely I'm not
the only person who having been building a report based on a procedure which
already exists suddenly decides to base it on new version with the same
parameter list of around a dozen parameters? And then, half an hour later,
will change my mind and go back to the original? Meaning (including the
original entering of parameters) I've had to enter 36 parameters and select
their report parameter from a list!
I realise this may sound lazy, but I really can't be bothered doing that.
Please - someone tell me there's a way to assign parameters without having
to use the dataset dialogue box or a way to persist the parameters over to
the new stored procedure.
Thanks in advance.Create a copy of your report (ctrl-c, ctrl-v). View Menu-> code . This
brings up the xml source of the rdl. Search for the name of the stored
procedure and replace it everywhere you find it. Save all.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"rocket salad" <rocketsalad@.discussions.microsoft.com> wrote in message
news:0ADA9C44-5CED-4831-A585-347896F0ECAB@.microsoft.com...
> I've only been using SSRS for a short period, but I've already found
> myself
> on the verge of throwing my computer out of the office window (would be
> less
> spectacular than it sounds - the window's are toughened glass and
> invariably
> shut).
> My beef is with the way that the parameter list is deleted from the
> dataset
> when the stored procedure is changed. Why does this happen? Surely I'm not
> the only person who having been building a report based on a procedure
> which
> already exists suddenly decides to base it on new version with the same
> parameter list of around a dozen parameters? And then, half an hour later,
> will change my mind and go back to the original? Meaning (including the
> original entering of parameters) I've had to enter 36 parameters and
> select
> their report parameter from a list!
> I realise this may sound lazy, but I really can't be bothered doing that.
> Please - someone tell me there's a way to assign parameters without having
> to use the dataset dialogue box or a way to persist the parameters over to
> the new stored procedure.
> Thanks in advance.|||Yup - that would work.
To be honest I haven't spent very much time looking at the rdl xml, I guess
it's better to get to grips with it.
I still find it hard to believe that this default behaviour was chosen as
the best and that it hasn't been a thorn in a lot of user's sides. It's a LOT
easier to delete unwanted parameters than enter new ones. Editting the rdl
directly seems like bypassing SSRS rather than using it.
Am I the only person to have found this an issue?
(BTW - Thanks, Bruce - I'll make use of that tip. Trusty old 'find and
replace' ;o)
"Bruce L-C [MVP]" wrote:
> Create a copy of your report (ctrl-c, ctrl-v). View Menu-> code . This
> brings up the xml source of the rdl. Search for the name of the stored
> procedure and replace it everywhere you find it. Save all.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "rocket salad" <rocketsalad@.discussions.microsoft.com> wrote in message
> news:0ADA9C44-5CED-4831-A585-347896F0ECAB@.microsoft.com...
> > I've only been using SSRS for a short period, but I've already found
> > myself
> > on the verge of throwing my computer out of the office window (would be
> > less
> > spectacular than it sounds - the window's are toughened glass and
> > invariably
> > shut).
> >
> > My beef is with the way that the parameter list is deleted from the
> > dataset
> > when the stored procedure is changed. Why does this happen? Surely I'm not
> > the only person who having been building a report based on a procedure
> > which
> > already exists suddenly decides to base it on new version with the same
> > parameter list of around a dozen parameters? And then, half an hour later,
> > will change my mind and go back to the original? Meaning (including the
> > original entering of parameters) I've had to enter 36 parameters and
> > select
> > their report parameter from a list!
> >
> > I realise this may sound lazy, but I really can't be bothered doing that.
> >
> > Please - someone tell me there's a way to assign parameters without having
> > to use the dataset dialogue box or a way to persist the parameters over to
> > the new stored procedure.
> >
> > Thanks in advance.
>
>|||Well, it is a case of Report Designer trying to help too much. It
automatically creates report parameters for every detected query parameter
of the stored procedure.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"rocket salad" <rocketsalad@.discussions.microsoft.com> wrote in message
news:61713364-3459-43AE-881B-CD075E6334FD@.microsoft.com...
> Yup - that would work.
> To be honest I haven't spent very much time looking at the rdl xml, I
> guess
> it's better to get to grips with it.
> I still find it hard to believe that this default behaviour was chosen as
> the best and that it hasn't been a thorn in a lot of user's sides. It's a
> LOT
> easier to delete unwanted parameters than enter new ones. Editting the rdl
> directly seems like bypassing SSRS rather than using it.
> Am I the only person to have found this an issue?
> (BTW - Thanks, Bruce - I'll make use of that tip. Trusty old 'find and
> replace' ;o)
> "Bruce L-C [MVP]" wrote:
>> Create a copy of your report (ctrl-c, ctrl-v). View Menu-> code . This
>> brings up the xml source of the rdl. Search for the name of the stored
>> procedure and replace it everywhere you find it. Save all.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "rocket salad" <rocketsalad@.discussions.microsoft.com> wrote in message
>> news:0ADA9C44-5CED-4831-A585-347896F0ECAB@.microsoft.com...
>> > I've only been using SSRS for a short period, but I've already found
>> > myself
>> > on the verge of throwing my computer out of the office window (would be
>> > less
>> > spectacular than it sounds - the window's are toughened glass and
>> > invariably
>> > shut).
>> >
>> > My beef is with the way that the parameter list is deleted from the
>> > dataset
>> > when the stored procedure is changed. Why does this happen? Surely I'm
>> > not
>> > the only person who having been building a report based on a procedure
>> > which
>> > already exists suddenly decides to base it on new version with the same
>> > parameter list of around a dozen parameters? And then, half an hour
>> > later,
>> > will change my mind and go back to the original? Meaning (including the
>> > original entering of parameters) I've had to enter 36 parameters and
>> > select
>> > their report parameter from a list!
>> >
>> > I realise this may sound lazy, but I really can't be bothered doing
>> > that.
>> >
>> > Please - someone tell me there's a way to assign parameters without
>> > having
>> > to use the dataset dialogue box or a way to persist the parameters over
>> > to
>> > the new stored procedure.
>> >
>> > Thanks in advance.
>>