|
|
You're in the
sql server reporting services
group:seriouse problem
sql server reporting services:
when I use union in my script and use parameter, sometime it will cause SQL Server shut down without any warning! It happened 3 times and I am sure VS has some problem. Not sure if any one out there has the same problem???? There are 50 user using the database the same time, you can imagine how sacre I am when I use VS to design report........
To Microsoft:
If I put @var first in my script, VS will auto generate report parameter....it works but if I create this parameter first and use this parameter in my union
I agree with you but you did not answer my quesiton. I have 3 database
instance with same structure. I have to use union to get all the result. I noticed that sometimes VS can shutdown my sql server, this is very scary and hope Microsoft can fix this bug....I believe this is because I use union and parameter together. If you define your paramter (from another dataset) first and use it in your script ( with union ), you might see what I mean. [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> If you are putting T-SQL in the design pane do not declare any variable that > is a report parameter. Just use the @Whatever and RS will create the report > parameter. If for some reason you want to do more with the report parameter > prior to using it then have a second variable that is for the report > parameter. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Wei Ming" <wming@cwalkergroup.com> wrote in message > news:230E1217-2C9B-4583-BCE2-B28482A15291@microsoft.com... > > To Microsoft: > > > > If I put @var first in my script, VS will auto generate report > > parameter....it works but > > if I create this parameter first and use this parameter in my union > > script.....woolala....guess what, my SQL Server shut down ...... :-(( > >
Not use RDL properly might cause some problem, I aware of that, use UNION the
execution order not guarantee is acceptable but use UNION in VS can shut down database is absolutely NOT acceptable. My soluiton is to let VS generate parameter for you, it seems VS can recongnize these parameter better than define it manually..... Hope VS 2005 will not let me phone ring crazy like this morning..... [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> Ahh, you are trying to tie two datasets together. First, although there is a > way to do this I wouldn't necessarily count on this behaviour to stay the > same. That being said, the order that datasets get filled in is based on the > order in the RDL. So look at the RDL and make sure that the dependent > dataset is prior to the second dataset. > > Dataset execution order is not guaranteeded. > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Wei Ming" <wming@cwalkergroup.com> wrote in message > news:40C8EBFC-197F-4276-A82C-9C13E18B520A@microsoft.com... > >I agree with you but you did not answer my quesiton. I have 3 database > > instance with same structure. I have to use union to get all the result. I > > noticed that sometimes VS can shutdown my sql server, this is very scary > > and > > hope Microsoft can fix this bug....I believe this is because I use union > > and > > parameter together. If you define your paramter (from another dataset) > > first > > and use it in your script ( with union ), you might see what I mean. > > > > > > > > > > > > "Bruce L-C [MVP]" wrote: > > > >> If you are putting T-SQL in the design pane do not declare any variable > >> that > >> is a report parameter. Just use the @Whatever and RS will create the > >> report > >> parameter. If for some reason you want to do more with the report > >> parameter > >> prior to using it then have a second variable that is for the report > >> parameter. > >> > >> > >> -- > >> Bruce Loehle-Conger > >> MVP SQL Server Reporting Services > >> > >> "Wei Ming" <wming@cwalkergroup.com> wrote in message > >> news:230E1217-2C9B-4583-BCE2-B28482A15291@microsoft.com... > >> > To Microsoft: > >> > > >> > If I put @var first in my script, VS will auto generate report > >> > parameter....it works but > >> > if I create this parameter first and use this parameter in my union > >> > script.....woolala....guess what, my SQL Server shut down ...... :-(( > >> > >> > >> > >
If you are putting T-SQL in the design pane do not declare any variable that
is a report parameter. Just use the @Whatever and RS will create the report parameter. If for some reason you want to do more with the report parameter prior to using it then have a second variable that is for the report parameter. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Wei Ming" <wming@cwalkergroup.com> wrote in message news:230E1217-2C9B-4583-BCE2-B28482A15291@microsoft.com... > To Microsoft: > > If I put @var first in my script, VS will auto generate report > parameter....it works but > if I create this parameter first and use this parameter in my union > script.....woolala....guess what, my SQL Server shut down ...... :-((
Ahh, you are trying to tie two datasets together. First, although there is a
way to do this I wouldn't necessarily count on this behaviour to stay the same. That being said, the order that datasets get filled in is based on the order in the RDL. So look at the RDL and make sure that the dependent dataset is prior to the second dataset. Dataset execution order is not guaranteeded. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Wei Ming" <wming@cwalkergroup.com> wrote in message news:40C8EBFC-197F-4276-A82C-9C13E18B520A@microsoft.com... >I agree with you but you did not answer my quesiton. I have 3 database > instance with same structure. I have to use union to get all the result. I > noticed that sometimes VS can shutdown my sql server, this is very scary > and > hope Microsoft can fix this bug....I believe this is because I use union > and > parameter together. If you define your paramter (from another dataset) > first > and use it in your script ( with union ), you might see what I mean. > > > > > > "Bruce L-C [MVP]" wrote: > >> If you are putting T-SQL in the design pane do not declare any variable >> that >> is a report parameter. Just use the @Whatever and RS will create the >> report >> parameter. If for some reason you want to do more with the report >> parameter >> prior to using it then have a second variable that is for the report >> parameter. >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "Wei Ming" <wming@cwalkergroup.com> wrote in message >> news:230E1217-2C9B-4583-BCE2-B28482A15291@microsoft.com... >> > To Microsoft: >> > >> > If I put @var first in my script, VS will auto generate report >> > parameter....it works but >> > if I create this parameter first and use this parameter in my union >> > script.....woolala....guess what, my SQL Server shut down ...... :-(( >> >> >>
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 |