|
|
You're in the
sql server reporting services
group:Pains of a lazy user
sql server reporting services:
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.
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) [quoted text, click to view] "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. > >
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 [quoted text, click to view] "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 [quoted text, click to view] "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. >> >> >>
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |