Great,
So basically, in a small networked office setup I described,I will:
1> Install myapp on all 4 machines
2> Install MSDE on the centralserver A
3> Connection string will point to the machine A for datasource
But what about:
1> If I need to start the sqlserver service on clients machine, for e.g. to backup/restore database. How will I do it. Currently I use the following code to create the service controller and then start it if needed:
svc = New ServiceController("MSSQL$MyInstanceName)
What will I do when the service is on the central machine. How to start the service using the above code.
(See my clients will not have a dba and are assumed to not know that there is anything related to sql server on their machines, so we are providing the UI for backup/restore etc and the db functionality is kept as hidden as possible from them, this UI wil
l be in the tools on my vb.net app)
2> Will I need to run any network config utilities on the client machine. I know I will have to set disablenetworkprotocols to false on the server, but is there anything related to network access to be done on the client.
3> Andrea sometime back you mentioned something like, the location to backup should be from the MSDE machine's point of view.. so if PC1 wants to backup the db on it's D:\Backup drive, then what change will I have to do to this code below(which works fine
for a machine which has msde installed)
'--
cn = New SqlConnection(mMasterConnString)
cn.Open()
Dim cm As New SqlCommand
With cm
.Connection = cn
.CommandType = CommandType.Text
.CommandText = "BACKUP DATABASE " & mDBName & " TO DISK = '" & bkpFileWithPath & "' WITH NAME = My Backup', INIT"
.ExecuteNonQuery()
End With
'Note: bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
'---
4> I guess I will take DMO slowly..
Thanks a lot guys.
dev
hi dev_kh,
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:FB209BF1-68B3-489C-A9E3-FD4CDDB6E87A@.microsoft.com...
> Great,
> So basically, in a small networked office setup I described,I will:
> 1> Install myapp on all 4 machines
> 2> Install MSDE on the centralserver A
> 3> Connection string will point to the machine A for datasource
yep =;-D
> But what about:
> 1> If I need to start the sqlserver service on clients machine, for e.g.
to
>backup/restore database. How will I do it. Currently I use the following
code to
>create the service controller and then start it if needed:
> svc = New ServiceController("MSSQL$MyInstanceName)
> What will I do when the service is on the central machine. How to start
the service
>using the above code.
usually the MSDE instance running on the remote server shoul'd be up and
running...
if you do have SQL-DMO [again =;-D ] you can try starting it, but the best
solution is making sure the MSDE instance starts at server startup...
> (See my clients will not have a dba and are assumed to not know that there
is
>anything related to sql server on their machines, so we are providing the
UI for
>backup/restore etc and the db functionality is kept as hidden as possible
from them,
>this UI will be in the tools on my vb.net app)
add a job script to make sure a dayly (?) backup operation is performed at
least..
> 2> Will I need to run any network config utilities on the client machine.
I know I will have
>to set disablenetworkprotocols to false on the server, but is there
anything related to network
>access to be done on the client.
usually not... but wait for WinXP sp2 and then he all will have a lot to do,
related to personal firewall settings =;-D ... and this is good, related to
secuirty concerns...
> 3> Andrea sometime back you mentioned something like, the location to
backup
>should be from the MSDE machine's point of view.. so if PC1 wants to backup
the
> db on it's D:\Backup drive, then what change will I have to do to this
code below(which
> works fine for a machine which has msde installed)
> '--
> cn = New SqlConnection(mMasterConnString)
> cn.Open()
> Dim cm As New SqlCommand
> With cm
> .Connection = cn
> .CommandType = CommandType.Text
> .CommandText = "BACKUP DATABASE " & mDBName & " TO DISK =
'" & bkpFileWithPath & "' WITH NAME = My Backup', INIT"
> .ExecuteNonQuery()
> End With
> 'Note: bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
> '---
nothing...
>bkpFileWithPath argument is: "D:\Backup\MyDB.bak"
will actually point to server's file system... so the db wil be backed up on
server's d:\....
> 4> I guess I will take DMO slowly..
ROTFL
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea,
you mentioned:
"usually the MSDE instance running on the remote server shoul'd be up and
running...
if you do have SQL-DMO [again =;-D ] you can try starting it, but the best
solution is making sure the MSDE instance starts at server startup"
Do you mean making sure that the MSDE is set to startup automatically.. but I want to use the Start Service if needed. So when my app starts I want to see if the service is running, if not I want to start it.
So, on my machine I was using the following line:
svc = New ServiceController("MSSQL$MyInstanceName)
but now when the service is on the central machine then will anything change in the above line of code? I mean will I have to add the server's name/path somewhere in the above line.. after all the service is on the server...
Hope my question is clear now..
Thanks a lot
dev
|||hi dev
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:CAF7632E-4D3E-4EF9-9B75-ADE8414C3632@.microsoft.com...[vbcol=seagreen]
> you mentioned:
best
> Do you mean making sure that the MSDE is set to startup automatically..
>but I want to use the Start Service if needed. So when my app starts I
want
> to see if the service is running, if not I want to start it.
> So, on my machine I was using the following line:
> svc = New ServiceController("MSSQL$MyInstanceName)
> but now when the service is on the central machine then will anything
change
>in the above line of code? I mean will I have to add the server's
name/path
>somewhere in the above line.. after all the service is on the server...
> Hope my question is clear now..
if you are using WMI, you will actually invoke SQL-DMO behind the scenes, so
just directly rely on DMO...
so you have to try a connection, possiblyy with low timeout in order not to
wait to much, and eventaully start the server if needed...
but, again, you shoul'd rely on autostart service method whenever
possible...
make it simple =;-D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You said "if you are using WMI, you will actually invoke SQL-DMO behind the scenes, so just directly rely on DMO... so you have to try a connection, possiblyy with low timeout in order not to wait to much, and eventaully start the server if needed... but,
again, you shoul'd rely on autostart service method whenever
possible... make it simple =;-D"
But this code works fine without wmi or dmo on my machine which has msde.. and if I don't want to use dmo, just simply start the service on the server from the client's machine.. then will I need to add some server name etc on this line of code...
thanks
dev
Saturday, February 25, 2012
Reporting, Visual Studio, layout level, median function
I'd like to calculate the median of a set of values, ie: 1,2,2,2,5 would have
a median of 2.
I've been able to get the average using
sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
How can the median be found using either a function or a math formula?
Thanks,
JimI have no clue if this would work, but it might be worth a try... add a new
text column ( and maybe hide it)...
It's value is
=IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
So the value of this field will be 0 for all rows except the middle row,
which will have the value of the OTHER column with values ... Of course this
only would work if the OTHER column is sorted, and you'd have to account for
an even/odd number of rows...
But then you sum this column in your aggregate row, which would be the
median value...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:440D1DAE-8C20-41D5-819D-C193254626F4@.microsoft.com...
> I'd like to calculate the median of a set of values, ie: 1,2,2,2,5 would
> have
> a median of 2.
> I've been able to get the average using
> sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
> How can the median be found using either a function or a math formula?
> Thanks,
> Jim|||Is your syntax correct? I cant get it to work..
=IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
what does Fields!1 represent?
"Wayne Snyder" wrote:
> I have no clue if this would work, but it might be worth a try... add a new
> text column ( and maybe hide it)...
> It's value is
> =IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
> So the value of this field will be 0 for all rows except the middle row,
> which will have the value of the OTHER column with values ... Of course this
> only would work if the OTHER column is sorted, and you'd have to account for
> an even/odd number of rows...
> But then you sum this column in your aggregate row, which would be the
> median value...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jim" <Jim@.discussions.microsoft.com> wrote in message
> news:440D1DAE-8C20-41D5-819D-C193254626F4@.microsoft.com...
> > I'd like to calculate the median of a set of values, ie: 1,2,2,2,5 would
> > have
> > a median of 2.
> >
> > I've been able to get the average using
> > sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
> >
> > How can the median be found using either a function or a math formula?
> >
> > Thanks,
> > Jim
>
>
a median of 2.
I've been able to get the average using
sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
How can the median be found using either a function or a math formula?
Thanks,
JimI have no clue if this would work, but it might be worth a try... add a new
text column ( and maybe hide it)...
It's value is
=IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
So the value of this field will be 0 for all rows except the middle row,
which will have the value of the OTHER column with values ... Of course this
only would work if the OTHER column is sorted, and you'd have to account for
an even/odd number of rows...
But then you sum this column in your aggregate row, which would be the
median value...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:440D1DAE-8C20-41D5-819D-C193254626F4@.microsoft.com...
> I'd like to calculate the median of a set of values, ie: 1,2,2,2,5 would
> have
> a median of 2.
> I've been able to get the average using
> sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
> How can the median be found using either a function or a math formula?
> Thanks,
> Jim|||Is your syntax correct? I cant get it to work..
=IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
what does Fields!1 represent?
"Wayne Snyder" wrote:
> I have no clue if this would work, but it might be worth a try... add a new
> text column ( and maybe hide it)...
> It's value is
> =IIF(rownumber(nothring)=Count(Fields!1,Value),Fields!Fieldname.Value,0)
> So the value of this field will be 0 for all rows except the middle row,
> which will have the value of the OTHER column with values ... Of course this
> only would work if the OTHER column is sorted, and you'd have to account for
> an even/odd number of rows...
> But then you sum this column in your aggregate row, which would be the
> median value...
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Jim" <Jim@.discussions.microsoft.com> wrote in message
> news:440D1DAE-8C20-41D5-819D-C193254626F4@.microsoft.com...
> > I'd like to calculate the median of a set of values, ie: 1,2,2,2,5 would
> > have
> > a median of 2.
> >
> > I've been able to get the average using
> > sum(fields!1.value)/count(fields!1.value) or Avg(fields!1.value).
> >
> > How can the median be found using either a function or a math formula?
> >
> > Thanks,
> > Jim
>
>
Reporting, notification options for MSDE??
We use MSDE for one, and soon two, of our applications. A key request
we get is for notifications and reports. Thus, when I started looking
into Reporting Services and Notifications, I had an AHA moment. Only
to be shot down by the fact that one technically, and the other from
a licensing POV, require SQL server to work... :-(
Anyone know about anything on the horizon for MSDE-utilizing ISV's
that will give us "in the box" capabilities we can sell through to
our customers? It's a shame that Reporting Services and Notification
Services seem to be effectively unavailable for the MSDE ISV
community.
I would not think it is shame for MS that MSDE does not come with Reporting
service and notification service. Hey, MSDE is very powerful for its price,
free!. If it comes with all bels and whistles that SQL Server has, how can
MS (or any business) make money?
Since you have already get such powerful database engine with no cost, shell
out a few hundred to get some fairly good third party report tools isn't a
difficult option, such as ActiveReport. Even MS Access is a perfect
reporting tool since the broad used base of MS Office (Pro).
"WM" <newsgroups@.getwired.com> wrote in message
news:utIiQatOFHA.508@.TK2MSFTNGP12.phx.gbl...
> We use MSDE for one, and soon two, of our applications. A key request
> we get is for notifications and reports. Thus, when I started looking
> into Reporting Services and Notifications, I had an AHA moment. Only
> to be shot down by the fact that one technically, and the other from
> a licensing POV, require SQL server to work... :-(
> Anyone know about anything on the horizon for MSDE-utilizing ISV's
> that will give us "in the box" capabilities we can sell through to
> our customers? It's a shame that Reporting Services and Notification
> Services seem to be effectively unavailable for the MSDE ISV
> community.
|||It's not a matter of cost - I would pay redist rights for tools
explicitly engineered by MS for use with SQL. I love the fact that
MSDE is available - that it is free is even better. But to have the
ability to generate reports that work as well as Reporting Services
or alerts as rich as Notification Services can would be great...
That said, we will be using third party tools for this, since
Microsoft does not make them available (at any rate) to ISV's for
redistribution...
4/6/2005 2:30:11 PM
Norman Yuan <NotReal@.NotReal.not> wrote in message
<e4xB#7tOFHA.1176@.TK2MSFTNGP12.phx.gbl>
> I would not think it is shame for MS that MSDE does not come with
Reporting
> service and notification service. Hey, MSDE is very powerful for
its price,
> free!. If it comes with all bels and whistles that SQL Server has,
how can
> MS (or any business) make money?
> Since you have already get such powerful database engine with no
cost, shell
> out a few hundred to get some fairly good third party report tools
isn't a[vbcol=seagreen]
> difficult option, such as ActiveReport. Even MS Access is a perfect
> reporting tool since the broad used base of MS Office (Pro).
> "WM" <newsgroups@.getwired.com> wrote in message
> news:utIiQatOFHA.508@.TK2MSFTNGP12.phx.gbl...
request[vbcol=seagreen]
looking[vbcol=seagreen]
Only[vbcol=seagreen]
from[vbcol=seagreen]
ISV's[vbcol=seagreen]
to[vbcol=seagreen]
Notification[vbcol=seagreen]
|||Hi WM,
You'll like the news on the new reporting controls in VS.NET 2005 that will
work with SQL Express then :-)
I quite agree that not having an offering at the MSDE level was an issue.
I've been talking with the product guys about it for ages. ISV's don't want
to have two different reporting strategies or write reports twice.
Personally, I'd like to see an identical feature set from SQL Express up to
SQL Standard Edition and have the differences be limitations on resources
only. That way, ISV's could write apps that target the "platform" and many
customers would just migrate up through the editions as their needs grow.
And the more features like reporting services that are thrown into the
mixture, the faster the resource limitations would be exceeded :-)
Just my 2c though.
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"WM" <newsgroups@.getwired.com> wrote in message
news:OGmALmuOFHA.3048@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> It's not a matter of cost - I would pay redist rights for tools
> explicitly engineered by MS for use with SQL. I love the fact that
> MSDE is available - that it is free is even better. But to have the
> ability to generate reports that work as well as Reporting Services
> or alerts as rich as Notification Services can would be great...
> That said, we will be using third party tools for this, since
> Microsoft does not make them available (at any rate) to ISV's for
> redistribution...
> 4/6/2005 2:30:11 PM
> Norman Yuan <NotReal@.NotReal.not> wrote in message
> <e4xB#7tOFHA.1176@.TK2MSFTNGP12.phx.gbl>
> Reporting
> its price,
> how can
> cost, shell
> isn't a
> request
> looking
> Only
> from
> ISV's
> to
> Notification
|||Cool - thanks for the insight Greg...
4/6/2005 6:48:57 PM
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
<OSPe1MwOFHA.1604@.TK2MSFTNGP10.phx.gbl>
> Hi WM,
> You'll like the news on the new reporting controls in VS.NET 2005
that will
> work with SQL Express then :-)
> I quite agree that not having an offering at the MSDE level was an
issue.
> I've been talking with the product guys about it for ages. ISV's
don't want
> to have two different reporting strategies or write reports twice.
> Personally, I'd like to see an identical feature set from SQL
Express up to
> SQL Standard Edition and have the differences be limitations on
resources
> only. That way, ISV's could write apps that target the "platform"
and many
> customers would just migrate up through the editions as their needs
grow.
> And the more features like reporting services that are thrown into
the[vbcol=seagreen]
> mixture, the faster the resource limitations would be exceeded :-)
> Just my 2c though.
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "WM" <newsgroups@.getwired.com> wrote in message
> news:OGmALmuOFHA.3048@.TK2MSFTNGP10.phx.gbl...
that[vbcol=seagreen]
the[vbcol=seagreen]
Services[vbcol=seagreen]
with[vbcol=seagreen]
has,[vbcol=seagreen]
tools[vbcol=seagreen]
perfect[vbcol=seagreen]
[vbcol=seagreen]
other[vbcol=seagreen]
through[vbcol=seagreen]
we get is for notifications and reports. Thus, when I started looking
into Reporting Services and Notifications, I had an AHA moment. Only
to be shot down by the fact that one technically, and the other from
a licensing POV, require SQL server to work... :-(
Anyone know about anything on the horizon for MSDE-utilizing ISV's
that will give us "in the box" capabilities we can sell through to
our customers? It's a shame that Reporting Services and Notification
Services seem to be effectively unavailable for the MSDE ISV
community.
I would not think it is shame for MS that MSDE does not come with Reporting
service and notification service. Hey, MSDE is very powerful for its price,
free!. If it comes with all bels and whistles that SQL Server has, how can
MS (or any business) make money?
Since you have already get such powerful database engine with no cost, shell
out a few hundred to get some fairly good third party report tools isn't a
difficult option, such as ActiveReport. Even MS Access is a perfect
reporting tool since the broad used base of MS Office (Pro).
"WM" <newsgroups@.getwired.com> wrote in message
news:utIiQatOFHA.508@.TK2MSFTNGP12.phx.gbl...
> We use MSDE for one, and soon two, of our applications. A key request
> we get is for notifications and reports. Thus, when I started looking
> into Reporting Services and Notifications, I had an AHA moment. Only
> to be shot down by the fact that one technically, and the other from
> a licensing POV, require SQL server to work... :-(
> Anyone know about anything on the horizon for MSDE-utilizing ISV's
> that will give us "in the box" capabilities we can sell through to
> our customers? It's a shame that Reporting Services and Notification
> Services seem to be effectively unavailable for the MSDE ISV
> community.
|||It's not a matter of cost - I would pay redist rights for tools
explicitly engineered by MS for use with SQL. I love the fact that
MSDE is available - that it is free is even better. But to have the
ability to generate reports that work as well as Reporting Services
or alerts as rich as Notification Services can would be great...
That said, we will be using third party tools for this, since
Microsoft does not make them available (at any rate) to ISV's for
redistribution...
4/6/2005 2:30:11 PM
Norman Yuan <NotReal@.NotReal.not> wrote in message
<e4xB#7tOFHA.1176@.TK2MSFTNGP12.phx.gbl>
> I would not think it is shame for MS that MSDE does not come with
Reporting
> service and notification service. Hey, MSDE is very powerful for
its price,
> free!. If it comes with all bels and whistles that SQL Server has,
how can
> MS (or any business) make money?
> Since you have already get such powerful database engine with no
cost, shell
> out a few hundred to get some fairly good third party report tools
isn't a[vbcol=seagreen]
> difficult option, such as ActiveReport. Even MS Access is a perfect
> reporting tool since the broad used base of MS Office (Pro).
> "WM" <newsgroups@.getwired.com> wrote in message
> news:utIiQatOFHA.508@.TK2MSFTNGP12.phx.gbl...
request[vbcol=seagreen]
looking[vbcol=seagreen]
Only[vbcol=seagreen]
from[vbcol=seagreen]
ISV's[vbcol=seagreen]
to[vbcol=seagreen]
Notification[vbcol=seagreen]
|||Hi WM,
You'll like the news on the new reporting controls in VS.NET 2005 that will
work with SQL Express then :-)
I quite agree that not having an offering at the MSDE level was an issue.
I've been talking with the product guys about it for ages. ISV's don't want
to have two different reporting strategies or write reports twice.
Personally, I'd like to see an identical feature set from SQL Express up to
SQL Standard Edition and have the differences be limitations on resources
only. That way, ISV's could write apps that target the "platform" and many
customers would just migrate up through the editions as their needs grow.
And the more features like reporting services that are thrown into the
mixture, the faster the resource limitations would be exceeded :-)
Just my 2c though.
Regards,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"WM" <newsgroups@.getwired.com> wrote in message
news:OGmALmuOFHA.3048@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> It's not a matter of cost - I would pay redist rights for tools
> explicitly engineered by MS for use with SQL. I love the fact that
> MSDE is available - that it is free is even better. But to have the
> ability to generate reports that work as well as Reporting Services
> or alerts as rich as Notification Services can would be great...
> That said, we will be using third party tools for this, since
> Microsoft does not make them available (at any rate) to ISV's for
> redistribution...
> 4/6/2005 2:30:11 PM
> Norman Yuan <NotReal@.NotReal.not> wrote in message
> <e4xB#7tOFHA.1176@.TK2MSFTNGP12.phx.gbl>
> Reporting
> its price,
> how can
> cost, shell
> isn't a
> request
> looking
> Only
> from
> ISV's
> to
> Notification
|||Cool - thanks for the insight Greg...
4/6/2005 6:48:57 PM
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
<OSPe1MwOFHA.1604@.TK2MSFTNGP10.phx.gbl>
> Hi WM,
> You'll like the news on the new reporting controls in VS.NET 2005
that will
> work with SQL Express then :-)
> I quite agree that not having an offering at the MSDE level was an
issue.
> I've been talking with the product guys about it for ages. ISV's
don't want
> to have two different reporting strategies or write reports twice.
> Personally, I'd like to see an identical feature set from SQL
Express up to
> SQL Standard Edition and have the differences be limitations on
resources
> only. That way, ISV's could write apps that target the "platform"
and many
> customers would just migrate up through the editions as their needs
grow.
> And the more features like reporting services that are thrown into
the[vbcol=seagreen]
> mixture, the faster the resource limitations would be exceeded :-)
> Just my 2c though.
> Regards,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "WM" <newsgroups@.getwired.com> wrote in message
> news:OGmALmuOFHA.3048@.TK2MSFTNGP10.phx.gbl...
that[vbcol=seagreen]
the[vbcol=seagreen]
Services[vbcol=seagreen]
with[vbcol=seagreen]
has,[vbcol=seagreen]
tools[vbcol=seagreen]
perfect[vbcol=seagreen]
[vbcol=seagreen]
other[vbcol=seagreen]
through[vbcol=seagreen]
Labels:
applications,
database,
key,
lookinginto,
microsoft,
msde,
mysql,
notification,
notifications,
oracle,
reporting,
reports,
requestwe,
server,
sql,
thus
Reporting Website Stops Responding - No Error Message
Hello,
We've had SQL Reporting Services running for over 6 months. This week,
every day, we've experienced a problem where the RS website stops responding.
There's no page could not be displayed message or any other error message,
just an hour glass as the browser tries to go to the URL. Restarting IIS and
the Reporting Services service makes the site available again. There are no
error messages in the RS logs, just processing messages. The server is a
dedicated Windows 2003 Enterprise, 4-CPU server.
Anyone else had this problem?
Thanks,
JasonJason its really sad that microsoft staff has been ignoring your post over a
month now.
Maybe you should try their sp 1 for Reporting Services. I my opinion its an
rewrite of the whole application judging from the sheer size of the
downloaded file.
"Jason" wrote:
> Hello,
> We've had SQL Reporting Services running for over 6 months. This week,
> every day, we've experienced a problem where the RS website stops responding.
> There's no page could not be displayed message or any other error message,
> just an hour glass as the browser tries to go to the URL. Restarting IIS and
> the Reporting Services service makes the site available again. There are no
> error messages in the RS logs, just processing messages. The server is a
> dedicated Windows 2003 Enterprise, 4-CPU server.
> Anyone else had this problem?
> Thanks,
> Jason|||Going to SP1 is a good idea. Note that you have a misconception about the
newsgroup. You are only guaranteed a response from MS if you are using a
managed newsgroup account when you post a question. Otherwise it is peer
supported. A problem like this should go the route of MS support, if it is a
bug / hotfix then there is no charge from product support.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"It a shame" <It a shame@.discussions.microsoft.com> wrote in message
news:574870D8-8FA3-4D7C-B428-EB8CA7805AE0@.microsoft.com...
> Jason its really sad that microsoft staff has been ignoring your post over
a
> month now.
> Maybe you should try their sp 1 for Reporting Services. I my opinion its
an
> rewrite of the whole application judging from the sheer size of the
> downloaded file.
>
> "Jason" wrote:
> > Hello,
> >
> > We've had SQL Reporting Services running for over 6 months. This week,
> > every day, we've experienced a problem where the RS website stops
responding.
> > There's no page could not be displayed message or any other error
message,
> > just an hour glass as the browser tries to go to the URL. Restarting
IIS and
> > the Reporting Services service makes the site available again. There
are no
> > error messages in the RS logs, just processing messages. The server is
a
> > dedicated Windows 2003 Enterprise, 4-CPU server.
> >
> > Anyone else had this problem?
> >
> > Thanks,
> > Jason
We've had SQL Reporting Services running for over 6 months. This week,
every day, we've experienced a problem where the RS website stops responding.
There's no page could not be displayed message or any other error message,
just an hour glass as the browser tries to go to the URL. Restarting IIS and
the Reporting Services service makes the site available again. There are no
error messages in the RS logs, just processing messages. The server is a
dedicated Windows 2003 Enterprise, 4-CPU server.
Anyone else had this problem?
Thanks,
JasonJason its really sad that microsoft staff has been ignoring your post over a
month now.
Maybe you should try their sp 1 for Reporting Services. I my opinion its an
rewrite of the whole application judging from the sheer size of the
downloaded file.
"Jason" wrote:
> Hello,
> We've had SQL Reporting Services running for over 6 months. This week,
> every day, we've experienced a problem where the RS website stops responding.
> There's no page could not be displayed message or any other error message,
> just an hour glass as the browser tries to go to the URL. Restarting IIS and
> the Reporting Services service makes the site available again. There are no
> error messages in the RS logs, just processing messages. The server is a
> dedicated Windows 2003 Enterprise, 4-CPU server.
> Anyone else had this problem?
> Thanks,
> Jason|||Going to SP1 is a good idea. Note that you have a misconception about the
newsgroup. You are only guaranteed a response from MS if you are using a
managed newsgroup account when you post a question. Otherwise it is peer
supported. A problem like this should go the route of MS support, if it is a
bug / hotfix then there is no charge from product support.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"It a shame" <It a shame@.discussions.microsoft.com> wrote in message
news:574870D8-8FA3-4D7C-B428-EB8CA7805AE0@.microsoft.com...
> Jason its really sad that microsoft staff has been ignoring your post over
a
> month now.
> Maybe you should try their sp 1 for Reporting Services. I my opinion its
an
> rewrite of the whole application judging from the sheer size of the
> downloaded file.
>
> "Jason" wrote:
> > Hello,
> >
> > We've had SQL Reporting Services running for over 6 months. This week,
> > every day, we've experienced a problem where the RS website stops
responding.
> > There's no page could not be displayed message or any other error
message,
> > just an hour glass as the browser tries to go to the URL. Restarting
IIS and
> > the Reporting Services service makes the site available again. There
are no
> > error messages in the RS logs, just processing messages. The server is
a
> > dedicated Windows 2003 Enterprise, 4-CPU server.
> >
> > Anyone else had this problem?
> >
> > Thanks,
> > Jason
Reporting web services
Has anybody used the sql reporting services web service?
If so, can anyone share an example?
I have searched google and didn't find nothing!!!
Thank you!
Personally I'm interested in an example of any kind of web service. Thanks.|||I created a DotNetNuke module to display report from MS SQL Reporting Services. Demo and EXE program can be downloaded from http://dnndev.icpconline.com. In VS 2003, I created a web ref to the server web service URL (ie. http://yourserver/reportserver/reportservice.asmx). The web service exposes method to retrieve reports from the server.
Source code is available to authorized developers.
Reporting WEB Service Timeout
I have succefully connected via VB.NET to the reporting service
and executed the UpdateReportExecutionSnapshot(strResult) method
to update the snapshot of reports. But when the report generation takes long
it reports me the following error:
An unhandled exception of type 'System.Net.WebException' occurred in
system.web.services.dll
Additional information: The operation has timed-out.
What should I do so it doesnt timeout so soon?
Thanks.
MPGo to Site Settings from the Report Manager site. Under "Report Execution
Timeout" modify the timeout setting.
Adrian Maull
"Minas Papageorgiou" <MinasPapageorgiou@.discussions.microsoft.com> wrote in
message news:0A4E573B-F004-4CB3-B5E6-D70719216056@.microsoft.com...
> I have succefully connected via VB.NET to the reporting service
> and executed the UpdateReportExecutionSnapshot(strResult) method
> to update the snapshot of reports. But when the report generation takes
long
> it reports me the following error:
> An unhandled exception of type 'System.Net.WebException' occurred in
> system.web.services.dll
> Additional information: The operation has timed-out.
> What should I do so it doesnt timeout so soon?
> Thanks.
> MP
>
and executed the UpdateReportExecutionSnapshot(strResult) method
to update the snapshot of reports. But when the report generation takes long
it reports me the following error:
An unhandled exception of type 'System.Net.WebException' occurred in
system.web.services.dll
Additional information: The operation has timed-out.
What should I do so it doesnt timeout so soon?
Thanks.
MPGo to Site Settings from the Report Manager site. Under "Report Execution
Timeout" modify the timeout setting.
Adrian Maull
"Minas Papageorgiou" <MinasPapageorgiou@.discussions.microsoft.com> wrote in
message news:0A4E573B-F004-4CB3-B5E6-D70719216056@.microsoft.com...
> I have succefully connected via VB.NET to the reporting service
> and executed the UpdateReportExecutionSnapshot(strResult) method
> to update the snapshot of reports. But when the report generation takes
long
> it reports me the following error:
> An unhandled exception of type 'System.Net.WebException' occurred in
> system.web.services.dll
> Additional information: The operation has timed-out.
> What should I do so it doesnt timeout so soon?
> Thanks.
> MP
>
Reporting Web Front End
Hi,
I need to give my clients access to their data for reporting which is
hosted on a web server in SQL server 2005. Basically they need to be
able to write any ad-hoc reports that they need at any time.
My first instinct was to create static reports but this will not suit
their requirements.
what i need to know is whether reporing services would be the best
tool to offer them but im not sure as i only want to give them access
to a reporting tool through the secure section of their website. if
anyone has any ideas on this then please let me know.
my second solution was to allow them to download a copy of their
existing website in access (an environment in which they are familiar)
for thei reporting needs.
any help or guidance on this appreciated
thanks
CGOn Feb 20, 4:31 am, csgraham74 <csgraha...@.gmail.com> wrote:
> Hi,
> I need to give my clients access to their data for reporting which is
> hosted on a web server in SQL server 2005. Basically they need to be
> able to write any ad-hoc reports that they need at any time.
> My first instinct was to create static reports but this will not suit
> their requirements.
> what i need to know is whether reporing services would be the best
> tool to offer them but im not sure as i only want to give them access
> to a reporting tool through the secure section of their website. if
> anyone has any ideas on this then please let me know.
> my second solution was to allow them to download a copy of their
> existing website in access (an environment in which they are familiar)
> for thei reporting needs.
> any help or guidance on this appreciated
> thanks
> CG
I would suggest looking into the Report Model side of SSRS/Reporting
Services (http://msdn2.microsoft.com/en-us/library/ms167048.aspx ).
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
I need to give my clients access to their data for reporting which is
hosted on a web server in SQL server 2005. Basically they need to be
able to write any ad-hoc reports that they need at any time.
My first instinct was to create static reports but this will not suit
their requirements.
what i need to know is whether reporing services would be the best
tool to offer them but im not sure as i only want to give them access
to a reporting tool through the secure section of their website. if
anyone has any ideas on this then please let me know.
my second solution was to allow them to download a copy of their
existing website in access (an environment in which they are familiar)
for thei reporting needs.
any help or guidance on this appreciated
thanks
CGOn Feb 20, 4:31 am, csgraham74 <csgraha...@.gmail.com> wrote:
> Hi,
> I need to give my clients access to their data for reporting which is
> hosted on a web server in SQL server 2005. Basically they need to be
> able to write any ad-hoc reports that they need at any time.
> My first instinct was to create static reports but this will not suit
> their requirements.
> what i need to know is whether reporing services would be the best
> tool to offer them but im not sure as i only want to give them access
> to a reporting tool through the secure section of their website. if
> anyone has any ideas on this then please let me know.
> my second solution was to allow them to download a copy of their
> existing website in access (an environment in which they are familiar)
> for thei reporting needs.
> any help or guidance on this appreciated
> thanks
> CG
I would suggest looking into the Report Model side of SSRS/Reporting
Services (http://msdn2.microsoft.com/en-us/library/ms167048.aspx ).
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
reporting views
Hi
We are using SQL reporting services as the reports engine on our projects.
Some reports come with a table view and a chart view. User wants to see
(print) the table report first by default. The chart report is optional.
The original approach is to have a link (button) on the first report; user
can click on it to see the chart report. However, since two trips will be
made to the data source, user might see different data because of the delay.
Is there a way to avoid that? We want two reports to have the same data.
Does SQL reporting service provide "Views"? So users can retrieve the
report and select different views without going back to the data source?
Thanks in advance!You can't build two different reports on the same query execution but what
you could do is have both the table and the chart in the same report. Set
the visibility propery on each to a parameter that tells which to display.
Have a link on the report that toggles between them.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"James Huang" <jianh@.avanade.com> wrote in message
news:unjgemapEHA.324@.TK2MSFTNGP11.phx.gbl...
> Hi
> We are using SQL reporting services as the reports engine on our projects.
> Some reports come with a table view and a chart view. User wants to see
> (print) the table report first by default. The chart report is optional.
> The original approach is to have a link (button) on the first report; user
> can click on it to see the chart report. However, since two trips will be
> made to the data source, user might see different data because of the
> delay.
> Is there a way to avoid that? We want two reports to have the same data.
> Does SQL reporting service provide "Views"? So users can retrieve the
> report and select different views without going back to the data source?
> Thanks in advance!
>
We are using SQL reporting services as the reports engine on our projects.
Some reports come with a table view and a chart view. User wants to see
(print) the table report first by default. The chart report is optional.
The original approach is to have a link (button) on the first report; user
can click on it to see the chart report. However, since two trips will be
made to the data source, user might see different data because of the delay.
Is there a way to avoid that? We want two reports to have the same data.
Does SQL reporting service provide "Views"? So users can retrieve the
report and select different views without going back to the data source?
Thanks in advance!You can't build two different reports on the same query execution but what
you could do is have both the table and the chart in the same report. Set
the visibility propery on each to a parameter that tells which to display.
Have a link on the report that toggles between them.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"James Huang" <jianh@.avanade.com> wrote in message
news:unjgemapEHA.324@.TK2MSFTNGP11.phx.gbl...
> Hi
> We are using SQL reporting services as the reports engine on our projects.
> Some reports come with a table view and a chart view. User wants to see
> (print) the table report first by default. The chart report is optional.
> The original approach is to have a link (button) on the first report; user
> can click on it to see the chart report. However, since two trips will be
> made to the data source, user might see different data because of the
> delay.
> Is there a way to avoid that? We want two reports to have the same data.
> Does SQL reporting service provide "Views"? So users can retrieve the
> report and select different views without going back to the data source?
> Thanks in advance!
>
Reporting using HTML??
Hi,
I am developing a data management system using ASP.net 2.0 and Sql server 2000.
Now I am dveloping some reports for the INVOICE, PACKING LIST etc.
Is there any tools for achieve thie purpose in ASP.net 2.0??
I was using crystal reports in legacy system, but crystal reports is too heavy and lots of problem, dont want to
use it this time.
I guess HTML is light. but dont know how?
All I came up with is using abosolute positioning is a aspx file. Is there any advanced skill???
Your help is appreciated!
Joseph
Hi,
In my applications I observed that reports especially in Excel or PDF reports are decreased in size after the SP2 for RS.
I guess this is also true for RS2005
Also internet printing may be a good feature for printing your reports from HTML
Eralper
http://www.kodyaz.com
|||Hi
If you are still looking for a report application to handle your reports via SQL Server and you dont want to use Crystal Reports - then use SQL Server Reporting Services. This application is still new but it is directly compatible with SQL Server.
I am developing a data management system using ASP.net 2.0 and Sql server 2000.
Now I am dveloping some reports for the INVOICE, PACKING LIST etc.
Is there any tools for achieve thie purpose in ASP.net 2.0??
I was using crystal reports in legacy system, but crystal reports is too heavy and lots of problem, dont want to
use it this time.
I guess HTML is light. but dont know how?
All I came up with is using abosolute positioning is a aspx file. Is there any advanced skill???
Your help is appreciated!
Joseph
Hi,
In my applications I observed that reports especially in Excel or PDF reports are decreased in size after the SP2 for RS.
I guess this is also true for RS2005
Also internet printing may be a good feature for printing your reports from HTML
Eralper
http://www.kodyaz.com
|||Hi
If you are still looking for a report application to handle your reports via SQL Server and you dont want to use Crystal Reports - then use SQL Server Reporting Services. This application is still new but it is directly compatible with SQL Server.
reporting user access rights on SQL7
I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000 (i
n
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
n
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
reporting user access rights on SQL7
I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000 (in
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
reporting total disk space
Has anyone got a way of reporting total disk space for
each drive on a server ?
I can use the DOS DIR command to report free space, but I
want to also get total space !
TIA.You can use xp_fixeddrives. It isn't documented, nor supported so all the regular warnings apply.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Jim
Check it out
CREATE table DriveTable (Drive varchar(10),[MB Free] int)
INSERT into Drivetable Exec xp_fixeddrives
SELECT * FROM DriveTable
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Hi Jim,
As well as the xp_fixeddrives the information is also easily available
through WMI scripting.
Here's one I found somewhere and modified to work in DTS as an active x
script. But I now mainly use a windows scripting host version to go get disk
information off all available servers. It was needed as I was told that
xp_fixeddrives doesn't work properly on either SAN/Clusters/multi instanced
servers (or a combination of all three). Not sure why/how xp_fixeddrives
doesn't work or under which scenarios, but had to get the WMI version
working all the same.
Function Main()strServer = "SomeMachineSomewhere"Const HARD_DISK = 3set
objLocator = CreateObject("WbemScripting.SWbemLocator")Set objServices =objLocator.ConnectServer(strServer, "root\cimv2")
objServices.Security_.ImpersonationLevel = 3 Set colInstances =objServices.ExecQuery("SELECT * FROM Win32_LogicalDisk WHERE DriveType = " &
HARD_DISK & "")For Each Drive In colInstances If Not IsNull(Drive.Size)
Then MsgBox ("Drive " & Drive.deviceid & " Total Size: "
&round(Drive.Size/1024/1024/1024,1) & " Free Space: "
&round(Drive.FreeSpace/1024/1024/1024,1) ) Else MsgBox ("Drive "
& Drive.deviceid & " is not available.") End IfNext Main =DTSTaskExecResult_SuccessEnd FunctionRegards,Nick"Jim Trowbridge"
<jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||This function will give you total space for any given drive:
CREATE FUNCTION dbo.GetDriveSize
(@.driveletter CHAR(1))
RETURNS NUMERIC(20)
BEGIN
DECLARE @.rs INTEGER, @.fso INTEGER, @.getdrive VARCHAR(13), @.drv INTEGER,
@.drivesize VARCHAR(20)
SET @.getdrive = 'GetDrive("' + @.driveletter + '")'
EXEC @.rs = sp_OACreate 'Scripting.FileSystemObject', @.fso OUTPUT
IF @.rs = 0
EXEC @.rs = sp_OAMethod @.fso, @.getdrive, @.drv OUTPUT
IF @.rs = 0
EXEC @.rs = sp_OAGetProperty @.drv,'TotalSize', @.drivesize OUTPUT
IF @.rs<> 0
SET @.drivesize = NULL
EXEC sp_OADestroy @.drv
EXEC sp_OADestroy @.fso
RETURN @.drivesize
END
GO
SELECT dbo.GetDriveSize('C')
--
David Portas
--
Please reply only to the newsgroup
--
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Yet another way :-)
use master
go
CREATE PROCEDURE sp_diskspace
AS
SET NOCOUNT ON
DECLARE @.hr int
DECLARE @.fso int
DECLARE @.drive char(1)
DECLARE @.odrive int
DECLARE @.TotalSize varchar(20)
DECLARE @.MB bigint ; SET @.MB = 1048576
CREATE TABLE #drives (drive char(1) PRIMARY KEY,
FreeSpace int NULL,
TotalSize int NULL)
INSERT #drives(drive,FreeSpace)
EXEC master.dbo.xp_fixeddrives
EXEC @.hr=sp_OACreate 'Scripting.FileSystemObject',@.fso OUT
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
DECLARE dcur CURSOR LOCAL FAST_FORWARD
FOR SELECT drive from #drives
ORDER by drive
OPEN dcur
FETCH NEXT FROM dcur INTO @.drive
WHILE @.@.FETCH_STATUS=0
BEGIN
EXEC @.hr = sp_OAMethod @.fso,'GetDrive', @.odrive OUT, @.drive
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
EXEC @.hr = sp_OAGetProperty @.odrive,'TotalSize', @.TotalSize OUT
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.odrive
UPDATE #drives
SET TotalSize=@.TotalSize/@.MB
WHERE drive=@.drive
FETCH NEXT FROM dcur INTO @.drive
END
CLOSE dcur
DEALLOCATE dcur
EXEC @.hr=sp_OADestroy @.fso
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
SELECT drive,
FreeSpace as 'Free(MB)',
TotalSize as 'Total(MB)',
CAST((FreeSpace/(TotalSize*1.0))*100.0 as int) as 'Free(%)'
FROM #drives
ORDER BY drive
DROP TABLE #drives
RETURN
go
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
Has anyone got a way of reporting total disk space for
each drive on a server ?
I can use the DOS DIR command to report free space, but I
want to also get total space !
TIA.
each drive on a server ?
I can use the DOS DIR command to report free space, but I
want to also get total space !
TIA.You can use xp_fixeddrives. It isn't documented, nor supported so all the regular warnings apply.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Jim
Check it out
CREATE table DriveTable (Drive varchar(10),[MB Free] int)
INSERT into Drivetable Exec xp_fixeddrives
SELECT * FROM DriveTable
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Hi Jim,
As well as the xp_fixeddrives the information is also easily available
through WMI scripting.
Here's one I found somewhere and modified to work in DTS as an active x
script. But I now mainly use a windows scripting host version to go get disk
information off all available servers. It was needed as I was told that
xp_fixeddrives doesn't work properly on either SAN/Clusters/multi instanced
servers (or a combination of all three). Not sure why/how xp_fixeddrives
doesn't work or under which scenarios, but had to get the WMI version
working all the same.
Function Main()strServer = "SomeMachineSomewhere"Const HARD_DISK = 3set
objLocator = CreateObject("WbemScripting.SWbemLocator")Set objServices =objLocator.ConnectServer(strServer, "root\cimv2")
objServices.Security_.ImpersonationLevel = 3 Set colInstances =objServices.ExecQuery("SELECT * FROM Win32_LogicalDisk WHERE DriveType = " &
HARD_DISK & "")For Each Drive In colInstances If Not IsNull(Drive.Size)
Then MsgBox ("Drive " & Drive.deviceid & " Total Size: "
&round(Drive.Size/1024/1024/1024,1) & " Free Space: "
&round(Drive.FreeSpace/1024/1024/1024,1) ) Else MsgBox ("Drive "
& Drive.deviceid & " is not available.") End IfNext Main =DTSTaskExecResult_SuccessEnd FunctionRegards,Nick"Jim Trowbridge"
<jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||This function will give you total space for any given drive:
CREATE FUNCTION dbo.GetDriveSize
(@.driveletter CHAR(1))
RETURNS NUMERIC(20)
BEGIN
DECLARE @.rs INTEGER, @.fso INTEGER, @.getdrive VARCHAR(13), @.drv INTEGER,
@.drivesize VARCHAR(20)
SET @.getdrive = 'GetDrive("' + @.driveletter + '")'
EXEC @.rs = sp_OACreate 'Scripting.FileSystemObject', @.fso OUTPUT
IF @.rs = 0
EXEC @.rs = sp_OAMethod @.fso, @.getdrive, @.drv OUTPUT
IF @.rs = 0
EXEC @.rs = sp_OAGetProperty @.drv,'TotalSize', @.drivesize OUTPUT
IF @.rs<> 0
SET @.drivesize = NULL
EXEC sp_OADestroy @.drv
EXEC sp_OADestroy @.fso
RETURN @.drivesize
END
GO
SELECT dbo.GetDriveSize('C')
--
David Portas
--
Please reply only to the newsgroup
--
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
> Has anyone got a way of reporting total disk space for
> each drive on a server ?
> I can use the DOS DIR command to report free space, but I
> want to also get total space !
> TIA.
>|||Yet another way :-)
use master
go
CREATE PROCEDURE sp_diskspace
AS
SET NOCOUNT ON
DECLARE @.hr int
DECLARE @.fso int
DECLARE @.drive char(1)
DECLARE @.odrive int
DECLARE @.TotalSize varchar(20)
DECLARE @.MB bigint ; SET @.MB = 1048576
CREATE TABLE #drives (drive char(1) PRIMARY KEY,
FreeSpace int NULL,
TotalSize int NULL)
INSERT #drives(drive,FreeSpace)
EXEC master.dbo.xp_fixeddrives
EXEC @.hr=sp_OACreate 'Scripting.FileSystemObject',@.fso OUT
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
DECLARE dcur CURSOR LOCAL FAST_FORWARD
FOR SELECT drive from #drives
ORDER by drive
OPEN dcur
FETCH NEXT FROM dcur INTO @.drive
WHILE @.@.FETCH_STATUS=0
BEGIN
EXEC @.hr = sp_OAMethod @.fso,'GetDrive', @.odrive OUT, @.drive
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
EXEC @.hr = sp_OAGetProperty @.odrive,'TotalSize', @.TotalSize OUT
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.odrive
UPDATE #drives
SET TotalSize=@.TotalSize/@.MB
WHERE drive=@.drive
FETCH NEXT FROM dcur INTO @.drive
END
CLOSE dcur
DEALLOCATE dcur
EXEC @.hr=sp_OADestroy @.fso
IF @.hr <> 0 EXEC sp_OAGetErrorInfo @.fso
SELECT drive,
FreeSpace as 'Free(MB)',
TotalSize as 'Total(MB)',
CAST((FreeSpace/(TotalSize*1.0))*100.0 as int) as 'Free(%)'
FROM #drives
ORDER BY drive
DROP TABLE #drives
RETURN
go
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jim Trowbridge" <jtrowbridge@.adelaidebank.com.au> wrote in message
news:01d701c3769e$8d9ca6f0$a001280a@.phx.gbl...
Has anyone got a way of reporting total disk space for
each drive on a server ?
I can use the DOS DIR command to report free space, but I
want to also get total space !
TIA.
Reporting tools ?
Hi,
Is there a Reporting tools in SQL Server Standard Edition ? or it's actually
refering to the Analysis Services ?
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting Services is a separate product which can be used if you have
a valid SQL Server 2k > licence, it not stuck to the analysis servces
but can keep benefit of this, due to the fact that you can use MDX
queries to access your database. The "tool set" to create Reporting
Services is brought to the dveloper by Visual Studio 2003 >.
HTH, Jens
|||Yes, SQL Server 2005 Reporting Services is included in Standard Edition
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:58e8077f9b87b@.uwe...
> Hi,
> Is there a Reporting tools in SQL Server Standard Edition ? or it's
> actually
> refering to the Analysis Services ?
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...-msde/200512/1
Is there a Reporting tools in SQL Server Standard Edition ? or it's actually
refering to the Analysis Services ?
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting Services is a separate product which can be used if you have
a valid SQL Server 2k > licence, it not stuck to the analysis servces
but can keep benefit of this, due to the fact that you can use MDX
queries to access your database. The "tool set" to create Reporting
Services is brought to the dveloper by Visual Studio 2003 >.
HTH, Jens
|||Yes, SQL Server 2005 Reporting Services is included in Standard Edition
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:58e8077f9b87b@.uwe...
> Hi,
> Is there a Reporting tools in SQL Server Standard Edition ? or it's
> actually
> refering to the Analysis Services ?
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting tool, loader, explorer for database
We welcome very much expert suggestions for our software
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime team
I could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegro ups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>
|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime team
I could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegro ups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>
|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
Reporting tool, loader, explorer for database
We welcome very much expert suggestions for our software
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime teamI could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegroups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime teamI could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegroups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
Reporting tool, loader, explorer for database
We welcome very much expert suggestions for our software
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime teamI could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegroups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
for exploring / loading / Reporting from database,
http://cam70.sta.uniroma1.it/TechnicalPreview/
free lifetime licence for experts.
thank you for your help.
the Datatime teamI could not open the link
"The page cannot be displayed"
<expertware@.libero.it> wrote in message
news:1120809575.409576.50060@.g47g2000cwa.googlegroups.com...
> We welcome very much expert suggestions for our software
> for exploring / loading / Reporting from database,
> http://cam70.sta.uniroma1.it/TechnicalPreview/
> free lifetime licence for experts.
> thank you for your help.
> the Datatime team
>|||Yes, a power interruption turned out the server.
Now it is on again.
Thanks.
Looking forward your suggestions!
http://cam70.sta.uniroma1.it/TechnicalPreview/
Reporting Tool Information
I am investigating whether there might be some commerical package that
might meet this kind of requirements.
I need a reporting system that will allow users (e.g. programmers for
the users) to write their own reports. However, I need to be able to
limit access to particular records within the database.
I have table used to run the business that contain information related
to many different users. I want users to be ablet to run queries
against these tables (abeit indirectly) and have automatic filters
applied that limit the records they can select.
In other words having
"WHERE USERID="12324" automatically placed on any query the user runs
(presumably indirectly).does your users will create reports themself or only the developpers will
create reports and the users will use these reports?
for the second case, near any reporting tool do the job, its the role of the
developper to use correctly the user login into the SQL queries.
for the first case, Microsoft Report Builder, Business Objects, Cognos
ReportNet, can allow your users to create reports and apply security
automatically.
I think there is more tools on the market.
also, you can secure the rows in the database directly by creating views
where the security is applied, so the user will always query these views
instead-of the tables. (for example, in SQL Server you can use the
suser_sname() function to retrieve the login name of the current user)
but I recommand to take a look at OLAP cubes.
this technology is better to manage and apply a good security.
<faceman28208@.yahoo.com> wrote in message
news:1155048912.857244.303540@.h48g2000cwc.googlegroups.com...
>I am investigating whether there might be some commerical package that
> might meet this kind of requirements.
> I need a reporting system that will allow users (e.g. programmers for
> the users) to write their own reports. However, I need to be able to
> limit access to particular records within the database.
> I have table used to run the business that contain information related
> to many different users. I want users to be ablet to run queries
> against these tables (abeit indirectly) and have automatic filters
> applied that limit the records they can select.
> In other words having
> "WHERE USERID="12324" automatically placed on any query the user runs
> (presumably indirectly).
>
might meet this kind of requirements.
I need a reporting system that will allow users (e.g. programmers for
the users) to write their own reports. However, I need to be able to
limit access to particular records within the database.
I have table used to run the business that contain information related
to many different users. I want users to be ablet to run queries
against these tables (abeit indirectly) and have automatic filters
applied that limit the records they can select.
In other words having
"WHERE USERID="12324" automatically placed on any query the user runs
(presumably indirectly).does your users will create reports themself or only the developpers will
create reports and the users will use these reports?
for the second case, near any reporting tool do the job, its the role of the
developper to use correctly the user login into the SQL queries.
for the first case, Microsoft Report Builder, Business Objects, Cognos
ReportNet, can allow your users to create reports and apply security
automatically.
I think there is more tools on the market.
also, you can secure the rows in the database directly by creating views
where the security is applied, so the user will always query these views
instead-of the tables. (for example, in SQL Server you can use the
suser_sname() function to retrieve the login name of the current user)
but I recommand to take a look at OLAP cubes.
this technology is better to manage and apply a good security.
<faceman28208@.yahoo.com> wrote in message
news:1155048912.857244.303540@.h48g2000cwc.googlegroups.com...
>I am investigating whether there might be some commerical package that
> might meet this kind of requirements.
> I need a reporting system that will allow users (e.g. programmers for
> the users) to write their own reports. However, I need to be able to
> limit access to particular records within the database.
> I have table used to run the business that contain information related
> to many different users. I want users to be ablet to run queries
> against these tables (abeit indirectly) and have automatic filters
> applied that limit the records they can select.
> In other words having
> "WHERE USERID="12324" automatically placed on any query the user runs
> (presumably indirectly).
>
Labels:
commerical,
database,
investigating,
meet,
microsoft,
mysql,
oracle,
package,
reporting,
requirements,
server,
sql,
system,
thatmight,
tool
reporting tool evaluation
I'm assigned the task to review and recommend a reporting tool for our project. Since I had virtually no experience with reporting before, just did some research and came down with two choices: Crystal Reports and StyleReport. The development will be done in Java so the tool must provide a Java api.
Functionality wise StyleReport is definitely superior, bug Crystal seems to be around longer and have more books and other information. One major problem with using Crystal is that rather lacking Java api, which is very new and thin. Like to see if any one had experience using Crystal's java api in a large scale reporting server environment, and what's the result.
Any feedback would be appreciated!I have limited experience with crystal's new java api so can't offer much help there, but have worked with stylereport for a while and highly recommend it. it is easily the most powerful reporting tool on the market. Just saw their 7.0 and a lots of cool new features. We run a reporting server on linux with stylereport running in the same web app, and it worked out great so far.
Functionality wise StyleReport is definitely superior, bug Crystal seems to be around longer and have more books and other information. One major problem with using Crystal is that rather lacking Java api, which is very new and thin. Like to see if any one had experience using Crystal's java api in a large scale reporting server environment, and what's the result.
Any feedback would be appreciated!I have limited experience with crystal's new java api so can't offer much help there, but have worked with stylereport for a while and highly recommend it. it is easily the most powerful reporting tool on the market. Just saw their 7.0 and a lots of cool new features. We run a reporting server on linux with stylereport running in the same web app, and it worked out great so far.
Reporting Test Web Environment
Has anyone come up with a way to deploy reports to a test environment without
purchasing a new server and a second copy of Reporting Services? I would
like to have second website with a copy of our live site for testing purposes
but we don't have the resources or the demand to warrant a second server.
There's nothing that I can find in the RS documentation to create a second
instance. I tried making a new virtual web in IIS and copying the files to
the web's underlying file structure but that did not work.
Any advice or guidance would be greatly appreciated.http://msdn2.microsoft.com/en-us/library/ms403426.aspx
"Stuart" <Stuart@.discussions.microsoft.com> wrote in message
news:4995111C-5CDE-439A-A1F0-9B75D44EBBF7@.microsoft.com...
> Has anyone come up with a way to deploy reports to a test environment
> without
> purchasing a new server and a second copy of Reporting Services? I would
> like to have second website with a copy of our live site for testing
> purposes
> but we don't have the resources or the demand to warrant a second server.
> There's nothing that I can find in the RS documentation to create a second
> instance. I tried making a new virtual web in IIS and copying the files
> to
> the web's underlying file structure but that did not work.
> Any advice or guidance would be greatly appreciated.|||Thanks!
"Immy" wrote:
> http://msdn2.microsoft.com/en-us/library/ms403426.aspx
> "Stuart" <Stuart@.discussions.microsoft.com> wrote in message
> news:4995111C-5CDE-439A-A1F0-9B75D44EBBF7@.microsoft.com...
> > Has anyone come up with a way to deploy reports to a test environment
> > without
> > purchasing a new server and a second copy of Reporting Services? I would
> > like to have second website with a copy of our live site for testing
> > purposes
> > but we don't have the resources or the demand to warrant a second server.
> > There's nothing that I can find in the RS documentation to create a second
> > instance. I tried making a new virtual web in IIS and copying the files
> > to
> > the web's underlying file structure but that did not work.
> >
> > Any advice or guidance would be greatly appreciated.
>
>|||or can you use a SQL Server Developers edition for testing; or is it
just for development'
Stuart wrote:
> Has anyone come up with a way to deploy reports to a test environment without
> purchasing a new server and a second copy of Reporting Services? I would
> like to have second website with a copy of our live site for testing purposes
> but we don't have the resources or the demand to warrant a second server.
> There's nothing that I can find in the RS documentation to create a second
> instance. I tried making a new virtual web in IIS and copying the files to
> the web's underlying file structure but that did not work.
> Any advice or guidance would be greatly appreciated.
purchasing a new server and a second copy of Reporting Services? I would
like to have second website with a copy of our live site for testing purposes
but we don't have the resources or the demand to warrant a second server.
There's nothing that I can find in the RS documentation to create a second
instance. I tried making a new virtual web in IIS and copying the files to
the web's underlying file structure but that did not work.
Any advice or guidance would be greatly appreciated.http://msdn2.microsoft.com/en-us/library/ms403426.aspx
"Stuart" <Stuart@.discussions.microsoft.com> wrote in message
news:4995111C-5CDE-439A-A1F0-9B75D44EBBF7@.microsoft.com...
> Has anyone come up with a way to deploy reports to a test environment
> without
> purchasing a new server and a second copy of Reporting Services? I would
> like to have second website with a copy of our live site for testing
> purposes
> but we don't have the resources or the demand to warrant a second server.
> There's nothing that I can find in the RS documentation to create a second
> instance. I tried making a new virtual web in IIS and copying the files
> to
> the web's underlying file structure but that did not work.
> Any advice or guidance would be greatly appreciated.|||Thanks!
"Immy" wrote:
> http://msdn2.microsoft.com/en-us/library/ms403426.aspx
> "Stuart" <Stuart@.discussions.microsoft.com> wrote in message
> news:4995111C-5CDE-439A-A1F0-9B75D44EBBF7@.microsoft.com...
> > Has anyone come up with a way to deploy reports to a test environment
> > without
> > purchasing a new server and a second copy of Reporting Services? I would
> > like to have second website with a copy of our live site for testing
> > purposes
> > but we don't have the resources or the demand to warrant a second server.
> > There's nothing that I can find in the RS documentation to create a second
> > instance. I tried making a new virtual web in IIS and copying the files
> > to
> > the web's underlying file structure but that did not work.
> >
> > Any advice or guidance would be greatly appreciated.
>
>|||or can you use a SQL Server Developers edition for testing; or is it
just for development'
Stuart wrote:
> Has anyone come up with a way to deploy reports to a test environment without
> purchasing a new server and a second copy of Reporting Services? I would
> like to have second website with a copy of our live site for testing purposes
> but we don't have the resources or the demand to warrant a second server.
> There's nothing that I can find in the RS documentation to create a second
> instance. I tried making a new virtual web in IIS and copying the files to
> the web's underlying file structure but that did not work.
> Any advice or guidance would be greatly appreciated.
Reporting Svcs vs Charting Controls
We are trying to decide between Reporting Svcs and Charting Controls. If we
go Reporting SVcs route, we'll have to use Web Service as we are passing
datasets as the datasource and there will be no URL access. It's a fairly
complex application using stock and candlestick charts. What are the pros and
cons of both? I feel charting controls provide a finer control over the look
and feel but I am open to other ideas/suggestions.
ThanksMy opinion is that the chart offerings of MSRS are pretty weak...at least
right now. You know MS is going to beef them up eventually but if you have
very specific charting requirements (like a zoom that doesn't just blow up a
jpg) you'll probably want to go with a control. The company that licensed
the charting component to Microsoft (www.dundas.com) has a more advance
charting component but I don't think it can be "plugged" into MSRS.
"vibs" <vibs@.discussions.microsoft.com> wrote in message
news:25D688C7-A8DB-40AF-B018-CF97739EB4C2@.microsoft.com...
> We are trying to decide between Reporting Svcs and Charting Controls. If
we
> go Reporting SVcs route, we'll have to use Web Service as we are passing
> datasets as the datasource and there will be no URL access. It's a fairly
> complex application using stock and candlestick charts. What are the pros
and
> cons of both? I feel charting controls provide a finer control over the
look
> and feel but I am open to other ideas/suggestions.
> Thanks
>
go Reporting SVcs route, we'll have to use Web Service as we are passing
datasets as the datasource and there will be no URL access. It's a fairly
complex application using stock and candlestick charts. What are the pros and
cons of both? I feel charting controls provide a finer control over the look
and feel but I am open to other ideas/suggestions.
ThanksMy opinion is that the chart offerings of MSRS are pretty weak...at least
right now. You know MS is going to beef them up eventually but if you have
very specific charting requirements (like a zoom that doesn't just blow up a
jpg) you'll probably want to go with a control. The company that licensed
the charting component to Microsoft (www.dundas.com) has a more advance
charting component but I don't think it can be "plugged" into MSRS.
"vibs" <vibs@.discussions.microsoft.com> wrote in message
news:25D688C7-A8DB-40AF-B018-CF97739EB4C2@.microsoft.com...
> We are trying to decide between Reporting Svcs and Charting Controls. If
we
> go Reporting SVcs route, we'll have to use Web Service as we are passing
> datasets as the datasource and there will be no URL access. It's a fairly
> complex application using stock and candlestick charts. What are the pros
and
> cons of both? I feel charting controls provide a finer control over the
look
> and feel but I am open to other ideas/suggestions.
> Thanks
>
Reporting Svcs not working after renaming the server - help!
Hi,
we had to rename our server running SQL server and reporting services
(including IIS), and now the reporting services don't work anymore.
I guess the easiest way would probably be uninstalling the reporting
services and then re-installing them again, but I wanted to ask if there
was another way...
Thanks!
JensWhat errors are you getting? Can you navigate to
http://localhost/reportserver? You may just need to run rsconfig.exe to
reset the connection string but I need to know the errors first.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jens Weiermann" <wexman@.wexman.com> wrote in message
news:u8DGsWtcEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Hi,
> we had to rename our server running SQL server and reporting services
> (including IIS), and now the reporting services don't work anymore.
> I guess the easiest way would probably be uninstalling the reporting
> services and then re-installing them again, but I wanted to ask if there
> was another way...
> Thanks!
> Jens|||Daniel Reib [MSFT] wrote:
> What errors are you getting? Can you navigate to
> http://localhost/reportserver? You may just need to run rsconfig.exe to
> reset the connection string but I need to know the errors first.
Hi Daniel,
thanks for your answer - but I'm afraid it is too late now <g> as we've
already uninstalled the reporting services and re-installed them again.
However, now I got a different problem: While reports are working in
general, subscriptions are *not*.
When I try to make a new abonnement, I'm receiving an internal error
"@.owner_login_name was specified and is invalid" (sorry, translation from
German version, might not be the exact wording).
Any suggestions?
Regards,
Jens|||There are two ways to fix this problem. Install the following SQL fix:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
Or use RSconfig to have RS talk to it's catalog using sql auth.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jens Weiermann" <spamgoeshere@.solidsoftware.de> wrote in message
news:OmlQkw8cEHA.4092@.TK2MSFTNGP10.phx.gbl...
> Daniel Reib [MSFT] wrote:
> > What errors are you getting? Can you navigate to
> > http://localhost/reportserver? You may just need to run rsconfig.exe to
> > reset the connection string but I need to know the errors first.
> Hi Daniel,
> thanks for your answer - but I'm afraid it is too late now <g> as we've
> already uninstalled the reporting services and re-installed them again.
> However, now I got a different problem: While reports are working in
> general, subscriptions are *not*.
> When I try to make a new abonnement, I'm receiving an internal error
> "@.owner_login_name was specified and is invalid" (sorry, translation from
> German version, might not be the exact wording).
> Any suggestions?
> Regards,
> Jens
we had to rename our server running SQL server and reporting services
(including IIS), and now the reporting services don't work anymore.
I guess the easiest way would probably be uninstalling the reporting
services and then re-installing them again, but I wanted to ask if there
was another way...
Thanks!
JensWhat errors are you getting? Can you navigate to
http://localhost/reportserver? You may just need to run rsconfig.exe to
reset the connection string but I need to know the errors first.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jens Weiermann" <wexman@.wexman.com> wrote in message
news:u8DGsWtcEHA.2352@.TK2MSFTNGP09.phx.gbl...
> Hi,
> we had to rename our server running SQL server and reporting services
> (including IIS), and now the reporting services don't work anymore.
> I guess the easiest way would probably be uninstalling the reporting
> services and then re-installing them again, but I wanted to ask if there
> was another way...
> Thanks!
> Jens|||Daniel Reib [MSFT] wrote:
> What errors are you getting? Can you navigate to
> http://localhost/reportserver? You may just need to run rsconfig.exe to
> reset the connection string but I need to know the errors first.
Hi Daniel,
thanks for your answer - but I'm afraid it is too late now <g> as we've
already uninstalled the reporting services and re-installed them again.
However, now I got a different problem: While reports are working in
general, subscriptions are *not*.
When I try to make a new abonnement, I'm receiving an internal error
"@.owner_login_name was specified and is invalid" (sorry, translation from
German version, might not be the exact wording).
Any suggestions?
Regards,
Jens|||There are two ways to fix this problem. Install the following SQL fix:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
Or use RSconfig to have RS talk to it's catalog using sql auth.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jens Weiermann" <spamgoeshere@.solidsoftware.de> wrote in message
news:OmlQkw8cEHA.4092@.TK2MSFTNGP10.phx.gbl...
> Daniel Reib [MSFT] wrote:
> > What errors are you getting? Can you navigate to
> > http://localhost/reportserver? You may just need to run rsconfig.exe to
> > reset the connection string but I need to know the errors first.
> Hi Daniel,
> thanks for your answer - but I'm afraid it is too late now <g> as we've
> already uninstalled the reporting services and re-installed them again.
> However, now I got a different problem: While reports are working in
> general, subscriptions are *not*.
> When I try to make a new abonnement, I'm receiving an internal error
> "@.owner_login_name was specified and is invalid" (sorry, translation from
> German version, might not be the exact wording).
> Any suggestions?
> Regards,
> Jens
Reporting SVCS Installed?
I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
switch from Crystal Reports 8.5 to MS Reporting Services. How can I upgrade
my SQL Server 2000 with this new reporting service/module? NOTE: I
purchased my SQL license in 2002.
There are no downloads in MSDN (except for an evaluation install), and no
options to upgrade to the latest version that includes the reprting service.
Also, where (on the Net) do I go to install the .Net components for
integration with the reporting service?There is a how to get RS info up on the RS website. Normally, it depends on
how you bought SQL Server. Most likely, you'll need to call your reseller
and get the RS CD from them.
Tom
"Billg_sd" <Billgsd@.discussions.microsoft.com> wrote in message
news:85432424-5394-42BE-BC39-3071F0C951EB@.microsoft.com...
>I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
> switch from Crystal Reports 8.5 to MS Reporting Services. How can I
> upgrade
> my SQL Server 2000 with this new reporting service/module? NOTE: I
> purchased my SQL license in 2002.
> There are no downloads in MSDN (except for an evaluation install), and no
> options to upgrade to the latest version that includes the reprting
> service.
> Also, where (on the Net) do I go to install the .Net components for
> integration with the reporting service?
>
switch from Crystal Reports 8.5 to MS Reporting Services. How can I upgrade
my SQL Server 2000 with this new reporting service/module? NOTE: I
purchased my SQL license in 2002.
There are no downloads in MSDN (except for an evaluation install), and no
options to upgrade to the latest version that includes the reprting service.
Also, where (on the Net) do I go to install the .Net components for
integration with the reporting service?There is a how to get RS info up on the RS website. Normally, it depends on
how you bought SQL Server. Most likely, you'll need to call your reseller
and get the RS CD from them.
Tom
"Billg_sd" <Billgsd@.discussions.microsoft.com> wrote in message
news:85432424-5394-42BE-BC39-3071F0C951EB@.microsoft.com...
>I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
> switch from Crystal Reports 8.5 to MS Reporting Services. How can I
> upgrade
> my SQL Server 2000 with this new reporting service/module? NOTE: I
> purchased my SQL license in 2002.
> There are no downloads in MSDN (except for an evaluation install), and no
> options to upgrade to the latest version that includes the reprting
> service.
> Also, where (on the Net) do I go to install the .Net components for
> integration with the reporting service?
>
Reporting Svcs Install problems : IIS
Hi,
I cannot install MSRS , I get this error , yellow !!!
"IIS is either not insalled or not configured for a server component
installation"
I have run aspnet_regiis, but still not use.
I have IIS running perfect with other apps, WSS, etc., on W2003Svr
Default web site http://localhost runs FP2002 extns
http://localhost/WSS runs WSS , works well
What else do i have to do to config IIS ?See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
Mike G.
"Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> Hi,
> I cannot install MSRS , I get this error , yellow !!!
> "IIS is either not insalled or not configured for a server component
> installation"
> I have run aspnet_regiis, but still not use.
> I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> Default web site http://localhost runs FP2002 extns
> http://localhost/WSS runs WSS , works well
> What else do i have to do to config IIS ?|||Thanks, I have already read this article, and followed all the steps.
but it still does not work, i still get the same error, looks like it cannot
see the Default Web on IIS.
WSS ,and all other web apps work perfect, even the Default web is working,
yet somehow, I cannot get RS to install?
regards
Paul
"Mike G." wrote:
> See:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
> Mike G.
>
> "Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
> news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> > Hi,
> >
> > I cannot install MSRS , I get this error , yellow !!!
> > "IIS is either not insalled or not configured for a server component
> > installation"
> >
> > I have run aspnet_regiis, but still not use.
> >
> > I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> >
> > Default web site http://localhost runs FP2002 extns
> > http://localhost/WSS runs WSS , works well
> >
> > What else do i have to do to config IIS ?
>
>|||Have you resolved this issue? I am having the same problem on WS 2003. But,
I do not have any Sharepoint products installed...
"Paul Matthews" wrote:
> Thanks, I have already read this article, and followed all the steps.
> but it still does not work, i still get the same error, looks like it cannot
> see the Default Web on IIS.
> WSS ,and all other web apps work perfect, even the Default web is working,
> yet somehow, I cannot get RS to install?
> regards
> Paul
>
> "Mike G." wrote:
> > See:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
> >
> > Mike G.
> >
> >
> > "Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
> > news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> > > Hi,
> > >
> > > I cannot install MSRS , I get this error , yellow !!!
> > > "IIS is either not insalled or not configured for a server component
> > > installation"
> > >
> > > I have run aspnet_regiis, but still not use.
> > >
> > > I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> > >
> > > Default web site http://localhost runs FP2002 extns
> > > http://localhost/WSS runs WSS , works well
> > >
> > > What else do i have to do to config IIS ?
> >
> >
> >
I cannot install MSRS , I get this error , yellow !!!
"IIS is either not insalled or not configured for a server component
installation"
I have run aspnet_regiis, but still not use.
I have IIS running perfect with other apps, WSS, etc., on W2003Svr
Default web site http://localhost runs FP2002 extns
http://localhost/WSS runs WSS , works well
What else do i have to do to config IIS ?See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
Mike G.
"Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> Hi,
> I cannot install MSRS , I get this error , yellow !!!
> "IIS is either not insalled or not configured for a server component
> installation"
> I have run aspnet_regiis, but still not use.
> I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> Default web site http://localhost runs FP2002 extns
> http://localhost/WSS runs WSS , works well
> What else do i have to do to config IIS ?|||Thanks, I have already read this article, and followed all the steps.
but it still does not work, i still get the same error, looks like it cannot
see the Default Web on IIS.
WSS ,and all other web apps work perfect, even the Default web is working,
yet somehow, I cannot get RS to install?
regards
Paul
"Mike G." wrote:
> See:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
> Mike G.
>
> "Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
> news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> > Hi,
> >
> > I cannot install MSRS , I get this error , yellow !!!
> > "IIS is either not insalled or not configured for a server component
> > installation"
> >
> > I have run aspnet_regiis, but still not use.
> >
> > I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> >
> > Default web site http://localhost runs FP2002 extns
> > http://localhost/WSS runs WSS , works well
> >
> > What else do i have to do to config IIS ?
>
>|||Have you resolved this issue? I am having the same problem on WS 2003. But,
I do not have any Sharepoint products installed...
"Paul Matthews" wrote:
> Thanks, I have already read this article, and followed all the steps.
> but it still does not work, i still get the same error, looks like it cannot
> see the Default Web on IIS.
> WSS ,and all other web apps work perfect, even the Default web is working,
> yet somehow, I cannot get RS to install?
> regards
> Paul
>
> "Mike G." wrote:
> > See:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp
> >
> > Mike G.
> >
> >
> > "Paul Matthews" <PaulMatthews@.discussions.microsoft.com> wrote in message
> > news:B10AF8C2-00DD-440F-ADBD-B15FC813C8DD@.microsoft.com...
> > > Hi,
> > >
> > > I cannot install MSRS , I get this error , yellow !!!
> > > "IIS is either not insalled or not configured for a server component
> > > installation"
> > >
> > > I have run aspnet_regiis, but still not use.
> > >
> > > I have IIS running perfect with other apps, WSS, etc., on W2003Svr
> > >
> > > Default web site http://localhost runs FP2002 extns
> > > http://localhost/WSS runs WSS , works well
> > >
> > > What else do i have to do to config IIS ?
> >
> >
> >
Reporting SVCS Error and Deadlock Victim Error
Hi Everyone,
I having a problem when generating the reports. Some time, the report generation are slow and there is frequent intermitten reporting svcs error such as process ID 86 or Deadlock victim error. But, some time the report generation are ok.
Please help !! Thank you.
Best Regard,
Terence Wong
I am speculating - but
Is there a "deadly embrace" on the table you are going after - cause you are timing out - and that indicates to me there is another process (ID 86) that is causing the "hang"..
Or in the SQL statement do you have a JOIN that is not correct -
Take your SQL statement your are using within the MS RS report and paste into query analyzer and
Within Query Analyzer <Query> <Display Estimated Execution Plan> this wil ltell you where the hang up is based upon percentages for every step within the SQL statement. As a general rule anything over 30% could potentially be a problem!
best regards,
I having a problem when generating the reports. Some time, the report generation are slow and there is frequent intermitten reporting svcs error such as process ID 86 or Deadlock victim error. But, some time the report generation are ok.
Please help !! Thank you.
Best Regard,
Terence Wong
I am speculating - but
Is there a "deadly embrace" on the table you are going after - cause you are timing out - and that indicates to me there is another process (ID 86) that is causing the "hang"..
Or in the SQL statement do you have a JOIN that is not correct -
Take your SQL statement your are using within the MS RS report and paste into query analyzer and
Within Query Analyzer <Query> <Display Estimated Execution Plan> this wil ltell you where the hang up is based upon percentages for every step within the SQL statement. As a general rule anything over 30% could potentially be a problem!
best regards,
Reporting SVCS and OLAP
Hello
I have question about OLAP and reporting services, is there any way, or any
add in component for Reporting SVCS, for dynamic olap table. First when i
read feature of Reporting services i read something about integration with
OWC so i was thougt that i can add OWC PivotTable like component on my
Report, but this is not or so....
Is also there any SDK how to buil own component for Reporting Services
thank
Matej
Home page: http://magic.streznik.org
---Hi,
MS Reporting Services is for SQL Reporting and MS Analysis Services is
for MDX Reporting. With the addin of Panorama for MS Reporting
Services it is possible to have a MDX Report in MS Reporting Services
with parameters to choice from a slicer. With a simple click you can
go from static reporting in MS Reporting Services to the webclient of
Panorama for more analysis.
With QuickQuery And ReportBuilder you can make your own SQL Reports in
MS Reporting Services and in future also based on MDX Reports.
You can also use ReportPortal to have all in one concept.
On our website www.gmsbv.nl you will find more info, demos and trials.
Regards,
Marco
www.gmsbv.nl
"Matej Kavèiè" <matej.kavcic@.email.si> wrote in message news:<ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl>...
> Hello
> I have question about OLAP and reporting services, is there any way, or any
> add in component for Reporting SVCS, for dynamic olap table. First when i
> read feature of Reporting services i read something about integration with
> OWC so i was thougt that i can add OWC PivotTable like component on my
> Report, but this is not or so....
> Is also there any SDK how to buil own component for Reporting Services
> thank
> Matej
> Home page: http://magic.streznik.org
> ---|||Ok, there are two independent questions here.
1. OWC:
You might want to checkout MSDN at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_43vn.asp
The dynamic pivot table functionality in Reporting Services is done via
Office Web Components (Office XP). Matrix reports (which you can build from
any type of data source) will be rendered as interactive pivot tables in
HTML with OWC.
2. Reporting from Analysis Services:
This question has come up several times on the newsgroup. You might want to
download and check out some samples from this link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f9b6e945-1f4c-4b7c-9c83-c6801f0576ff&DisplayLang=en
In addition, you may also want to subscribe to this discussion list:
http://groups.msn.com/OLAPServicesDevelopersForum. It should contain a
document in the discussion group under General about approaches how to
directly use Analysis Services 2000 as a datasource for Reporting Services
2000.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matej Kavèiè" <matej.kavcic@.email.si> wrote in message
news:ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Hello
> I have question about OLAP and reporting services, is there any way, or
any
> add in component for Reporting SVCS, for dynamic olap table. First when i
> read feature of Reporting services i read something about integration with
> OWC so i was thougt that i can add OWC PivotTable like component on my
> Report, but this is not or so....
> Is also there any SDK how to buil own component for Reporting Services
> thank
> Matej
> Home page: http://magic.streznik.org
> ---
>|||There is also a MSDN article available now: "Integrating Analysis Services
with Reporting Services"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/olapasandrs.asp
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:OxSEHJaVEHA.4092@.TK2MSFTNGP11.phx.gbl...
> Ok, there are two independent questions here.
> 1. OWC:
> You might want to checkout MSDN at
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_43vn.asp
> The dynamic pivot table functionality in Reporting Services is done via
> Office Web Components (Office XP). Matrix reports (which you can build
from
> any type of data source) will be rendered as interactive pivot tables in
> HTML with OWC.
> 2. Reporting from Analysis Services:
> This question has come up several times on the newsgroup. You might want
to
> download and check out some samples from this link:
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=f9b6e945-1f4c-4b7c-9c83-c6801f0576ff&DisplayLang=en
> In addition, you may also want to subscribe to this discussion list:
> http://groups.msn.com/OLAPServicesDevelopersForum. It should contain a
> document in the discussion group under General about approaches how to
> directly use Analysis Services 2000 as a datasource for Reporting Services
> 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Matej Kavèiè" <matej.kavcic@.email.si> wrote in message
> news:ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl...
> > Hello
> >
> > I have question about OLAP and reporting services, is there any way, or
> any
> > add in component for Reporting SVCS, for dynamic olap table. First when
i
> > read feature of Reporting services i read something about integration
with
> > OWC so i was thougt that i can add OWC PivotTable like component on my
> > Report, but this is not or so....
> > Is also there any SDK how to buil own component for Reporting Services
> >
> > thank
> >
> > Matej
> > Home page: http://magic.streznik.org
> > ---
> >
> >
>
I have question about OLAP and reporting services, is there any way, or any
add in component for Reporting SVCS, for dynamic olap table. First when i
read feature of Reporting services i read something about integration with
OWC so i was thougt that i can add OWC PivotTable like component on my
Report, but this is not or so....
Is also there any SDK how to buil own component for Reporting Services
thank
Matej
Home page: http://magic.streznik.org
---Hi,
MS Reporting Services is for SQL Reporting and MS Analysis Services is
for MDX Reporting. With the addin of Panorama for MS Reporting
Services it is possible to have a MDX Report in MS Reporting Services
with parameters to choice from a slicer. With a simple click you can
go from static reporting in MS Reporting Services to the webclient of
Panorama for more analysis.
With QuickQuery And ReportBuilder you can make your own SQL Reports in
MS Reporting Services and in future also based on MDX Reports.
You can also use ReportPortal to have all in one concept.
On our website www.gmsbv.nl you will find more info, demos and trials.
Regards,
Marco
www.gmsbv.nl
"Matej Kavèiè" <matej.kavcic@.email.si> wrote in message news:<ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl>...
> Hello
> I have question about OLAP and reporting services, is there any way, or any
> add in component for Reporting SVCS, for dynamic olap table. First when i
> read feature of Reporting services i read something about integration with
> OWC so i was thougt that i can add OWC PivotTable like component on my
> Report, but this is not or so....
> Is also there any SDK how to buil own component for Reporting Services
> thank
> Matej
> Home page: http://magic.streznik.org
> ---|||Ok, there are two independent questions here.
1. OWC:
You might want to checkout MSDN at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_43vn.asp
The dynamic pivot table functionality in Reporting Services is done via
Office Web Components (Office XP). Matrix reports (which you can build from
any type of data source) will be rendered as interactive pivot tables in
HTML with OWC.
2. Reporting from Analysis Services:
This question has come up several times on the newsgroup. You might want to
download and check out some samples from this link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f9b6e945-1f4c-4b7c-9c83-c6801f0576ff&DisplayLang=en
In addition, you may also want to subscribe to this discussion list:
http://groups.msn.com/OLAPServicesDevelopersForum. It should contain a
document in the discussion group under General about approaches how to
directly use Analysis Services 2000 as a datasource for Reporting Services
2000.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Matej Kavèiè" <matej.kavcic@.email.si> wrote in message
news:ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl...
> Hello
> I have question about OLAP and reporting services, is there any way, or
any
> add in component for Reporting SVCS, for dynamic olap table. First when i
> read feature of Reporting services i read something about integration with
> OWC so i was thougt that i can add OWC PivotTable like component on my
> Report, but this is not or so....
> Is also there any SDK how to buil own component for Reporting Services
> thank
> Matej
> Home page: http://magic.streznik.org
> ---
>|||There is also a MSDN article available now: "Integrating Analysis Services
with Reporting Services"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/olapasandrs.asp
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:OxSEHJaVEHA.4092@.TK2MSFTNGP11.phx.gbl...
> Ok, there are two independent questions here.
> 1. OWC:
> You might want to checkout MSDN at
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_43vn.asp
> The dynamic pivot table functionality in Reporting Services is done via
> Office Web Components (Office XP). Matrix reports (which you can build
from
> any type of data source) will be rendered as interactive pivot tables in
> HTML with OWC.
> 2. Reporting from Analysis Services:
> This question has come up several times on the newsgroup. You might want
to
> download and check out some samples from this link:
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=f9b6e945-1f4c-4b7c-9c83-c6801f0576ff&DisplayLang=en
> In addition, you may also want to subscribe to this discussion list:
> http://groups.msn.com/OLAPServicesDevelopersForum. It should contain a
> document in the discussion group under General about approaches how to
> directly use Analysis Services 2000 as a datasource for Reporting Services
> 2000.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Matej Kavèiè" <matej.kavcic@.email.si> wrote in message
> news:ebhlhMSVEHA.1292@.TK2MSFTNGP10.phx.gbl...
> > Hello
> >
> > I have question about OLAP and reporting services, is there any way, or
> any
> > add in component for Reporting SVCS, for dynamic olap table. First when
i
> > read feature of Reporting services i read something about integration
with
> > OWC so i was thougt that i can add OWC PivotTable like component on my
> > Report, but this is not or so....
> > Is also there any SDK how to buil own component for Reporting Services
> >
> > thank
> >
> > Matej
> > Home page: http://magic.streznik.org
> > ---
> >
> >
>
Reporting Svcs 2000 and Visual Studio 2005?
Hi,
I'm a newbie to Reporting Svcs.
My PC has VStudio 2003 and VStudio 2005.
I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
From VStudio 2005 there's no access to create projects of type Report.
The windows end-user application project that needs to display the reports
is in VStudio 2005, but from VStudio 2005 I don't see the option to create
reports with Rep Svcs 2000.
I need to be able to design reports in Rep Svcs 2000 and be able to access
them from this win application project that is in VStudio 2005. Is this
possible? How can I do that?
Thank you in advance,
RichardRS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0 framework
asp.net application. There are two ways to integrate a 2.0 app with (whether
winforms or webforms) you can use web services (which requires a good bit of
work on your part for winforms) or you can use URL integration. Just embed
an IE control on your winform and use URL integration. Pretty straight
forward as long as you are doing an intranet app.
VS 2005 comes with new winform and webform controls. These can be used in
either local mode (all rendering is local, no server is involved) or server
mode. Either way, the new controls only work with RS 2005 reports.
Note that you can (if you have a license) install RS 2005 to use SQL Server
2000 as its metadata/object store.
I highly recommend going to RS 2005. It has a lot of new, really useful
features (better performance, multi-select parameters, end user sorting,
etc).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> Hi,
> I'm a newbie to Reporting Svcs.
> My PC has VStudio 2003 and VStudio 2005.
> I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
> From VStudio 2005 there's no access to create projects of type Report.
> The windows end-user application project that needs to display the reports
> is in VStudio 2005, but from VStudio 2005 I don't see the option to create
> reports with Rep Svcs 2000.
> I need to be able to design reports in Rep Svcs 2000 and be able to access
> them from this win application project that is in VStudio 2005. Is this
> possible? How can I do that?
> Thank you in advance,
> Richard|||Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
2000, and have the WinForm application in .Net 2.0 invoke/render/display this
report? How would you suggest this could be done?
Thank you in advance,
Richard
===
"Bruce L-C [MVP]" wrote:
> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0 framework
> asp.net application. There are two ways to integrate a 2.0 app with (whether
> winforms or webforms) you can use web services (which requires a good bit of
> work on your part for winforms) or you can use URL integration. Just embed
> an IE control on your winform and use URL integration. Pretty straight
> forward as long as you are doing an intranet app.
> VS 2005 comes with new winform and webform controls. These can be used in
> either local mode (all rendering is local, no server is involved) or server
> mode. Either way, the new controls only work with RS 2005 reports.
> Note that you can (if you have a license) install RS 2005 to use SQL Server
> 2000 as its metadata/object store.
> I highly recommend going to RS 2005. It has a lot of new, really useful
> features (better performance, multi-select parameters, end user sorting,
> etc).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> > Hi,
> >
> > I'm a newbie to Reporting Svcs.
> > My PC has VStudio 2003 and VStudio 2005.
> > I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
> > From VStudio 2005 there's no access to create projects of type Report.
> >
> > The windows end-user application project that needs to display the reports
> > is in VStudio 2005, but from VStudio 2005 I don't see the option to create
> > reports with Rep Svcs 2000.
> >
> > I need to be able to design reports in Rep Svcs 2000 and be able to access
> > them from this win application project that is in VStudio 2005. Is this
> > possible? How can I do that?
> >
> > Thank you in advance,
> >
> > Richard
>
>|||Webservices: render to PDF or HTML and give it to something to display.
URL integration. Assemble a string passing in parameters via URL. Use the IE
control in a Winform and set its URL to the string.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:E95F77EE-9D60-4863-8D68-E6B2CEEA79C6@.microsoft.com...
> Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
> 2000, and have the WinForm application in .Net 2.0 invoke/render/display
> this
> report? How would you suggest this could be done?
> Thank you in advance,
> Richard
> ===> "Bruce L-C [MVP]" wrote:
>> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0
>> framework
>> asp.net application. There are two ways to integrate a 2.0 app with
>> (whether
>> winforms or webforms) you can use web services (which requires a good bit
>> of
>> work on your part for winforms) or you can use URL integration. Just
>> embed
>> an IE control on your winform and use URL integration. Pretty straight
>> forward as long as you are doing an intranet app.
>> VS 2005 comes with new winform and webform controls. These can be used in
>> either local mode (all rendering is local, no server is involved) or
>> server
>> mode. Either way, the new controls only work with RS 2005 reports.
>> Note that you can (if you have a license) install RS 2005 to use SQL
>> Server
>> 2000 as its metadata/object store.
>> I highly recommend going to RS 2005. It has a lot of new, really useful
>> features (better performance, multi-select parameters, end user sorting,
>> etc).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Richard" <Richard@.discussions.microsoft.com> wrote in message
>> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
>> > Hi,
>> >
>> > I'm a newbie to Reporting Svcs.
>> > My PC has VStudio 2003 and VStudio 2005.
>> > I installed Rep Svcs 2000 and created a report with it from VStudio
>> > 2003.
>> > From VStudio 2005 there's no access to create projects of type Report.
>> >
>> > The windows end-user application project that needs to display the
>> > reports
>> > is in VStudio 2005, but from VStudio 2005 I don't see the option to
>> > create
>> > reports with Rep Svcs 2000.
>> >
>> > I need to be able to design reports in Rep Svcs 2000 and be able to
>> > access
>> > them from this win application project that is in VStudio 2005. Is this
>> > possible? How can I do that?
>> >
>> > Thank you in advance,
>> >
>> > Richard
>>|||Thank you. The current implementation uses Crystal Reports Viewer on a
WinForm, so the use of an IE control on a WinForm will be the easiest to
implement.
Sincerely,
Richard
==="Bruce L-C [MVP]" wrote:
> Webservices: render to PDF or HTML and give it to something to display.
> URL integration. Assemble a string passing in parameters via URL. Use the IE
> control in a Winform and set its URL to the string.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:E95F77EE-9D60-4863-8D68-E6B2CEEA79C6@.microsoft.com...
> > Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
> > 2000, and have the WinForm application in .Net 2.0 invoke/render/display
> > this
> > report? How would you suggest this could be done?
> >
> > Thank you in advance,
> >
> > Richard
> > ===> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0
> >> framework
> >> asp.net application. There are two ways to integrate a 2.0 app with
> >> (whether
> >> winforms or webforms) you can use web services (which requires a good bit
> >> of
> >> work on your part for winforms) or you can use URL integration. Just
> >> embed
> >> an IE control on your winform and use URL integration. Pretty straight
> >> forward as long as you are doing an intranet app.
> >>
> >> VS 2005 comes with new winform and webform controls. These can be used in
> >> either local mode (all rendering is local, no server is involved) or
> >> server
> >> mode. Either way, the new controls only work with RS 2005 reports.
> >>
> >> Note that you can (if you have a license) install RS 2005 to use SQL
> >> Server
> >> 2000 as its metadata/object store.
> >>
> >> I highly recommend going to RS 2005. It has a lot of new, really useful
> >> features (better performance, multi-select parameters, end user sorting,
> >> etc).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> >> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> >> > Hi,
> >> >
> >> > I'm a newbie to Reporting Svcs.
> >> > My PC has VStudio 2003 and VStudio 2005.
> >> > I installed Rep Svcs 2000 and created a report with it from VStudio
> >> > 2003.
> >> > From VStudio 2005 there's no access to create projects of type Report.
> >> >
> >> > The windows end-user application project that needs to display the
> >> > reports
> >> > is in VStudio 2005, but from VStudio 2005 I don't see the option to
> >> > create
> >> > reports with Rep Svcs 2000.
> >> >
> >> > I need to be able to design reports in Rep Svcs 2000 and be able to
> >> > access
> >> > them from this win application project that is in VStudio 2005. Is this
> >> > possible? How can I do that?
> >> >
> >> > Thank you in advance,
> >> >
> >> > Richard
> >>
> >>
> >>
>
>
I'm a newbie to Reporting Svcs.
My PC has VStudio 2003 and VStudio 2005.
I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
From VStudio 2005 there's no access to create projects of type Report.
The windows end-user application project that needs to display the reports
is in VStudio 2005, but from VStudio 2005 I don't see the option to create
reports with Rep Svcs 2000.
I need to be able to design reports in Rep Svcs 2000 and be able to access
them from this win application project that is in VStudio 2005. Is this
possible? How can I do that?
Thank you in advance,
RichardRS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0 framework
asp.net application. There are two ways to integrate a 2.0 app with (whether
winforms or webforms) you can use web services (which requires a good bit of
work on your part for winforms) or you can use URL integration. Just embed
an IE control on your winform and use URL integration. Pretty straight
forward as long as you are doing an intranet app.
VS 2005 comes with new winform and webform controls. These can be used in
either local mode (all rendering is local, no server is involved) or server
mode. Either way, the new controls only work with RS 2005 reports.
Note that you can (if you have a license) install RS 2005 to use SQL Server
2000 as its metadata/object store.
I highly recommend going to RS 2005. It has a lot of new, really useful
features (better performance, multi-select parameters, end user sorting,
etc).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> Hi,
> I'm a newbie to Reporting Svcs.
> My PC has VStudio 2003 and VStudio 2005.
> I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
> From VStudio 2005 there's no access to create projects of type Report.
> The windows end-user application project that needs to display the reports
> is in VStudio 2005, but from VStudio 2005 I don't see the option to create
> reports with Rep Svcs 2000.
> I need to be able to design reports in Rep Svcs 2000 and be able to access
> them from this win application project that is in VStudio 2005. Is this
> possible? How can I do that?
> Thank you in advance,
> Richard|||Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
2000, and have the WinForm application in .Net 2.0 invoke/render/display this
report? How would you suggest this could be done?
Thank you in advance,
Richard
===
"Bruce L-C [MVP]" wrote:
> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0 framework
> asp.net application. There are two ways to integrate a 2.0 app with (whether
> winforms or webforms) you can use web services (which requires a good bit of
> work on your part for winforms) or you can use URL integration. Just embed
> an IE control on your winform and use URL integration. Pretty straight
> forward as long as you are doing an intranet app.
> VS 2005 comes with new winform and webform controls. These can be used in
> either local mode (all rendering is local, no server is involved) or server
> mode. Either way, the new controls only work with RS 2005 reports.
> Note that you can (if you have a license) install RS 2005 to use SQL Server
> 2000 as its metadata/object store.
> I highly recommend going to RS 2005. It has a lot of new, really useful
> features (better performance, multi-select parameters, end user sorting,
> etc).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> > Hi,
> >
> > I'm a newbie to Reporting Svcs.
> > My PC has VStudio 2003 and VStudio 2005.
> > I installed Rep Svcs 2000 and created a report with it from VStudio 2003.
> > From VStudio 2005 there's no access to create projects of type Report.
> >
> > The windows end-user application project that needs to display the reports
> > is in VStudio 2005, but from VStudio 2005 I don't see the option to create
> > reports with Rep Svcs 2000.
> >
> > I need to be able to design reports in Rep Svcs 2000 and be able to access
> > them from this win application project that is in VStudio 2005. Is this
> > possible? How can I do that?
> >
> > Thank you in advance,
> >
> > Richard
>
>|||Webservices: render to PDF or HTML and give it to something to display.
URL integration. Assemble a string passing in parameters via URL. Use the IE
control in a Winform and set its URL to the string.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:E95F77EE-9D60-4863-8D68-E6B2CEEA79C6@.microsoft.com...
> Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
> 2000, and have the WinForm application in .Net 2.0 invoke/render/display
> this
> report? How would you suggest this could be done?
> Thank you in advance,
> Richard
> ===> "Bruce L-C [MVP]" wrote:
>> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0
>> framework
>> asp.net application. There are two ways to integrate a 2.0 app with
>> (whether
>> winforms or webforms) you can use web services (which requires a good bit
>> of
>> work on your part for winforms) or you can use URL integration. Just
>> embed
>> an IE control on your winform and use URL integration. Pretty straight
>> forward as long as you are doing an intranet app.
>> VS 2005 comes with new winform and webform controls. These can be used in
>> either local mode (all rendering is local, no server is involved) or
>> server
>> mode. Either way, the new controls only work with RS 2005 reports.
>> Note that you can (if you have a license) install RS 2005 to use SQL
>> Server
>> 2000 as its metadata/object store.
>> I highly recommend going to RS 2005. It has a lot of new, really useful
>> features (better performance, multi-select parameters, end user sorting,
>> etc).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Richard" <Richard@.discussions.microsoft.com> wrote in message
>> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
>> > Hi,
>> >
>> > I'm a newbie to Reporting Svcs.
>> > My PC has VStudio 2003 and VStudio 2005.
>> > I installed Rep Svcs 2000 and created a report with it from VStudio
>> > 2003.
>> > From VStudio 2005 there's no access to create projects of type Report.
>> >
>> > The windows end-user application project that needs to display the
>> > reports
>> > is in VStudio 2005, but from VStudio 2005 I don't see the option to
>> > create
>> > reports with Rep Svcs 2000.
>> >
>> > I need to be able to design reports in Rep Svcs 2000 and be able to
>> > access
>> > them from this win application project that is in VStudio 2005. Is this
>> > possible? How can I do that?
>> >
>> > Thank you in advance,
>> >
>> > Richard
>>|||Thank you. The current implementation uses Crystal Reports Viewer on a
WinForm, so the use of an IE control on a WinForm will be the easiest to
implement.
Sincerely,
Richard
==="Bruce L-C [MVP]" wrote:
> Webservices: render to PDF or HTML and give it to something to display.
> URL integration. Assemble a string passing in parameters via URL. Use the IE
> control in a Winform and set its URL to the string.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:E95F77EE-9D60-4863-8D68-E6B2CEEA79C6@.microsoft.com...
> > Thank you, Bruce. Then is it possible to design the report using Rpt Scvs
> > 2000, and have the WinForm application in .Net 2.0 invoke/render/display
> > this
> > report? How would you suggest this could be done?
> >
> > Thank you in advance,
> >
> > Richard
> > ===> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> RS 2000 is a framework 1.1 asp.net application. RS 2005 is a 2.0
> >> framework
> >> asp.net application. There are two ways to integrate a 2.0 app with
> >> (whether
> >> winforms or webforms) you can use web services (which requires a good bit
> >> of
> >> work on your part for winforms) or you can use URL integration. Just
> >> embed
> >> an IE control on your winform and use URL integration. Pretty straight
> >> forward as long as you are doing an intranet app.
> >>
> >> VS 2005 comes with new winform and webform controls. These can be used in
> >> either local mode (all rendering is local, no server is involved) or
> >> server
> >> mode. Either way, the new controls only work with RS 2005 reports.
> >>
> >> Note that you can (if you have a license) install RS 2005 to use SQL
> >> Server
> >> 2000 as its metadata/object store.
> >>
> >> I highly recommend going to RS 2005. It has a lot of new, really useful
> >> features (better performance, multi-select parameters, end user sorting,
> >> etc).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> >> news:FC440BC3-BF2F-430E-A5CB-9929322F7EE7@.microsoft.com...
> >> > Hi,
> >> >
> >> > I'm a newbie to Reporting Svcs.
> >> > My PC has VStudio 2003 and VStudio 2005.
> >> > I installed Rep Svcs 2000 and created a report with it from VStudio
> >> > 2003.
> >> > From VStudio 2005 there's no access to create projects of type Report.
> >> >
> >> > The windows end-user application project that needs to display the
> >> > reports
> >> > is in VStudio 2005, but from VStudio 2005 I don't see the option to
> >> > create
> >> > reports with Rep Svcs 2000.
> >> >
> >> > I need to be able to design reports in Rep Svcs 2000 and be able to
> >> > access
> >> > them from this win application project that is in VStudio 2005. Is this
> >> > possible? How can I do that?
> >> >
> >> > Thank you in advance,
> >> >
> >> > Richard
> >>
> >>
> >>
>
>
Reporting Svcs - stored procedure
Hi. I have a need to create a number of different reports via Reporting
Services. All of which are based on stored procedures, none of which require
any parameters. Most if not all of the report is calculated. I am
struggling badly to get even the most basic of the fields in place w/the
correct expressions. The only one I actually got to accept the expression
was a Date field, this is the calculation:
=SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
It, too, fails to preview, indicating the value expression for the field
contains an error. Again, all of the other report items are calculated
fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using the
report designer/report wizard to 'do it for me' only returns Date and a
couple fields that are not even in my resultset. like one of my values in
the report is 'Total Trades'...one of the fields listed as available is
'ID__Total__'
Further, in VS I've got the report open and am on the data tab, i hit the
Run option, I receive this error: An error occurred while retrieving the
parameters in the query. Could not locate entry in sysdatabases for database
'EXEC databasename'. No entry found with that name. Make sure that the name
is entered correctly.'
Clearly I am doing something very wrong with the stored procedure
definition. Like I said, all of these reports are based on procedures, can
anybody give me some suggestion/direction on the right way to call the procs?
They run w/out parameters...EXEC databasename.dbo.proc that's it.
Please advise.
-- LynnPick the command type as stored procedure and then just enter the name of
the stored procedure. When you click on the ! you should get back the data
and the fields. If you do not get the field list populated then click on the
refresh fields button (to the right of the ..., it looks like the refresh
button for IE).
Note that RS only works with the first resultset returned. It cannot handle
mutliple resultsets.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> Hi. I have a need to create a number of different reports via Reporting
> Services. All of which are based on stored procedures, none of which
> require
> any parameters. Most if not all of the report is calculated. I am
> struggling badly to get even the most basic of the fields in place w/the
> correct expressions. The only one I actually got to accept the expression
> was a Date field, this is the calculation:
> =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> It, too, fails to preview, indicating the value expression for the field
> contains an error. Again, all of the other report items are calculated
> fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using
> the
> report designer/report wizard to 'do it for me' only returns Date and a
> couple fields that are not even in my resultset. like one of my values in
> the report is 'Total Trades'...one of the fields listed as available is
> 'ID__Total__'
> Further, in VS I've got the report open and am on the data tab, i hit the
> Run option, I receive this error: An error occurred while retrieving the
> parameters in the query. Could not locate entry in sysdatabases for
> database
> 'EXEC databasename'. No entry found with that name. Make sure that the
> name
> is entered correctly.'
> Clearly I am doing something very wrong with the stored procedure
> definition. Like I said, all of these reports are based on procedures,
> can
> anybody give me some suggestion/direction on the right way to call the
> procs?
> They run w/out parameters...EXEC databasename.dbo.proc that's it.
> Please advise.
>
> -- Lynn|||oh, bruce, that is great. I can't believe it was as simple as that. one
remaining problem, though. one of my reports is like this:
Date Total Trades Symbols Traded Total $
-- -- -- --
02/07/2006 333,333 333 33,333,333,333.33
#Stocks Volume Total $
-- -- --
333,333 33,333,333 3,333,333,333.33
EndPoint Liquidity #Trades Volume Total $
-- -- -- -- --
AAAA Add 114,729 21,797,575 583,102,631.33
AAAA Opening 1 27
3,412.53
AAAA Remove 30,836 8,330,843 444,521,928.10
AAAA Route 41 4,543
103,291.31
BBBB Add 26,997 9,940,201 178,600,674.78
BBBB Opening 8,089 1,448,143 44,276,419.41
BBBB Remove 3,406 1,719,403 40,267,318.25
CCCC Add 83,781 22,443,732 746,570,071.43
CCCC Remove 35,756 12,250,359 483,329,796.97
CCCC Route 1,088 244,697 6,655,913.26
DDDD Route 2 62,500 2,539,375.00
DDDD Add 2,354 1,262,589 19,136,233.44
DDDD Remove 258 195,019 6,227,451.69
I only receive the top line in the resultset:
Date Total Trades Symbols Traded Total $
-- -- -- --
02/07/2006 333,333 333 33,333,333,333.33
I assume this is what you mean when you say it will only handle the 1st
resultset. All of my reports have multiple 'chunks' in the body. Do you
have any idea how I can achieve this report via reporting svcs?
Unfortunately, this is very important. Please do advise.
--Lynn
"Bruce L-C [MVP]" wrote:
> Pick the command type as stored procedure and then just enter the name of
> the stored procedure. When you click on the ! you should get back the data
> and the fields. If you do not get the field list populated then click on the
> refresh fields button (to the right of the ..., it looks like the refresh
> button for IE).
> Note that RS only works with the first resultset returned. It cannot handle
> mutliple resultsets.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> > Hi. I have a need to create a number of different reports via Reporting
> > Services. All of which are based on stored procedures, none of which
> > require
> > any parameters. Most if not all of the report is calculated. I am
> > struggling badly to get even the most basic of the fields in place w/the
> > correct expressions. The only one I actually got to accept the expression
> > was a Date field, this is the calculation:
> >
> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >
> > It, too, fails to preview, indicating the value expression for the field
> > contains an error. Again, all of the other report items are calculated
> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using
> > the
> > report designer/report wizard to 'do it for me' only returns Date and a
> > couple fields that are not even in my resultset. like one of my values in
> > the report is 'Total Trades'...one of the fields listed as available is
> > 'ID__Total__'
> >
> > Further, in VS I've got the report open and am on the data tab, i hit the
> > Run option, I receive this error: An error occurred while retrieving the
> > parameters in the query. Could not locate entry in sysdatabases for
> > database
> > 'EXEC databasename'. No entry found with that name. Make sure that the
> > name
> > is entered correctly.'
> >
> > Clearly I am doing something very wrong with the stored procedure
> > definition. Like I said, all of these reports are based on procedures,
> > can
> > anybody give me some suggestion/direction on the right way to call the
> > procs?
> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
> > Please advise.
> >
> >
> > -- Lynn
>
>|||This is three resultsets. RS does not have the ability to handle that. There
is no work around from RS side. You could create another stored procedure
that calls this one and have it return just one of the resultsets.
RS can deal with multiple datasets quite well, but each stored procedure
call can only return one.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> oh, bruce, that is great. I can't believe it was as simple as that. one
> remaining problem, though. one of my reports is like this:
> Date Total Trades Symbols Traded Total $
> -- -- -- --
> 02/07/2006 333,333 333 33,333,333,333.33
> #Stocks Volume Total $
> -- -- --
> 333,333 33,333,333 3,333,333,333.33
> EndPoint Liquidity #Trades Volume Total $
> -- -- -- -- --
> AAAA Add 114,729 21,797,575
> 583,102,631.33
> AAAA Opening 1 27
> 3,412.53
> AAAA Remove 30,836 8,330,843
> 444,521,928.10
> AAAA Route 41 4,543
> 103,291.31
> BBBB Add 26,997 9,940,201
> 178,600,674.78
> BBBB Opening 8,089 1,448,143
> 44,276,419.41
> BBBB Remove 3,406 1,719,403
> 40,267,318.25
> CCCC Add 83,781 22,443,732
> 746,570,071.43
> CCCC Remove 35,756 12,250,359
> 483,329,796.97
> CCCC Route 1,088 244,697
> 6,655,913.26
> DDDD Route 2 62,500
> 2,539,375.00
> DDDD Add 2,354 1,262,589
> 19,136,233.44
> DDDD Remove 258 195,019
> 6,227,451.69
> I only receive the top line in the resultset:
> Date Total Trades Symbols Traded Total $
> -- -- -- --
> 02/07/2006 333,333 333 33,333,333,333.33
> I assume this is what you mean when you say it will only handle the 1st
> resultset. All of my reports have multiple 'chunks' in the body. Do you
> have any idea how I can achieve this report via reporting svcs?
> Unfortunately, this is very important. Please do advise.
> --Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Pick the command type as stored procedure and then just enter the name of
>> the stored procedure. When you click on the ! you should get back the
>> data
>> and the fields. If you do not get the field list populated then click on
>> the
>> refresh fields button (to the right of the ..., it looks like the refresh
>> button for IE).
>> Note that RS only works with the first resultset returned. It cannot
>> handle
>> mutliple resultsets.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> > Hi. I have a need to create a number of different reports via
>> > Reporting
>> > Services. All of which are based on stored procedures, none of which
>> > require
>> > any parameters. Most if not all of the report is calculated. I am
>> > struggling badly to get even the most basic of the fields in place
>> > w/the
>> > correct expressions. The only one I actually got to accept the
>> > expression
>> > was a Date field, this is the calculation:
>> >
>> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >
>> > It, too, fails to preview, indicating the value expression for the
>> > field
>> > contains an error. Again, all of the other report items are calculated
>> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
>> > Using
>> > the
>> > report designer/report wizard to 'do it for me' only returns Date and a
>> > couple fields that are not even in my resultset. like one of my values
>> > in
>> > the report is 'Total Trades'...one of the fields listed as available
>> > is
>> > 'ID__Total__'
>> >
>> > Further, in VS I've got the report open and am on the data tab, i hit
>> > the
>> > Run option, I receive this error: An error occurred while retrieving
>> > the
>> > parameters in the query. Could not locate entry in sysdatabases for
>> > database
>> > 'EXEC databasename'. No entry found with that name. Make sure that the
>> > name
>> > is entered correctly.'
>> >
>> > Clearly I am doing something very wrong with the stored procedure
>> > definition. Like I said, all of these reports are based on procedures,
>> > can
>> > anybody give me some suggestion/direction on the right way to call the
>> > procs?
>> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
>> > Please advise.
>> >
>> >
>> > -- Lynn
>>|||Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
the second, possibly third procedure?
-- Lynn
"Bruce L-C [MVP]" wrote:
> This is three resultsets. RS does not have the ability to handle that. There
> is no work around from RS side. You could create another stored procedure
> that calls this one and have it return just one of the resultsets.
> RS can deal with multiple datasets quite well, but each stored procedure
> call can only return one.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> > oh, bruce, that is great. I can't believe it was as simple as that. one
> > remaining problem, though. one of my reports is like this:
> >
> > Date Total Trades Symbols Traded Total $
> > -- -- -- --
> > 02/07/2006 333,333 333 33,333,333,333.33
> >
> > #Stocks Volume Total $
> > -- -- --
> > 333,333 33,333,333 3,333,333,333.33
> >
> > EndPoint Liquidity #Trades Volume Total $
> > -- -- -- -- --
> > AAAA Add 114,729 21,797,575
> > 583,102,631.33
> > AAAA Opening 1 27
> > 3,412.53
> > AAAA Remove 30,836 8,330,843
> > 444,521,928.10
> > AAAA Route 41 4,543
> > 103,291.31
> > BBBB Add 26,997 9,940,201
> > 178,600,674.78
> > BBBB Opening 8,089 1,448,143
> > 44,276,419.41
> > BBBB Remove 3,406 1,719,403
> > 40,267,318.25
> > CCCC Add 83,781 22,443,732
> > 746,570,071.43
> > CCCC Remove 35,756 12,250,359
> > 483,329,796.97
> > CCCC Route 1,088 244,697
> > 6,655,913.26
> > DDDD Route 2 62,500
> > 2,539,375.00
> > DDDD Add 2,354 1,262,589
> > 19,136,233.44
> > DDDD Remove 258 195,019
> > 6,227,451.69
> >
> > I only receive the top line in the resultset:
> >
> > Date Total Trades Symbols Traded Total $
> > -- -- -- --
> > 02/07/2006 333,333 333 33,333,333,333.33
> >
> > I assume this is what you mean when you say it will only handle the 1st
> > resultset. All of my reports have multiple 'chunks' in the body. Do you
> > have any idea how I can achieve this report via reporting svcs?
> > Unfortunately, this is very important. Please do advise.
> >
> > --Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Pick the command type as stored procedure and then just enter the name of
> >> the stored procedure. When you click on the ! you should get back the
> >> data
> >> and the fields. If you do not get the field list populated then click on
> >> the
> >> refresh fields button (to the right of the ..., it looks like the refresh
> >> button for IE).
> >>
> >> Note that RS only works with the first resultset returned. It cannot
> >> handle
> >> mutliple resultsets.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> > Hi. I have a need to create a number of different reports via
> >> > Reporting
> >> > Services. All of which are based on stored procedures, none of which
> >> > require
> >> > any parameters. Most if not all of the report is calculated. I am
> >> > struggling badly to get even the most basic of the fields in place
> >> > w/the
> >> > correct expressions. The only one I actually got to accept the
> >> > expression
> >> > was a Date field, this is the calculation:
> >> >
> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >
> >> > It, too, fails to preview, indicating the value expression for the
> >> > field
> >> > contains an error. Again, all of the other report items are calculated
> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> > Using
> >> > the
> >> > report designer/report wizard to 'do it for me' only returns Date and a
> >> > couple fields that are not even in my resultset. like one of my values
> >> > in
> >> > the report is 'Total Trades'...one of the fields listed as available
> >> > is
> >> > 'ID__Total__'
> >> >
> >> > Further, in VS I've got the report open and am on the data tab, i hit
> >> > the
> >> > Run option, I receive this error: An error occurred while retrieving
> >> > the
> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> > database
> >> > 'EXEC databasename'. No entry found with that name. Make sure that the
> >> > name
> >> > is entered correctly.'
> >> >
> >> > Clearly I am doing something very wrong with the stored procedure
> >> > definition. Like I said, all of these reports are based on procedures,
> >> > can
> >> > anybody give me some suggestion/direction on the right way to call the
> >> > procs?
> >> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
> >> > Please advise.
> >> >
> >> >
> >> > -- Lynn
> >>
> >>
> >>
>
>|||Configure your existing stored procedure to accept a parameter (you can make
it optional so that it doesn't break existing code).
Then call it three times in RS with a static value and create three
datasets.
For instance dataset1
yourproc 1
Dataset2
yourproc 2
etc.
Then in your stored procedure return the appropriate resultset based on the
parameter.
Downside is that your sp is being run three times.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> the second, possibly third procedure?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> This is three resultsets. RS does not have the ability to handle that.
>> There
>> is no work around from RS side. You could create another stored procedure
>> that calls this one and have it return just one of the resultsets.
>> RS can deal with multiple datasets quite well, but each stored procedure
>> call can only return one.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> > oh, bruce, that is great. I can't believe it was as simple as that.
>> > one
>> > remaining problem, though. one of my reports is like this:
>> >
>> > Date Total Trades Symbols Traded Total $
>> > -- -- -- --
>> > 02/07/2006 333,333 333 33,333,333,333.33
>> >
>> > #Stocks Volume Total $
>> > -- -- --
>> > 333,333 33,333,333 3,333,333,333.33
>> >
>> > EndPoint Liquidity #Trades Volume Total $
>> > -- -- -- -- --
>> > AAAA Add 114,729 21,797,575
>> > 583,102,631.33
>> > AAAA Opening 1 27
>> > 3,412.53
>> > AAAA Remove 30,836 8,330,843
>> > 444,521,928.10
>> > AAAA Route 41 4,543
>> > 103,291.31
>> > BBBB Add 26,997 9,940,201
>> > 178,600,674.78
>> > BBBB Opening 8,089 1,448,143
>> > 44,276,419.41
>> > BBBB Remove 3,406 1,719,403
>> > 40,267,318.25
>> > CCCC Add 83,781 22,443,732
>> > 746,570,071.43
>> > CCCC Remove 35,756 12,250,359
>> > 483,329,796.97
>> > CCCC Route 1,088 244,697
>> > 6,655,913.26
>> > DDDD Route 2 62,500
>> > 2,539,375.00
>> > DDDD Add 2,354 1,262,589
>> > 19,136,233.44
>> > DDDD Remove 258 195,019
>> > 6,227,451.69
>> >
>> > I only receive the top line in the resultset:
>> >
>> > Date Total Trades Symbols Traded Total $
>> > -- -- -- --
>> > 02/07/2006 333,333 333 33,333,333,333.33
>> >
>> > I assume this is what you mean when you say it will only handle the 1st
>> > resultset. All of my reports have multiple 'chunks' in the body. Do
>> > you
>> > have any idea how I can achieve this report via reporting svcs?
>> > Unfortunately, this is very important. Please do advise.
>> >
>> > --Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Pick the command type as stored procedure and then just enter the name
>> >> of
>> >> the stored procedure. When you click on the ! you should get back the
>> >> data
>> >> and the fields. If you do not get the field list populated then click
>> >> on
>> >> the
>> >> refresh fields button (to the right of the ..., it looks like the
>> >> refresh
>> >> button for IE).
>> >>
>> >> Note that RS only works with the first resultset returned. It cannot
>> >> handle
>> >> mutliple resultsets.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> > Hi. I have a need to create a number of different reports via
>> >> > Reporting
>> >> > Services. All of which are based on stored procedures, none of
>> >> > which
>> >> > require
>> >> > any parameters. Most if not all of the report is calculated. I am
>> >> > struggling badly to get even the most basic of the fields in place
>> >> > w/the
>> >> > correct expressions. The only one I actually got to accept the
>> >> > expression
>> >> > was a Date field, this is the calculation:
>> >> >
>> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >
>> >> > It, too, fails to preview, indicating the value expression for the
>> >> > field
>> >> > contains an error. Again, all of the other report items are
>> >> > calculated
>> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
>> >> > Using
>> >> > the
>> >> > report designer/report wizard to 'do it for me' only returns Date
>> >> > and a
>> >> > couple fields that are not even in my resultset. like one of my
>> >> > values
>> >> > in
>> >> > the report is 'Total Trades'...one of the fields listed as
>> >> > available
>> >> > is
>> >> > 'ID__Total__'
>> >> >
>> >> > Further, in VS I've got the report open and am on the data tab, i
>> >> > hit
>> >> > the
>> >> > Run option, I receive this error: An error occurred while
>> >> > retrieving
>> >> > the
>> >> > parameters in the query. Could not locate entry in sysdatabases for
>> >> > database
>> >> > 'EXEC databasename'. No entry found with that name. Make sure that
>> >> > the
>> >> > name
>> >> > is entered correctly.'
>> >> >
>> >> > Clearly I am doing something very wrong with the stored procedure
>> >> > definition. Like I said, all of these reports are based on
>> >> > procedures,
>> >> > can
>> >> > anybody give me some suggestion/direction on the right way to call
>> >> > the
>> >> > procs?
>> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
>> >> > it.
>> >> > Please advise.
>> >> >
>> >> >
>> >> > -- Lynn
>> >>
>> >>
>> >>
>>|||well, bruce, i'm still not sure i know what to do w/these parameters...how
will i get one parameter to do one resultset and get the other resultsets
w/parameters 2 and 3? but, i will see if i can walk through this.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Hi again, Bruce. Is there any way you can give me an example of how to
change my proc to accept the 3 parameters? I know how to pass parameters to
a procedure, I just don't understand how I can do it to make my procedure gen
three different resultsets.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Bruce, or somebody else, might you give me an example of how to give the proc
3 parameters, producing three resultsets in a way that RS will display them?
Or, am I giving it three parameters and calling it three times? If so, how
would i call the 3 procs in RS?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Yes, you are calling it three times. In RS you create three datasets. Go to
the dataset tab and there is a combo box with the name of the dataset, you
can click on that and there is a an option for a new.
In your stored procedure
if @.WHICHRESULTSET = 1
begin
--return the first resultset here
end
etc
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> Bruce, or somebody else, might you give me an example of how to give the
> proc
> 3 parameters, producing three resultsets in a way that RS will display
> them?
> Or, am I giving it three parameters and calling it three times? If so,
> how
> would i call the 3 procs in RS?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Configure your existing stored procedure to accept a parameter (you can
>> make
>> it optional so that it doesn't break existing code).
>> Then call it three times in RS with a static value and create three
>> datasets.
>> For instance dataset1
>> yourproc 1
>> Dataset2
>> yourproc 2
>> etc.
>> Then in your stored procedure return the appropriate resultset based on
>> the
>> parameter.
>> Downside is that your sp is being run three times.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
>> > on
>> > the second, possibly third procedure?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> This is three resultsets. RS does not have the ability to handle that.
>> >> There
>> >> is no work around from RS side. You could create another stored
>> >> procedure
>> >> that calls this one and have it return just one of the resultsets.
>> >>
>> >> RS can deal with multiple datasets quite well, but each stored
>> >> procedure
>> >> call can only return one.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> > oh, bruce, that is great. I can't believe it was as simple as that.
>> >> > one
>> >> > remaining problem, though. one of my reports is like this:
>> >> >
>> >> > Date Total Trades Symbols Traded Total $
>> >> > -- -- -- --
>> >> > 02/07/2006 333,333 333 33,333,333,333.33
>> >> >
>> >> > #Stocks Volume Total $
>> >> > -- -- --
>> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >
>> >> > EndPoint Liquidity #Trades Volume Total $
>> >> > -- -- -- -- --
>> >> > AAAA Add 114,729 21,797,575
>> >> > 583,102,631.33
>> >> > AAAA Opening 1 27
>> >> > 3,412.53
>> >> > AAAA Remove 30,836 8,330,843
>> >> > 444,521,928.10
>> >> > AAAA Route 41 4,543
>> >> > 103,291.31
>> >> > BBBB Add 26,997 9,940,201
>> >> > 178,600,674.78
>> >> > BBBB Opening 8,089 1,448,143
>> >> > 44,276,419.41
>> >> > BBBB Remove 3,406 1,719,403
>> >> > 40,267,318.25
>> >> > CCCC Add 83,781 22,443,732
>> >> > 746,570,071.43
>> >> > CCCC Remove 35,756 12,250,359
>> >> > 483,329,796.97
>> >> > CCCC Route 1,088 244,697
>> >> > 6,655,913.26
>> >> > DDDD Route 2 62,500
>> >> > 2,539,375.00
>> >> > DDDD Add 2,354 1,262,589
>> >> > 19,136,233.44
>> >> > DDDD Remove 258 195,019
>> >> > 6,227,451.69
>> >> >
>> >> > I only receive the top line in the resultset:
>> >> >
>> >> > Date Total Trades Symbols Traded Total $
>> >> > -- -- -- --
>> >> > 02/07/2006 333,333 333 33,333,333,333.33
>> >> >
>> >> > I assume this is what you mean when you say it will only handle the
>> >> > 1st
>> >> > resultset. All of my reports have multiple 'chunks' in the body.
>> >> > Do
>> >> > you
>> >> > have any idea how I can achieve this report via reporting svcs?
>> >> > Unfortunately, this is very important. Please do advise.
>> >> >
>> >> > --Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Pick the command type as stored procedure and then just enter the
>> >> >> name
>> >> >> of
>> >> >> the stored procedure. When you click on the ! you should get back
>> >> >> the
>> >> >> data
>> >> >> and the fields. If you do not get the field list populated then
>> >> >> click
>> >> >> on
>> >> >> the
>> >> >> refresh fields button (to the right of the ..., it looks like the
>> >> >> refresh
>> >> >> button for IE).
>> >> >>
>> >> >> Note that RS only works with the first resultset returned. It
>> >> >> cannot
>> >> >> handle
>> >> >> mutliple resultsets.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> > Hi. I have a need to create a number of different reports via
>> >> >> > Reporting
>> >> >> > Services. All of which are based on stored procedures, none of
>> >> >> > which
>> >> >> > require
>> >> >> > any parameters. Most if not all of the report is calculated. I
>> >> >> > am
>> >> >> > struggling badly to get even the most basic of the fields in
>> >> >> > place
>> >> >> > w/the
>> >> >> > correct expressions. The only one I actually got to accept the
>> >> >> > expression
>> >> >> > was a Date field, this is the calculation:
>> >> >> >
>> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >
>> >> >> > It, too, fails to preview, indicating the value expression for
>> >> >> > the
>> >> >> > field
>> >> >> > contains an error. Again, all of the other report items are
>> >> >> > calculated
>> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
>> >> >> > etc.
>> >> >> > Using
>> >> >> > the
>> >> >> > report designer/report wizard to 'do it for me' only returns Date
>> >> >> > and a
>> >> >> > couple fields that are not even in my resultset. like one of my
>> >> >> > values
>> >> >> > in
>> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> > available
>> >> >> > is
>> >> >> > 'ID__Total__'
>> >> >> >
>> >> >> > Further, in VS I've got the report open and am on the data tab, i
>> >> >> > hit
>> >> >> > the
>> >> >> > Run option, I receive this error: An error occurred while
>> >> >> > retrieving
>> >> >> > the
>> >> >> > parameters in the query. Could not locate entry in sysdatabases
>> >> >> > for
>> >> >> > database
>> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
>> >> >> > that
>> >> >> > the
>> >> >> > name
>> >> >> > is entered correctly.'
>> >> >> >
>> >> >> > Clearly I am doing something very wrong with the stored procedure
>> >> >> > definition. Like I said, all of these reports are based on
>> >> >> > procedures,
>> >> >> > can
>> >> >> > anybody give me some suggestion/direction on the right way to
>> >> >> > call
>> >> >> > the
>> >> >> > procs?
>> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
>> >> >> > it.
>> >> >> > Please advise.
>> >> >> >
>> >> >> >
>> >> >> > -- Lynn
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||bruce, i've added the parameters to the proc, now if you fire procname 1,
procname 2, procname 3 or procname 4, it returns each of the resultsets to me
in query analyzer.
in Rs i've got one dataset running this successfully:
EXEC db.dbo.procname 1
results are given, everthing looks good.
but, i go add dataset 2, it seems to do so successfully, but now the data is
not shown. not even the data from the first dataset. it just gives my
header, no results. i don't know how to fix this. should i be using
subreports, should i be using one proce multiple times w/multiple datasets,
i'm just not sure.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Yes, you are calling it three times. In RS you create three datasets. Go to
> the dataset tab and there is a combo box with the name of the dataset, you
> can click on that and there is a an option for a new.
> In your stored procedure
> if @.WHICHRESULTSET = 1
> begin
> --return the first resultset here
> end
> etc
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> > Bruce, or somebody else, might you give me an example of how to give the
> > proc
> > 3 parameters, producing three resultsets in a way that RS will display
> > them?
> > Or, am I giving it three parameters and calling it three times? If so,
> > how
> > would i call the 3 procs in RS?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Configure your existing stored procedure to accept a parameter (you can
> >> make
> >> it optional so that it doesn't break existing code).
> >>
> >> Then call it three times in RS with a static value and create three
> >> datasets.
> >> For instance dataset1
> >> yourproc 1
> >>
> >> Dataset2
> >> yourproc 2
> >>
> >> etc.
> >>
> >> Then in your stored procedure return the appropriate resultset based on
> >> the
> >> parameter.
> >>
> >> Downside is that your sp is being run three times.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
> >> > on
> >> > the second, possibly third procedure?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> This is three resultsets. RS does not have the ability to handle that.
> >> >> There
> >> >> is no work around from RS side. You could create another stored
> >> >> procedure
> >> >> that calls this one and have it return just one of the resultsets.
> >> >>
> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> procedure
> >> >> call can only return one.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> >> > one
> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > #Stocks Volume Total $
> >> >> > -- -- --
> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >
> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> > -- -- -- -- --
> >> >> > AAAA Add 114,729 21,797,575
> >> >> > 583,102,631.33
> >> >> > AAAA Opening 1 27
> >> >> > 3,412.53
> >> >> > AAAA Remove 30,836 8,330,843
> >> >> > 444,521,928.10
> >> >> > AAAA Route 41 4,543
> >> >> > 103,291.31
> >> >> > BBBB Add 26,997 9,940,201
> >> >> > 178,600,674.78
> >> >> > BBBB Opening 8,089 1,448,143
> >> >> > 44,276,419.41
> >> >> > BBBB Remove 3,406 1,719,403
> >> >> > 40,267,318.25
> >> >> > CCCC Add 83,781 22,443,732
> >> >> > 746,570,071.43
> >> >> > CCCC Remove 35,756 12,250,359
> >> >> > 483,329,796.97
> >> >> > CCCC Route 1,088 244,697
> >> >> > 6,655,913.26
> >> >> > DDDD Route 2 62,500
> >> >> > 2,539,375.00
> >> >> > DDDD Add 2,354 1,262,589
> >> >> > 19,136,233.44
> >> >> > DDDD Remove 258 195,019
> >> >> > 6,227,451.69
> >> >> >
> >> >> > I only receive the top line in the resultset:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > I assume this is what you mean when you say it will only handle the
> >> >> > 1st
> >> >> > resultset. All of my reports have multiple 'chunks' in the body.
> >> >> > Do
> >> >> > you
> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >
> >> >> > --Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Pick the command type as stored procedure and then just enter the
> >> >> >> name
> >> >> >> of
> >> >> >> the stored procedure. When you click on the ! you should get back
> >> >> >> the
> >> >> >> data
> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> click
> >> >> >> on
> >> >> >> the
> >> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> >> refresh
> >> >> >> button for IE).
> >> >> >>
> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> cannot
> >> >> >> handle
> >> >> >> mutliple resultsets.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> > Reporting
> >> >> >> > Services. All of which are based on stored procedures, none of
> >> >> >> > which
> >> >> >> > require
> >> >> >> > any parameters. Most if not all of the report is calculated. I
> >> >> >> > am
> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> > place
> >> >> >> > w/the
> >> >> >> > correct expressions. The only one I actually got to accept the
> >> >> >> > expression
> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >
> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >
> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> > the
> >> >> >> > field
> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> > calculated
> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> > etc.
> >> >> >> > Using
> >> >> >> > the
> >> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> >> > and a
> >> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> >> > values
> >> >> >> > in
> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> > available
> >> >> >> > is
> >> >> >> > 'ID__Total__'
> >> >> >> >
> >> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> >> > hit
> >> >> >> > the
> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> > retrieving
> >> >> >> > the
> >> >> >> > parameters in the query. Could not locate entry in sysdatabases
> >> >> >> > for
> >> >> >> > database
> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> > that
> >> >> >> > the
> >> >> >> > name
> >> >> >> > is entered correctly.'
> >> >> >> >
> >> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> > procedures,
> >> >> >> > can
> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> > call
> >> >> >> > the
> >> >> >> > procs?
> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> >> > it.
> >> >> >> > Please advise.
> >> >> >> >
> >> >> >> >
> >> >> >> > -- Lynn
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||And, if I blow away the 2nd dataset and just give my 1st one parameters, it
almost works. EXEC db.dbo.procname 1 for chunk one of the results, works
just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
tab it returns an error: SQL Syntax Errors Encountered...The designer does
not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
results are still returned to me. On 'Preview' tab, however, I get no
data/results at all.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Yes, you are calling it three times. In RS you create three datasets. Go to
> the dataset tab and there is a combo box with the name of the dataset, you
> can click on that and there is a an option for a new.
> In your stored procedure
> if @.WHICHRESULTSET = 1
> begin
> --return the first resultset here
> end
> etc
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> > Bruce, or somebody else, might you give me an example of how to give the
> > proc
> > 3 parameters, producing three resultsets in a way that RS will display
> > them?
> > Or, am I giving it three parameters and calling it three times? If so,
> > how
> > would i call the 3 procs in RS?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Configure your existing stored procedure to accept a parameter (you can
> >> make
> >> it optional so that it doesn't break existing code).
> >>
> >> Then call it three times in RS with a static value and create three
> >> datasets.
> >> For instance dataset1
> >> yourproc 1
> >>
> >> Dataset2
> >> yourproc 2
> >>
> >> etc.
> >>
> >> Then in your stored procedure return the appropriate resultset based on
> >> the
> >> parameter.
> >>
> >> Downside is that your sp is being run three times.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
> >> > on
> >> > the second, possibly third procedure?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> This is three resultsets. RS does not have the ability to handle that.
> >> >> There
> >> >> is no work around from RS side. You could create another stored
> >> >> procedure
> >> >> that calls this one and have it return just one of the resultsets.
> >> >>
> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> procedure
> >> >> call can only return one.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> >> > one
> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > #Stocks Volume Total $
> >> >> > -- -- --
> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >
> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> > -- -- -- -- --
> >> >> > AAAA Add 114,729 21,797,575
> >> >> > 583,102,631.33
> >> >> > AAAA Opening 1 27
> >> >> > 3,412.53
> >> >> > AAAA Remove 30,836 8,330,843
> >> >> > 444,521,928.10
> >> >> > AAAA Route 41 4,543
> >> >> > 103,291.31
> >> >> > BBBB Add 26,997 9,940,201
> >> >> > 178,600,674.78
> >> >> > BBBB Opening 8,089 1,448,143
> >> >> > 44,276,419.41
> >> >> > BBBB Remove 3,406 1,719,403
> >> >> > 40,267,318.25
> >> >> > CCCC Add 83,781 22,443,732
> >> >> > 746,570,071.43
> >> >> > CCCC Remove 35,756 12,250,359
> >> >> > 483,329,796.97
> >> >> > CCCC Route 1,088 244,697
> >> >> > 6,655,913.26
> >> >> > DDDD Route 2 62,500
> >> >> > 2,539,375.00
> >> >> > DDDD Add 2,354 1,262,589
> >> >> > 19,136,233.44
> >> >> > DDDD Remove 258 195,019
> >> >> > 6,227,451.69
> >> >> >
> >> >> > I only receive the top line in the resultset:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > I assume this is what you mean when you say it will only handle the
> >> >> > 1st
> >> >> > resultset. All of my reports have multiple 'chunks' in the body.
> >> >> > Do
> >> >> > you
> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >
> >> >> > --Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Pick the command type as stored procedure and then just enter the
> >> >> >> name
> >> >> >> of
> >> >> >> the stored procedure. When you click on the ! you should get back
> >> >> >> the
> >> >> >> data
> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> click
> >> >> >> on
> >> >> >> the
> >> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> >> refresh
> >> >> >> button for IE).
> >> >> >>
> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> cannot
> >> >> >> handle
> >> >> >> mutliple resultsets.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> > Reporting
> >> >> >> > Services. All of which are based on stored procedures, none of
> >> >> >> > which
> >> >> >> > require
> >> >> >> > any parameters. Most if not all of the report is calculated. I
> >> >> >> > am
> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> > place
> >> >> >> > w/the
> >> >> >> > correct expressions. The only one I actually got to accept the
> >> >> >> > expression
> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >
> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >
> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> > the
> >> >> >> > field
> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> > calculated
> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> > etc.
> >> >> >> > Using
> >> >> >> > the
> >> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> >> > and a
> >> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> >> > values
> >> >> >> > in
> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> > available
> >> >> >> > is
> >> >> >> > 'ID__Total__'
> >> >> >> >
> >> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> >> > hit
> >> >> >> > the
> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> > retrieving
> >> >> >> > the
> >> >> >> > parameters in the query. Could not locate entry in sysdatabases
> >> >> >> > for
> >> >> >> > database
> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> > that
> >> >> >> > the
> >> >> >> > name
> >> >> >> > is entered correctly.'
> >> >> >> >
> >> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> > procedures,
> >> >> >> > can
> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> > call
> >> >> >> > the
> >> >> >> > procs?
> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> >> > it.
> >> >> >> > Please advise.
> >> >> >> >
> >> >> >> >
> >> >> >> > -- Lynn
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||If you are going against SQL Server do not run your stored procedure this
way. Pick command type of stored procedure. RS will detect the parameters.
If going against ODBC or OLEDB driver (which uses ? format for parameters)
then pick text as the command type and do this:
myproc ?
Create multiple datasets and for each one you should call the stored
procedure for each one.
Bruce Loehle-Conger
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> And, if I blow away the 2nd dataset and just give my 1st one parameters,
> it
> almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> works
> just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
> tab it returns an error: SQL Syntax Errors Encountered...The designer
> does
> not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
> results are still returned to me. On 'Preview' tab, however, I get no
> data/results at all.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Yes, you are calling it three times. In RS you create three datasets. Go
>> to
>> the dataset tab and there is a combo box with the name of the dataset,
>> you
>> can click on that and there is a an option for a new.
>> In your stored procedure
>> if @.WHICHRESULTSET = 1
>> begin
>> --return the first resultset here
>> end
>> etc
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> > Bruce, or somebody else, might you give me an example of how to give
>> > the
>> > proc
>> > 3 parameters, producing three resultsets in a way that RS will display
>> > them?
>> > Or, am I giving it three parameters and calling it three times? If so,
>> > how
>> > would i call the 3 procs in RS?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Configure your existing stored procedure to accept a parameter (you
>> >> can
>> >> make
>> >> it optional so that it doesn't break existing code).
>> >>
>> >> Then call it three times in RS with a static value and create three
>> >> datasets.
>> >> For instance dataset1
>> >> yourproc 1
>> >>
>> >> Dataset2
>> >> yourproc 2
>> >>
>> >> etc.
>> >>
>> >> Then in your stored procedure return the appropriate resultset based
>> >> on
>> >> the
>> >> parameter.
>> >>
>> >> Downside is that your sp is being run three times.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
>> >> > please,
>> >> > on
>> >> > the second, possibly third procedure?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> This is three resultsets. RS does not have the ability to handle
>> >> >> that.
>> >> >> There
>> >> >> is no work around from RS side. You could create another stored
>> >> >> procedure
>> >> >> that calls this one and have it return just one of the resultsets.
>> >> >>
>> >> >> RS can deal with multiple datasets quite well, but each stored
>> >> >> procedure
>> >> >> call can only return one.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> > oh, bruce, that is great. I can't believe it was as simple as
>> >> >> > that.
>> >> >> > one
>> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >
>> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> > -- -- -- --
>> >> >> > 02/07/2006 333,333 333
>> >> >> > 33,333,333,333.33
>> >> >> >
>> >> >> > #Stocks Volume Total $
>> >> >> > -- -- --
>> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >
>> >> >> > EndPoint Liquidity #Trades Volume Total $
>> >> >> > -- -- -- -- --
>> >> >> > AAAA Add 114,729 21,797,575
>> >> >> > 583,102,631.33
>> >> >> > AAAA Opening 1 27
>> >> >> > 3,412.53
>> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> > 444,521,928.10
>> >> >> > AAAA Route 41 4,543
>> >> >> > 103,291.31
>> >> >> > BBBB Add 26,997 9,940,201
>> >> >> > 178,600,674.78
>> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> > 44,276,419.41
>> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> > 40,267,318.25
>> >> >> > CCCC Add 83,781 22,443,732
>> >> >> > 746,570,071.43
>> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> > 483,329,796.97
>> >> >> > CCCC Route 1,088 244,697
>> >> >> > 6,655,913.26
>> >> >> > DDDD Route 2 62,500
>> >> >> > 2,539,375.00
>> >> >> > DDDD Add 2,354 1,262,589
>> >> >> > 19,136,233.44
>> >> >> > DDDD Remove 258 195,019
>> >> >> > 6,227,451.69
>> >> >> >
>> >> >> > I only receive the top line in the resultset:
>> >> >> >
>> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> > -- -- -- --
>> >> >> > 02/07/2006 333,333 333
>> >> >> > 33,333,333,333.33
>> >> >> >
>> >> >> > I assume this is what you mean when you say it will only handle
>> >> >> > the
>> >> >> > 1st
>> >> >> > resultset. All of my reports have multiple 'chunks' in the
>> >> >> > body.
>> >> >> > Do
>> >> >> > you
>> >> >> > have any idea how I can achieve this report via reporting svcs?
>> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >
>> >> >> > --Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Pick the command type as stored procedure and then just enter
>> >> >> >> the
>> >> >> >> name
>> >> >> >> of
>> >> >> >> the stored procedure. When you click on the ! you should get
>> >> >> >> back
>> >> >> >> the
>> >> >> >> data
>> >> >> >> and the fields. If you do not get the field list populated then
>> >> >> >> click
>> >> >> >> on
>> >> >> >> the
>> >> >> >> refresh fields button (to the right of the ..., it looks like
>> >> >> >> the
>> >> >> >> refresh
>> >> >> >> button for IE).
>> >> >> >>
>> >> >> >> Note that RS only works with the first resultset returned. It
>> >> >> >> cannot
>> >> >> >> handle
>> >> >> >> mutliple resultsets.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> > Hi. I have a need to create a number of different reports via
>> >> >> >> > Reporting
>> >> >> >> > Services. All of which are based on stored procedures, none
>> >> >> >> > of
>> >> >> >> > which
>> >> >> >> > require
>> >> >> >> > any parameters. Most if not all of the report is calculated.
>> >> >> >> > I
>> >> >> >> > am
>> >> >> >> > struggling badly to get even the most basic of the fields in
>> >> >> >> > place
>> >> >> >> > w/the
>> >> >> >> > correct expressions. The only one I actually got to accept
>> >> >> >> > the
>> >> >> >> > expression
>> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >
>> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >
>> >> >> >> > It, too, fails to preview, indicating the value expression for
>> >> >> >> > the
>> >> >> >> > field
>> >> >> >> > contains an error. Again, all of the other report items are
>> >> >> >> > calculated
>> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
>> >> >> >> > etc.
>> >> >> >> > Using
>> >> >> >> > the
>> >> >> >> > report designer/report wizard to 'do it for me' only returns
>> >> >> >> > Date
>> >> >> >> > and a
>> >> >> >> > couple fields that are not even in my resultset. like one of
>> >> >> >> > my
>> >> >> >> > values
>> >> >> >> > in
>> >> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> >> > available
>> >> >> >> > is
>> >> >> >> > 'ID__Total__'
>> >> >> >> >
>> >> >> >> > Further, in VS I've got the report open and am on the data
>> >> >> >> > tab, i
>> >> >> >> > hit
>> >> >> >> > the
>> >> >> >> > Run option, I receive this error: An error occurred while
>> >> >> >> > retrieving
>> >> >> >> > the
>> >> >> >> > parameters in the query. Could not locate entry in
>> >> >> >> > sysdatabases
>> >> >> >> > for
>> >> >> >> > database
>> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
>> >> >> >> > that
>> >> >> >> > the
>> >> >> >> > name
>> >> >> >> > is entered correctly.'
>> >> >> >> >
>> >> >> >> > Clearly I am doing something very wrong with the stored
>> >> >> >> > procedure
>> >> >> >> > definition. Like I said, all of these reports are based on
>> >> >> >> > procedures,
>> >> >> >> > can
>> >> >> >> > anybody give me some suggestion/direction on the right way to
>> >> >> >> > call
>> >> >> >> > the
>> >> >> >> > procs?
>> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
>> >> >> >> > that's
>> >> >> >> > it.
>> >> >> >> > Please advise.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > -- Lynn
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||i'm sorry, bruce, but where do i define the parameters? rs is not detecting
them. in my 1st dataset i've got cmd type stored procedure and the proc name
is in the query string. i assumed i would put the 1st parameter in on the
parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so i
gave it @.ch and the value of 1, but when i attempted to run it, it threw me a
'define query parameters box asking me to put the '1' in it.
-- Lynn
"Bruce L-C [MVP]" wrote:
> If you are going against SQL Server do not run your stored procedure this
> way. Pick command type of stored procedure. RS will detect the parameters.
> If going against ODBC or OLEDB driver (which uses ? format for parameters)
> then pick text as the command type and do this:
> myproc ?
> Create multiple datasets and for each one you should call the stored
> procedure for each one.
> Bruce Loehle-Conger
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> > And, if I blow away the 2nd dataset and just give my 1st one parameters,
> > it
> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> > works
> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> > does
> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
> > results are still returned to me. On 'Preview' tab, however, I get no
> > data/results at all.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Yes, you are calling it three times. In RS you create three datasets. Go
> >> to
> >> the dataset tab and there is a combo box with the name of the dataset,
> >> you
> >> can click on that and there is a an option for a new.
> >>
> >> In your stored procedure
> >>
> >> if @.WHICHRESULTSET = 1
> >> begin
> >> --return the first resultset here
> >> end
> >> etc
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> > Bruce, or somebody else, might you give me an example of how to give
> >> > the
> >> > proc
> >> > 3 parameters, producing three resultsets in a way that RS will display
> >> > them?
> >> > Or, am I giving it three parameters and calling it three times? If so,
> >> > how
> >> > would i call the 3 procs in RS?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> can
> >> >> make
> >> >> it optional so that it doesn't break existing code).
> >> >>
> >> >> Then call it three times in RS with a static value and create three
> >> >> datasets.
> >> >> For instance dataset1
> >> >> yourproc 1
> >> >>
> >> >> Dataset2
> >> >> yourproc 2
> >> >>
> >> >> etc.
> >> >>
> >> >> Then in your stored procedure return the appropriate resultset based
> >> >> on
> >> >> the
> >> >> parameter.
> >> >>
> >> >> Downside is that your sp is being run three times.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> > please,
> >> >> > on
> >> >> > the second, possibly third procedure?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> that.
> >> >> >> There
> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> procedure
> >> >> >> that calls this one and have it return just one of the resultsets.
> >> >> >>
> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> procedure
> >> >> >> call can only return one.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> > that.
> >> >> >> > one
> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >
> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> > -- -- -- --
> >> >> >> > 02/07/2006 333,333 333
> >> >> >> > 33,333,333,333.33
> >> >> >> >
> >> >> >> > #Stocks Volume Total $
> >> >> >> > -- -- --
> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >
> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> > -- -- -- -- --
> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> > 583,102,631.33
> >> >> >> > AAAA Opening 1 27
> >> >> >> > 3,412.53
> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> > 444,521,928.10
> >> >> >> > AAAA Route 41 4,543
> >> >> >> > 103,291.31
> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> > 178,600,674.78
> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> > 44,276,419.41
> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> > 40,267,318.25
> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> > 746,570,071.43
> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> > 483,329,796.97
> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> > 6,655,913.26
> >> >> >> > DDDD Route 2 62,500
> >> >> >> > 2,539,375.00
> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> > 19,136,233.44
> >> >> >> > DDDD Remove 258 195,019
> >> >> >> > 6,227,451.69
> >> >> >> >
> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >
> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> > -- -- -- --
> >> >> >> > 02/07/2006 333,333 333
> >> >> >> > 33,333,333,333.33
> >> >> >> >
> >> >> >> > I assume this is what you mean when you say it will only handle
> >> >> >> > the
> >> >> >> > 1st
> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> > body.
> >> >> >> > Do
> >> >> >> > you
> >> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >
> >> >> >> > --Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> the
> >> >> >> >> name
> >> >> >> >> of
> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> back
> >> >> >> >> the
> >> >> >> >> data
> >> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> >> click
> >> >> >> >> on
> >> >> >> >> the
> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> the
> >> >> >> >> refresh
> >> >> >> >> button for IE).
> >> >> >> >>
> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> cannot
> >> >> >> >> handle
> >> >> >> >> mutliple resultsets.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> >> > Reporting
> >> >> >> >> > Services. All of which are based on stored procedures, none
> >> >> >> >> > of
> >> >> >> >> > which
> >> >> >> >> > require
> >> >> >> >> > any parameters. Most if not all of the report is calculated.
> >> >> >> >> > I
> >> >> >> >> > am
> >> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> >> > place
> >> >> >> >> > w/the
> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> > the
> >> >> >> >> > expression
> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >
> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >
> >> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> >> > the
> >> >> >> >> > field
> >> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> >> > calculated
> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> >> > etc.
> >> >> >> >> > Using
> >> >> >> >> > the
> >> >> >> >> > report designer/report wizard to 'do it for me' only returns
> >> >> >> >> > Date
> >> >> >> >> > and a
> >> >> >> >> > couple fields that are not even in my resultset. like one of
> >> >> >> >> > my
> >> >> >> >> > values
> >> >> >> >> > in
> >> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> >> > available
> >> >> >> >> > is
> >> >> >> >> > 'ID__Total__'
> >> >> >> >> >
> >> >> >> >> > Further, in VS I've got the report open and am on the data
> >> >> >> >> > tab, i
> >> >> >> >> > hit
> >> >> >> >> > the
> >> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> >> > retrieving
> >> >> >> >> > the
> >> >> >> >> > parameters in the query. Could not locate entry in
> >> >> >> >> > sysdatabases
> >> >> >> >> > for
> >> >> >> >> > database
> >> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> >> > that
> >> >> >> >> > the
> >> >> >> >> > name
> >> >> >> >> > is entered correctly.'
> >> >> >> >> >
> >> >> >> >> > Clearly I am doing something very wrong with the stored
> >> >> >> >> > procedure
> >> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> >> > procedures,
> >> >> >> >> > can
> >> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> >> > call
> >> >> >> >> > the
> >> >> >> >> > procs?
> >> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
> >> >> >> >> > that's
> >> >> >> >> > it.
> >> >> >> >> > Please advise.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > -- Lynn
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Are you going against SQL Server?
If so, then just select tored procedure for the command type and just put in
the name of the stored procedure. Do not put exec in from of it or anything
else. It should detect the parameter and prompt you for it. It should also
create a report parameter as well for you.
Try creating a new dataset and do this from the start. If you continue to
have problems create a new stored procedure just for testing .
create procedure dbo.testproc
@.PARAM1 int
as
select 'Parameter passed in = ' + @.PARAM1 as Message
return
Get the above procedure to work for you so you know how to call a stored
procedure they way I am telling you (do not use exec).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> i'm sorry, bruce, but where do i define the parameters? rs is not
> detecting
> them. in my 1st dataset i've got cmd type stored procedure and the proc
> name
> is in the query string. i assumed i would put the 1st parameter in on the
> parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> i
> gave it @.ch and the value of 1, but when i attempted to run it, it threw
> me a
> 'define query parameters box asking me to put the '1' in it.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> If you are going against SQL Server do not run your stored procedure this
>> way. Pick command type of stored procedure. RS will detect the
>> parameters.
>> If going against ODBC or OLEDB driver (which uses ? format for
>> parameters)
>> then pick text as the command type and do this:
>> myproc ?
>> Create multiple datasets and for each one you should call the stored
>> procedure for each one.
>> Bruce Loehle-Conger
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> > And, if I blow away the 2nd dataset and just give my 1st one
>> > parameters,
>> > it
>> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
>> > works
>> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
>> > Data
>> > tab it returns an error: SQL Syntax Errors Encountered...The designer
>> > does
>> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
>> > my
>> > results are still returned to me. On 'Preview' tab, however, I get no
>> > data/results at all.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Yes, you are calling it three times. In RS you create three datasets.
>> >> Go
>> >> to
>> >> the dataset tab and there is a combo box with the name of the dataset,
>> >> you
>> >> can click on that and there is a an option for a new.
>> >>
>> >> In your stored procedure
>> >>
>> >> if @.WHICHRESULTSET = 1
>> >> begin
>> >> --return the first resultset here
>> >> end
>> >> etc
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> > Bruce, or somebody else, might you give me an example of how to give
>> >> > the
>> >> > proc
>> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> > display
>> >> > them?
>> >> > Or, am I giving it three parameters and calling it three times? If
>> >> > so,
>> >> > how
>> >> > would i call the 3 procs in RS?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Configure your existing stored procedure to accept a parameter (you
>> >> >> can
>> >> >> make
>> >> >> it optional so that it doesn't break existing code).
>> >> >>
>> >> >> Then call it three times in RS with a static value and create three
>> >> >> datasets.
>> >> >> For instance dataset1
>> >> >> yourproc 1
>> >> >>
>> >> >> Dataset2
>> >> >> yourproc 2
>> >> >>
>> >> >> etc.
>> >> >>
>> >> >> Then in your stored procedure return the appropriate resultset
>> >> >> based
>> >> >> on
>> >> >> the
>> >> >> parameter.
>> >> >>
>> >> >> Downside is that your sp is being run three times.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
>> >> >> > please,
>> >> >> > on
>> >> >> > the second, possibly third procedure?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> This is three resultsets. RS does not have the ability to handle
>> >> >> >> that.
>> >> >> >> There
>> >> >> >> is no work around from RS side. You could create another stored
>> >> >> >> procedure
>> >> >> >> that calls this one and have it return just one of the
>> >> >> >> resultsets.
>> >> >> >>
>> >> >> >> RS can deal with multiple datasets quite well, but each stored
>> >> >> >> procedure
>> >> >> >> call can only return one.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
>> >> >> >> > that.
>> >> >> >> > one
>> >> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >> >
>> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> > -- -- -- --
>> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> > 33,333,333,333.33
>> >> >> >> >
>> >> >> >> > #Stocks Volume Total $
>> >> >> >> > -- -- --
>> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >
>> >> >> >> > EndPoint Liquidity #Trades Volume Total $
>> >> >> >> > -- -- -- -- --
>> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> > 583,102,631.33
>> >> >> >> > AAAA Opening 1 27
>> >> >> >> > 3,412.53
>> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> > 444,521,928.10
>> >> >> >> > AAAA Route 41 4,543
>> >> >> >> > 103,291.31
>> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> > 178,600,674.78
>> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> > 44,276,419.41
>> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> > 40,267,318.25
>> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> > 746,570,071.43
>> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> > 483,329,796.97
>> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> > 6,655,913.26
>> >> >> >> > DDDD Route 2 62,500
>> >> >> >> > 2,539,375.00
>> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> > 19,136,233.44
>> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> > 6,227,451.69
>> >> >> >> >
>> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >
>> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> > -- -- -- --
>> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> > 33,333,333,333.33
>> >> >> >> >
>> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> > handle
>> >> >> >> > the
>> >> >> >> > 1st
>> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
>> >> >> >> > body.
>> >> >> >> > Do
>> >> >> >> > you
>> >> >> >> > have any idea how I can achieve this report via reporting
>> >> >> >> > svcs?
>> >> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >> >
>> >> >> >> > --Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Pick the command type as stored procedure and then just enter
>> >> >> >> >> the
>> >> >> >> >> name
>> >> >> >> >> of
>> >> >> >> >> the stored procedure. When you click on the ! you should get
>> >> >> >> >> back
>> >> >> >> >> the
>> >> >> >> >> data
>> >> >> >> >> and the fields. If you do not get the field list populated
>> >> >> >> >> then
>> >> >> >> >> click
>> >> >> >> >> on
>> >> >> >> >> the
>> >> >> >> >> refresh fields button (to the right of the ..., it looks like
>> >> >> >> >> the
>> >> >> >> >> refresh
>> >> >> >> >> button for IE).
>> >> >> >> >>
>> >> >> >> >> Note that RS only works with the first resultset returned. It
>> >> >> >> >> cannot
>> >> >> >> >> handle
>> >> >> >> >> mutliple resultsets.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> >> > Hi. I have a need to create a number of different reports
>> >> >> >> >> > via
>> >> >> >> >> > Reporting
>> >> >> >> >> > Services. All of which are based on stored procedures,
>> >> >> >> >> > none
>> >> >> >> >> > of
>> >> >> >> >> > which
>> >> >> >> >> > require
>> >> >> >> >> > any parameters. Most if not all of the report is
>> >> >> >> >> > calculated.
>> >> >> >> >> > I
>> >> >> >> >> > am
>> >> >> >> >> > struggling badly to get even the most basic of the fields
>> >> >> >> >> > in
>> >> >> >> >> > place
>> >> >> >> >> > w/the
>> >> >> >> >> > correct expressions. The only one I actually got to accept
>> >> >> >> >> > the
>> >> >> >> >> > expression
>> >> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >> >
>> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >> >
>> >> >> >> >> > It, too, fails to preview, indicating the value expression
>> >> >> >> >> > for
>> >> >> >> >> > the
>> >> >> >> >> > field
>> >> >> >> >> > contains an error. Again, all of the other report items
>> >> >> >> >> > are
>> >> >> >> >> > calculated
>> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,
>> >> >> >> >> > CASTs,
>> >> >> >> >> > etc.
>> >> >> >> >> > Using
>> >> >> >> >> > the
>> >> >> >> >> > report designer/report wizard to 'do it for me' only
>> >> >> >> >> > returns
>> >> >> >> >> > Date
>> >> >> >> >> > and a
>> >> >> >> >> > couple fields that are not even in my resultset. like one
>> >> >> >> >> > of
>> >> >> >> >> > my
>> >> >> >> >> > values
>> >> >> >> >> > in
>> >> >> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> >> >> > available
>> >> >> >> >> > is
>> >> >> >> >> > 'ID__Total__'
>> >> >> >> >> >
>> >> >> >> >> > Further, in VS I've got the report open and am on the data
>> >> >> >> >> > tab, i
>> >> >> >> >> > hit
>> >> >> >> >> > the
>> >> >> >> >> > Run option, I receive this error: An error occurred while
>> >> >> >> >> > retrieving
>> >> >> >> >> > the
>> >> >> >> >> > parameters in the query. Could not locate entry in
>> >> >> >> >> > sysdatabases
>> >> >> >> >> > for
>> >> >> >> >> > database
>> >> >> >> >> > 'EXEC databasename'. No entry found with that name. Make
>> >> >> >> >> > sure
>> >> >> >> >> > that
>> >> >> >> >> > the
>> >> >> >> >> > name
>> >> >> >> >> > is entered correctly.'
>> >> >> >> >> >
>> >> >> >> >> > Clearly I am doing something very wrong with the stored
>> >> >> >> >> > procedure
>> >> >> >> >> > definition. Like I said, all of these reports are based on
>> >> >> >> >> > procedures,
>> >> >> >> >> > can
>> >> >> >> >> > anybody give me some suggestion/direction on the right way
>> >> >> >> >> > to
>> >> >> >> >> > call
>> >> >> >> >> > the
>> >> >> >> >> > procs?
>> >> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
>> >> >> >> >> > that's
>> >> >> >> >> > it.
>> >> >> >> >> > Please advise.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > -- Lynn
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||yes, it's sql2k, i am somewhat of a RS newbie, but I spent last week setting
reports up for all my sql jobs, just to kind of practice in the RS arena.
everything went flawlessly. i even set up one of the company reports just
fine, but it was a proc with only a single resultset. everything else is
multiple resultsets, i'm just having a very difficult time. but, i will give
this a shot, bruce. thank you, bruce
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||i am not sure how to display each resultset/dataset in the same report
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||removing everything but the proc name in the query string in dataset fails
w/this:
Could not generate a list of fields for the query.
Check the query syntax or click Refresh Fields on the query toolbar.
Line 1: Incorrect syntax near 'usp_procname'.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||my bad, bruce, that was because i had text in cmd type. having changed it to
stored procedure, it pops up the 'define query parameters' box, asking me to
put something in. how do i pass those in dynamically?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||last one for a while, bruce, i promise. i've got all 4 datasets in there,
each asks me for a parameter, i put 1,2,3 and 4 into each, getting my 'whole
report' in four small subsets of data. how do i get this to happen on the
report page automatically without needing user input?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||Query parameters and report parameters seem to be the same thing but they
are not. RS automatically creates a report parameter for each query
parameter but instead you can map the query parameter to a constant. Click
on the ... for the dataset, go to the parameters tab. On the right you will
see it mapping to the report parameter, click on that and select expression.
In expression put = 1 (assuming it is an integert expression) for the first
dataset, =2 etc. Then go to report layout, report menu-> report parameters
and then delete the report parameters created for you.
You are very very close to the solution.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> last one for a while, bruce, i promise. i've got all 4 datasets in there,
> each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> 'whole
> report' in four small subsets of data. how do i get this to happen on the
> report page automatically without needing user input?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Are you going against SQL Server?
>> If so, then just select tored procedure for the command type and just put
>> in
>> the name of the stored procedure. Do not put exec in from of it or
>> anything
>> else. It should detect the parameter and prompt you for it. It should
>> also
>> create a report parameter as well for you.
>> Try creating a new dataset and do this from the start. If you continue to
>> have problems create a new stored procedure just for testing .
>> create procedure dbo.testproc
>> @.PARAM1 int
>> as
>> select 'Parameter passed in = ' + @.PARAM1 as Message
>> return
>> Get the above procedure to work for you so you know how to call a stored
>> procedure they way I am telling you (do not use exec).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> > i'm sorry, bruce, but where do i define the parameters? rs is not
>> > detecting
>> > them. in my 1st dataset i've got cmd type stored procedure and the
>> > proc
>> > name
>> > is in the query string. i assumed i would put the 1st parameter in on
>> > the
>> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets,
>> > so
>> > i
>> > gave it @.ch and the value of 1, but when i attempted to run it, it
>> > threw
>> > me a
>> > 'define query parameters box asking me to put the '1' in it.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> If you are going against SQL Server do not run your stored procedure
>> >> this
>> >> way. Pick command type of stored procedure. RS will detect the
>> >> parameters.
>> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> parameters)
>> >> then pick text as the command type and do this:
>> >> myproc ?
>> >>
>> >> Create multiple datasets and for each one you should call the stored
>> >> procedure for each one.
>> >>
>> >> Bruce Loehle-Conger
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> > parameters,
>> >> > it
>> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> > results,
>> >> > works
>> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN
>> >> > in
>> >> > Data
>> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> > designer
>> >> > does
>> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK'
>> >> > and
>> >> > my
>> >> > results are still returned to me. On 'Preview' tab, however, I get
>> >> > no
>> >> > data/results at all.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> datasets.
>> >> >> Go
>> >> >> to
>> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> dataset,
>> >> >> you
>> >> >> can click on that and there is a an option for a new.
>> >> >>
>> >> >> In your stored procedure
>> >> >>
>> >> >> if @.WHICHRESULTSET = 1
>> >> >> begin
>> >> >> --return the first resultset here
>> >> >> end
>> >> >> etc
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> > Bruce, or somebody else, might you give me an example of how to
>> >> >> > give
>> >> >> > the
>> >> >> > proc
>> >> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> >> > display
>> >> >> > them?
>> >> >> > Or, am I giving it three parameters and calling it three times?
>> >> >> > If
>> >> >> > so,
>> >> >> > how
>> >> >> > would i call the 3 procs in RS?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Configure your existing stored procedure to accept a parameter
>> >> >> >> (you
>> >> >> >> can
>> >> >> >> make
>> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >>
>> >> >> >> Then call it three times in RS with a static value and create
>> >> >> >> three
>> >> >> >> datasets.
>> >> >> >> For instance dataset1
>> >> >> >> yourproc 1
>> >> >> >>
>> >> >> >> Dataset2
>> >> >> >> yourproc 2
>> >> >> >>
>> >> >> >> etc.
>> >> >> >>
>> >> >> >> Then in your stored procedure return the appropriate resultset
>> >> >> >> based
>> >> >> >> on
>> >> >> >> the
>> >> >> >> parameter.
>> >> >> >>
>> >> >> >> Downside is that your sp is being run three times.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
>> >> >> >> > more,
>> >> >> >> > please,
>> >> >> >> > on
>> >> >> >> > the second, possibly third procedure?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> This is three resultsets. RS does not have the ability to
>> >> >> >> >> handle
>> >> >> >> >> that.
>> >> >> >> >> There
>> >> >> >> >> is no work around from RS side. You could create another
>> >> >> >> >> stored
>> >> >> >> >> procedure
>> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> resultsets.
>> >> >> >> >>
>> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> stored
>> >> >> >> >> procedure
>> >> >> >> >> call can only return one.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple
>> >> >> >> >> > as
>> >> >> >> >> > that.
>> >> >> >> >> > one
>> >> >> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >> >> >
>> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> > -- -- -- --
>> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > #Stocks Volume Total $
>> >> >> >> >> > -- -- --
>> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > EndPoint Liquidity #Trades Volume
>> >> >> >> >> > Total $
>> >> >> >> >> > -- -- -- -- --
>> >> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> >> > 583,102,631.33
>> >> >> >> >> > AAAA Opening 1 27
>> >> >> >> >> > 3,412.53
>> >> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> >> > 444,521,928.10
>> >> >> >> >> > AAAA Route 41 4,543
>> >> >> >> >> > 103,291.31
>> >> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> >> > 178,600,674.78
>> >> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> >> > 44,276,419.41
>> >> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> >> > 40,267,318.25
>> >> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> >> > 746,570,071.43
>> >> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> >> > 483,329,796.97
>> >> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> >> > 6,655,913.26
>> >> >> >> >> > DDDD Route 2 62,500
>> >> >> >> >> > 2,539,375.00
>> >> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> >> > 19,136,233.44
>> >> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> >> > 6,227,451.69
>> >> >> >> >> >
>> >> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >> >
>> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> > -- -- -- --
>> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> >> > handle
>> >> >> >> >> > the
>> >> >> >> >> > 1st
>> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
>> >> >> >> >> > the
>> >> >> >> >> > body.
>> >> >> >> >> > Do
>> >> >> >> >> > you
>> >> >> >> >> > have any idea how I can achieve this report via reporting
>> >> >> >> >> > svcs?
>> >> >> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >> >> >
>> >> >> >> >> > --Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Pick the command type as stored procedure and then just
>> >> >> >> >> >> enter
>> >> >> >> >> >> the
>> >> >> >> >> >> name
>> >> >> >> >> >> of
>> >> >> >> >> >> the stored procedure. When you click on the ! you should
>> >> >> >> >> >> get
>> >> >> >> >> >> back
>> >> >> >> >> >> the
>> >> >> >> >> >> data
>> >> >> >> >> >> and the fields. If you do not get the field list populated
>> >> >> >> >> >> then
>> >> >> >> >> >> click
>> >> >> >> >> >> on
>> >> >> >> >> >> the
>> >> >> >> >> >> refresh fields button (to the right of the ..., it looks
>> >> >> >> >> >> like
>> >> >> >> >> >> the
>> >> >> >> >> >> refresh
>> >> >> >> >> >> button for IE).
>> >> >> >> >> >>
>> >> >> >> >> >> Note that RS only works with the first resultset returned.
>> >> >> >> >> >> It
>> >> >> >> >> >> cannot
>> >> >> >> >> >> handle
>> >> >> >> >> >> mutliple resultsets.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> >> >> > Hi. I have a need to create a number of different
>> >> >> >> >> >> > reports
>> >> >> >> >> >> > via
>> >> >> >> >> >> > Reporting
>> >> >> >> >> >> > Services. All of which are based on stored procedures,
>> >> >> >> >> >> > none
>> >> >> >> >> >> > of
>> >> >> >> >> >> > which
>> >> >> >> >> >> > require
>> >> >> >> >> >> > any parameters. Most if not all of the report is
>> >> >> >> >> >> > calculated.
>> >> >> >> >> >> > I
>> >> >> >> >> >> > am
>> >> >> >> >> >> > struggling badly to get even the most basic of the
>> >> >> >> >> >> > fields
>> >> >> >> >> >> > in
>> >> >> >> >> >> > place
>> >> >> >> >> >> > w/the
>> >> >> >> >> >> > correct expressions. The only one I actually got to
>> >> >> >> >> >> > accept
>> >> >> >> >> >> > the
>> >> >> >> >> >> > expression
>> >> >> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >> >> >
>> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >> >> >
>> >> >> >> >> >> > It, too, fails to preview, indicating the value
>> >> >> >> >> >> > expression
>> >> >> >> >> >> > for
>> >> >> >> >> >> > the
>> >> >> >> >> >> > field
>> >> >> >> >> >> > contains an error. Again, all of the other report items
>> >> >> >> >> >> > are
>> >> >> >> >> >> > calculated
>> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||oh my goodness this is frustrating me....i did what you said, bruce, and it
almost worked. the preview report shows me three values which correspond, i
believe, to the only three fields in my report. see, they're all calculated
fields. the output of the rpt is this:
Build complete -- 0 errors, 0 warnings
The data set â'DataSet3â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
The data set â'DataSet4â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
The data set â'DataSet2â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
Preview complete -- 0 errors, 3 warnings
Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
4. The report, or the query, is not auto-generating my other fields as it
did for three that I do see. The 'Futures_Volume' is one of the fields that
was auto-generated for me, and it is in the 1st dataset. Is it that I just
need to manually add in the other fields? Please do let me know what you
think.
and thank you, bruce, for helping me through this. i truly do appreciate
it. i know i am close...and i got the other reports for my server jobs and
one of the other company reports to work. it's just these multi-resultset
reports are fighting me.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Query parameters and report parameters seem to be the same thing but they
> are not. RS automatically creates a report parameter for each query
> parameter but instead you can map the query parameter to a constant. Click
> on the ... for the dataset, go to the parameters tab. On the right you will
> see it mapping to the report parameter, click on that and select expression.
> In expression put = 1 (assuming it is an integert expression) for the first
> dataset, =2 etc. Then go to report layout, report menu-> report parameters
> and then delete the report parameters created for you.
> You are very very close to the solution.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> > last one for a while, bruce, i promise. i've got all 4 datasets in there,
> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> > 'whole
> > report' in four small subsets of data. how do i get this to happen on the
> > report page automatically without needing user input?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Are you going against SQL Server?
> >>
> >> If so, then just select tored procedure for the command type and just put
> >> in
> >> the name of the stored procedure. Do not put exec in from of it or
> >> anything
> >> else. It should detect the parameter and prompt you for it. It should
> >> also
> >> create a report parameter as well for you.
> >>
> >> Try creating a new dataset and do this from the start. If you continue to
> >> have problems create a new stored procedure just for testing .
> >>
> >> create procedure dbo.testproc
> >> @.PARAM1 int
> >> as
> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> return
> >>
> >> Get the above procedure to work for you so you know how to call a stored
> >> procedure they way I am telling you (do not use exec).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
> >> > detecting
> >> > them. in my 1st dataset i've got cmd type stored procedure and the
> >> > proc
> >> > name
> >> > is in the query string. i assumed i would put the 1st parameter in on
> >> > the
> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets,
> >> > so
> >> > i
> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
> >> > threw
> >> > me a
> >> > 'define query parameters box asking me to put the '1' in it.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> If you are going against SQL Server do not run your stored procedure
> >> >> this
> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> parameters.
> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> parameters)
> >> >> then pick text as the command type and do this:
> >> >> myproc ?
> >> >>
> >> >> Create multiple datasets and for each one you should call the stored
> >> >> procedure for each one.
> >> >>
> >> >> Bruce Loehle-Conger
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> > parameters,
> >> >> > it
> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> > results,
> >> >> > works
> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN
> >> >> > in
> >> >> > Data
> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> > designer
> >> >> > does
> >> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK'
> >> >> > and
> >> >> > my
> >> >> > results are still returned to me. On 'Preview' tab, however, I get
> >> >> > no
> >> >> > data/results at all.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> datasets.
> >> >> >> Go
> >> >> >> to
> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> dataset,
> >> >> >> you
> >> >> >> can click on that and there is a an option for a new.
> >> >> >>
> >> >> >> In your stored procedure
> >> >> >>
> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> begin
> >> >> >> --return the first resultset here
> >> >> >> end
> >> >> >> etc
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> > Bruce, or somebody else, might you give me an example of how to
> >> >> >> > give
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> >> > display
> >> >> >> > them?
> >> >> >> > Or, am I giving it three parameters and calling it three times?
> >> >> >> > If
> >> >> >> > so,
> >> >> >> > how
> >> >> >> > would i call the 3 procs in RS?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Configure your existing stored procedure to accept a parameter
> >> >> >> >> (you
> >> >> >> >> can
> >> >> >> >> make
> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >>
> >> >> >> >> Then call it three times in RS with a static value and create
> >> >> >> >> three
> >> >> >> >> datasets.
> >> >> >> >> For instance dataset1
> >> >> >> >> yourproc 1
> >> >> >> >>
> >> >> >> >> Dataset2
> >> >> >> >> yourproc 2
> >> >> >> >>
> >> >> >> >> etc.
> >> >> >> >>
> >> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> >> based
> >> >> >> >> on
> >> >> >> >> the
> >> >> >> >> parameter.
> >> >> >> >>
> >> >> >> >> Downside is that your sp is being run three times.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
> >> >> >> >> > more,
> >> >> >> >> > please,
> >> >> >> >> > on
> >> >> >> >> > the second, possibly third procedure?
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> This is three resultsets. RS does not have the ability to
> >> >> >> >> >> handle
> >> >> >> >> >> that.
> >> >> >> >> >> There
> >> >> >> >> >> is no work around from RS side. You could create another
> >> >> >> >> >> stored
> >> >> >> >> >> procedure
> >> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> >> resultsets.
> >> >> >> >> >>
> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
> >> >> >> >> >> stored
> >> >> >> >> >> procedure
> >> >> >> >> >> call can only return one.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple
> >> >> >> >> >> > as
> >> >> >> >> >> > that.
> >> >> >> >> >> > one
> >> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >> >
> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> >> > -- -- -- --
> >> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> >> > -- -- --
> >> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > EndPoint Liquidity #Trades Volume
> >> >> >> >> >> > Total $
> >> >> >> >> >> > -- -- -- -- --
> >> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> >> > 583,102,631.33
> >> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> >> > 3,412.53
> >> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> >> > 444,521,928.10
> >> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> >> > 103,291.31
> >> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> >> > 178,600,674.78
> >> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> >> > 44,276,419.41
> >> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> >> > 40,267,318.25
> >> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> >> > 746,570,071.43
> >> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> >> > 483,329,796.97
> >> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> >> > 6,655,913.26
> >> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> >> > 2,539,375.00
> >> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> >> > 19,136,233.44
> >> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> >> > 6,227,451.69
> >> >> >> >> >> >
> >> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >> >
> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> >> > -- -- -- --
> >> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> >> > handle
> >> >> >> >> >> > the
> >> >> >> >> >> > 1st
> >> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
> >> >> >> >> >> > the
> >> >> >> >> >> > body.
> >> >> >> >> >> > Do
> >> >> >> >> >> > you
> >> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> >> > svcs?
> >> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >> >
> >> >> >> >> >> > --Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Pick the command type as stored procedure and then just
> >> >> >> >> >> >> enter
> >> >> >> >> >> >> the
> >> >> >> >> >> >> name
> >> >> >> >> >> >> of
> >> >> >> >> >> >> the stored procedure. When you click on the ! you should
> >> >> >> >> >> >> get
> >> >> >> >> >> >> back|||For each of your datasets make sure there is a field list. Sometimes you
have to click on the refresh fields button (to the right of the ...).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> oh my goodness this is frustrating me....i did what you said, bruce, and
> it
> almost worked. the preview report shows me three values which correspond,
> i
> believe, to the only three fields in my report. see, they're all
> calculated
> fields. the output of the rpt is this:
> Build complete -- 0 errors, 0 warnings
> The data set 'DataSet3' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> The data set 'DataSet4' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> The data set 'DataSet2' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> Preview complete -- 0 errors, 3 warnings
> Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
> 4. The report, or the query, is not auto-generating my other fields as it
> did for three that I do see. The 'Futures_Volume' is one of the fields
> that
> was auto-generated for me, and it is in the 1st dataset. Is it that I
> just
> need to manually add in the other fields? Please do let me know what you
> think.
> and thank you, bruce, for helping me through this. i truly do appreciate
> it. i know i am close...and i got the other reports for my server jobs
> and
> one of the other company reports to work. it's just these multi-resultset
> reports are fighting me.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Query parameters and report parameters seem to be the same thing but they
>> are not. RS automatically creates a report parameter for each query
>> parameter but instead you can map the query parameter to a constant.
>> Click
>> on the ... for the dataset, go to the parameters tab. On the right you
>> will
>> see it mapping to the report parameter, click on that and select
>> expression.
>> In expression put = 1 (assuming it is an integert expression) for the
>> first
>> dataset, =2 etc. Then go to report layout, report menu-> report
>> parameters
>> and then delete the report parameters created for you.
>> You are very very close to the solution.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> > last one for a while, bruce, i promise. i've got all 4 datasets in
>> > there,
>> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
>> > 'whole
>> > report' in four small subsets of data. how do i get this to happen on
>> > the
>> > report page automatically without needing user input?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Are you going against SQL Server?
>> >>
>> >> If so, then just select tored procedure for the command type and just
>> >> put
>> >> in
>> >> the name of the stored procedure. Do not put exec in from of it or
>> >> anything
>> >> else. It should detect the parameter and prompt you for it. It should
>> >> also
>> >> create a report parameter as well for you.
>> >>
>> >> Try creating a new dataset and do this from the start. If you continue
>> >> to
>> >> have problems create a new stored procedure just for testing .
>> >>
>> >> create procedure dbo.testproc
>> >> @.PARAM1 int
>> >> as
>> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> return
>> >>
>> >> Get the above procedure to work for you so you know how to call a
>> >> stored
>> >> procedure they way I am telling you (do not use exec).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
>> >> > detecting
>> >> > them. in my 1st dataset i've got cmd type stored procedure and the
>> >> > proc
>> >> > name
>> >> > is in the query string. i assumed i would put the 1st parameter in
>> >> > on
>> >> > the
>> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> > datasets,
>> >> > so
>> >> > i
>> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
>> >> > threw
>> >> > me a
>> >> > 'define query parameters box asking me to put the '1' in it.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> If you are going against SQL Server do not run your stored
>> >> >> procedure
>> >> >> this
>> >> >> way. Pick command type of stored procedure. RS will detect the
>> >> >> parameters.
>> >> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> >> parameters)
>> >> >> then pick text as the command type and do this:
>> >> >> myproc ?
>> >> >>
>> >> >> Create multiple datasets and for each one you should call the
>> >> >> stored
>> >> >> procedure for each one.
>> >> >>
>> >> >> Bruce Loehle-Conger
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> >> > parameters,
>> >> >> > it
>> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> >> > results,
>> >> >> > works
>> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
>> >> >> > RUN
>> >> >> > in
>> >> >> > Data
>> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> >> > designer
>> >> >> > does
>> >> >> > not graphically support the EXEC SQL Construct' but, i hit
>> >> >> > 'OK'
>> >> >> > and
>> >> >> > my
>> >> >> > results are still returned to me. On 'Preview' tab, however, I
>> >> >> > get
>> >> >> > no
>> >> >> > data/results at all.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> >> datasets.
>> >> >> >> Go
>> >> >> >> to
>> >> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> >> dataset,
>> >> >> >> you
>> >> >> >> can click on that and there is a an option for a new.
>> >> >> >>
>> >> >> >> In your stored procedure
>> >> >> >>
>> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> begin
>> >> >> >> --return the first resultset here
>> >> >> >> end
>> >> >> >> etc
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> > Bruce, or somebody else, might you give me an example of how
>> >> >> >> > to
>> >> >> >> > give
>> >> >> >> > the
>> >> >> >> > proc
>> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> >> >> > display
>> >> >> >> > them?
>> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> > times?
>> >> >> >> > If
>> >> >> >> > so,
>> >> >> >> > how
>> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> parameter
>> >> >> >> >> (you
>> >> >> >> >> can
>> >> >> >> >> make
>> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >>
>> >> >> >> >> Then call it three times in RS with a static value and create
>> >> >> >> >> three
>> >> >> >> >> datasets.
>> >> >> >> >> For instance dataset1
>> >> >> >> >> yourproc 1
>> >> >> >> >>
>> >> >> >> >> Dataset2
>> >> >> >> >> yourproc 2
>> >> >> >> >>
>> >> >> >> >> etc.
>> >> >> >> >>
>> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> resultset
>> >> >> >> >> based
>> >> >> >> >> on
>> >> >> >> >> the
>> >> >> >> >> parameter.
>> >> >> >> >>
>> >> >> >> >> Downside is that your sp is being run three times.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
>> >> >> >> >> > more,
>> >> >> >> >> > please,
>> >> >> >> >> > on
>> >> >> >> >> > the second, possibly third procedure?
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> This is three resultsets. RS does not have the ability to
>> >> >> >> >> >> handle
>> >> >> >> >> >> that.
>> >> >> >> >> >> There
>> >> >> >> >> >> is no work around from RS side. You could create another
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> >> resultsets.
>> >> >> >> >> >>
>> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> call can only return one.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
>> >> >> >> >> >> > simple
>> >> >> >> >> >> > as
>> >> >> >> >> >> > that.
>> >> >> >> >> >> > one
>> >> >> >> >> >> > remaining problem, though. one of my reports is like
>> >> >> >> >> >> > this:
>> >> >> >> >> >> >
>> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> >> > -- -- -- --
>> >> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > #Stocks Volume Total $
>> >> >> >> >> >> > -- -- --
>> >> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > EndPoint Liquidity #Trades Volume
>> >> >> >> >> >> > Total $
>> >> >> >> >> >> > -- -- -- -- --
>> >> >> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> >> >> > 583,102,631.33
>> >> >> >> >> >> > AAAA Opening 1 27
>> >> >> >> >> >> > 3,412.53
>> >> >> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> >> >> > 444,521,928.10
>> >> >> >> >> >> > AAAA Route 41 4,543
>> >> >> >> >> >> > 103,291.31
>> >> >> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> >> >> > 178,600,674.78
>> >> >> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> >> >> > 44,276,419.41
>> >> >> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> >> >> > 40,267,318.25
>> >> >> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> >> >> > 746,570,071.43
>> >> >> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> >> >> > 483,329,796.97
>> >> >> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> >> >> > 6,655,913.26
>> >> >> >> >> >> > DDDD Route 2 62,500
>> >> >> >> >> >> > 2,539,375.00
>> >> >> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> >> >> > 19,136,233.44
>> >> >> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> >> >> > 6,227,451.69
>> >> >> >> >> >> >
>> >> >> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >> >> >
>> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> >> > -- -- -- --
>> >> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> >> >> > handle
>> >> >> >> >> >> > the
>> >> >> >> >> >> > 1st
>> >> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
>> >> >> >> >> >> > the
>> >> >> >> >> >> > body.
>> >> >> >> >> >> > Do
>> >> >> >> >> >> > you
>> >> >> >> >> >> > have any idea how I can achieve this report via
>> >> >> >> >> >> > reporting
>> >> >> >> >> >> > svcs?
>> >> >> >> >> >> > Unfortunately, this is very important. Please do
>> >> >> >> >> >> > advise.
>> >> >> >> >> >> >
>> >> >> >> >> >> > --Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Pick the command type as stored procedure and then just
>> >> >> >> >> >> >> enter
>> >> >> >> >> >> >> the
>> >> >> >> >> >> >> name
>> >> >> >> >> >> >> of
>> >> >> >> >> >> >> the stored procedure. When you click on the ! you
>> >> >> >> >> >> >> should
>> >> >> >> >> >> >> get
>> >> >> >> >> >> >> back|||Bruce, every time I refresh the fields, it pops the 1st three back in the
list. They're the first three in the report, and i guess they're the only
ones in that first resultset. So, I go into dataset 2, 3 and 4, all the same
3 fields are listed. i remove them per dataset, hit refresh, and the same 3
come back.
-- Lynn
"Bruce L-C [MVP]" wrote:
> For each of your datasets make sure there is a field list. Sometimes you
> have to click on the refresh fields button (to the right of the ...).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> > oh my goodness this is frustrating me....i did what you said, bruce, and
> > it
> > almost worked. the preview report shows me three values which correspond,
> > i
> > believe, to the only three fields in my report. see, they're all
> > calculated
> > fields. the output of the rpt is this:
> >
> > Build complete -- 0 errors, 0 warnings
> > The data set 'DataSet3' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > The data set 'DataSet4' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > The data set 'DataSet2' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > Preview complete -- 0 errors, 3 warnings
> >
> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
> > 4. The report, or the query, is not auto-generating my other fields as it
> > did for three that I do see. The 'Futures_Volume' is one of the fields
> > that
> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> > just
> > need to manually add in the other fields? Please do let me know what you
> > think.
> >
> > and thank you, bruce, for helping me through this. i truly do appreciate
> > it. i know i am close...and i got the other reports for my server jobs
> > and
> > one of the other company reports to work. it's just these multi-resultset
> > reports are fighting me.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Query parameters and report parameters seem to be the same thing but they
> >> are not. RS automatically creates a report parameter for each query
> >> parameter but instead you can map the query parameter to a constant.
> >> Click
> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> will
> >> see it mapping to the report parameter, click on that and select
> >> expression.
> >> In expression put = 1 (assuming it is an integert expression) for the
> >> first
> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> parameters
> >> and then delete the report parameters created for you.
> >>
> >> You are very very close to the solution.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> > there,
> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> >> > 'whole
> >> > report' in four small subsets of data. how do i get this to happen on
> >> > the
> >> > report page automatically without needing user input?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Are you going against SQL Server?
> >> >>
> >> >> If so, then just select tored procedure for the command type and just
> >> >> put
> >> >> in
> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> anything
> >> >> else. It should detect the parameter and prompt you for it. It should
> >> >> also
> >> >> create a report parameter as well for you.
> >> >>
> >> >> Try creating a new dataset and do this from the start. If you continue
> >> >> to
> >> >> have problems create a new stored procedure just for testing .
> >> >>
> >> >> create procedure dbo.testproc
> >> >> @.PARAM1 int
> >> >> as
> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> return
> >> >>
> >> >> Get the above procedure to work for you so you know how to call a
> >> >> stored
> >> >> procedure they way I am telling you (do not use exec).
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
> >> >> > detecting
> >> >> > them. in my 1st dataset i've got cmd type stored procedure and the
> >> >> > proc
> >> >> > name
> >> >> > is in the query string. i assumed i would put the 1st parameter in
> >> >> > on
> >> >> > the
> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> > datasets,
> >> >> > so
> >> >> > i
> >> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
> >> >> > threw
> >> >> > me a
> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> procedure
> >> >> >> this
> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> parameters.
> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> parameters)
> >> >> >> then pick text as the command type and do this:
> >> >> >> myproc ?
> >> >> >>
> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> stored
> >> >> >> procedure for each one.
> >> >> >>
> >> >> >> Bruce Loehle-Conger
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> > parameters,
> >> >> >> > it
> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> > results,
> >> >> >> > works
> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> > RUN
> >> >> >> > in
> >> >> >> > Data
> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> > designer
> >> >> >> > does
> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> > 'OK'
> >> >> >> > and
> >> >> >> > my
> >> >> >> > results are still returned to me. On 'Preview' tab, however, I
> >> >> >> > get
> >> >> >> > no
> >> >> >> > data/results at all.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> datasets.
> >> >> >> >> Go
> >> >> >> >> to
> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> dataset,
> >> >> >> >> you
> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >>
> >> >> >> >> In your stored procedure
> >> >> >> >>
> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> begin
> >> >> >> >> --return the first resultset here
> >> >> >> >> end
> >> >> >> >> etc
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> > Bruce, or somebody else, might you give me an example of how
> >> >> >> >> > to
> >> >> >> >> > give
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> >> >> > display
> >> >> >> >> > them?
> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> > times?
> >> >> >> >> > If
> >> >> >> >> > so,
> >> >> >> >> > how
> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> parameter
> >> >> >> >> >> (you
> >> >> >> >> >> can
> >> >> >> >> >> make
> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >>
> >> >> >> >> >> Then call it three times in RS with a static value and create
> >> >> >> >> >> three
> >> >> >> >> >> datasets.
> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> yourproc 1
> >> >> >> >> >>
> >> >> >> >> >> Dataset2
> >> >> >> >> >> yourproc 2
> >> >> >> >> >>
> >> >> >> >> >> etc.
> >> >> >> >> >>
> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> resultset
> >> >> >> >> >> based
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> parameter.
> >> >> >> >> >>
> >> >> >> >> >> Downside is that your sp is being run three times.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
> >> >> >> >> >> > more,
> >> >> >> >> >> > please,
> >> >> >> >> >> > on
> >> >> >> >> >> > the second, possibly third procedure?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> This is three resultsets. RS does not have the ability to
> >> >> >> >> >> >> handle
> >> >> >> >> >> >> that.
> >> >> >> >> >> >> There
> >> >> >> >> >> >> is no work around from RS side. You could create another
> >> >> >> >> >> >> stored
> >> >> >> >> >> >> procedure
> >> >> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> >> >> resultsets.
> >> >> >> >> >> >>
> >> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
> >> >> >> >> >> >> stored
> >> >> >> >> >> >> procedure
> >> >> >> >> >> >> call can only return one.
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> --
> >> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >> >>
> >> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
> >> >> >> >> >> >> > simple
> >> >> >> >> >> >> > as
> >> >> >> >> >> >> > that.
> >> >> >> >> >> >> > one
> >> >> >> >> >> >> > remaining problem, though. one of my reports is like|||Ok, what is happening is that it is detecting the first resultset. What you
can do it is add the fields manually. In the field list add a new field and
name it correctly for what will be coming back. (Right mouse click in the
field list).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> Bruce, every time I refresh the fields, it pops the 1st three back in the
> list. They're the first three in the report, and i guess they're the only
> ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> same
> 3 fields are listed. i remove them per dataset, hit refresh, and the same
> 3
> come back.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> For each of your datasets make sure there is a field list. Sometimes you
>> have to click on the refresh fields button (to the right of the ...).
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> > oh my goodness this is frustrating me....i did what you said, bruce,
>> > and
>> > it
>> > almost worked. the preview report shows me three values which
>> > correspond,
>> > i
>> > believe, to the only three fields in my report. see, they're all
>> > calculated
>> > fields. the output of the rpt is this:
>> >
>> > Build complete -- 0 errors, 0 warnings
>> > The data set 'DataSet3' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > The data set 'DataSet4' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > The data set 'DataSet2' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > Preview complete -- 0 errors, 3 warnings
>> >
>> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
>> > and
>> > 4. The report, or the query, is not auto-generating my other fields as
>> > it
>> > did for three that I do see. The 'Futures_Volume' is one of the fields
>> > that
>> > was auto-generated for me, and it is in the 1st dataset. Is it that I
>> > just
>> > need to manually add in the other fields? Please do let me know what
>> > you
>> > think.
>> >
>> > and thank you, bruce, for helping me through this. i truly do
>> > appreciate
>> > it. i know i am close...and i got the other reports for my server jobs
>> > and
>> > one of the other company reports to work. it's just these
>> > multi-resultset
>> > reports are fighting me.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Query parameters and report parameters seem to be the same thing but
>> >> they
>> >> are not. RS automatically creates a report parameter for each query
>> >> parameter but instead you can map the query parameter to a constant.
>> >> Click
>> >> on the ... for the dataset, go to the parameters tab. On the right you
>> >> will
>> >> see it mapping to the report parameter, click on that and select
>> >> expression.
>> >> In expression put = 1 (assuming it is an integert expression) for the
>> >> first
>> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> parameters
>> >> and then delete the report parameters created for you.
>> >>
>> >> You are very very close to the solution.
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
>> >> > there,
>> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
>> >> > my
>> >> > 'whole
>> >> > report' in four small subsets of data. how do i get this to happen
>> >> > on
>> >> > the
>> >> > report page automatically without needing user input?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Are you going against SQL Server?
>> >> >>
>> >> >> If so, then just select tored procedure for the command type and
>> >> >> just
>> >> >> put
>> >> >> in
>> >> >> the name of the stored procedure. Do not put exec in from of it or
>> >> >> anything
>> >> >> else. It should detect the parameter and prompt you for it. It
>> >> >> should
>> >> >> also
>> >> >> create a report parameter as well for you.
>> >> >>
>> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> continue
>> >> >> to
>> >> >> have problems create a new stored procedure just for testing .
>> >> >>
>> >> >> create procedure dbo.testproc
>> >> >> @.PARAM1 int
>> >> >> as
>> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> return
>> >> >>
>> >> >> Get the above procedure to work for you so you know how to call a
>> >> >> stored
>> >> >> procedure they way I am telling you (do not use exec).
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
>> >> >> > not
>> >> >> > detecting
>> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
>> >> >> > the
>> >> >> > proc
>> >> >> > name
>> >> >> > is in the query string. i assumed i would put the 1st parameter
>> >> >> > in
>> >> >> > on
>> >> >> > the
>> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> >> > datasets,
>> >> >> > so
>> >> >> > i
>> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
>> >> >> > it
>> >> >> > threw
>> >> >> > me a
>> >> >> > 'define query parameters box asking me to put the '1' in it.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> procedure
>> >> >> >> this
>> >> >> >> way. Pick command type of stored procedure. RS will detect the
>> >> >> >> parameters.
>> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> >> >> parameters)
>> >> >> >> then pick text as the command type and do this:
>> >> >> >> myproc ?
>> >> >> >>
>> >> >> >> Create multiple datasets and for each one you should call the
>> >> >> >> stored
>> >> >> >> procedure for each one.
>> >> >> >>
>> >> >> >> Bruce Loehle-Conger
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> >> >> > parameters,
>> >> >> >> > it
>> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> >> >> > results,
>> >> >> >> > works
>> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
>> >> >> >> > RUN
>> >> >> >> > in
>> >> >> >> > Data
>> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> >> >> > designer
>> >> >> >> > does
>> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
>> >> >> >> > 'OK'
>> >> >> >> > and
>> >> >> >> > my
>> >> >> >> > results are still returned to me. On 'Preview' tab, however,
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > no
>> >> >> >> > data/results at all.
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> >> >> datasets.
>> >> >> >> >> Go
>> >> >> >> >> to
>> >> >> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> >> >> dataset,
>> >> >> >> >> you
>> >> >> >> >> can click on that and there is a an option for a new.
>> >> >> >> >>
>> >> >> >> >> In your stored procedure
>> >> >> >> >>
>> >> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> >> begin
>> >> >> >> >> --return the first resultset here
>> >> >> >> >> end
>> >> >> >> >> etc
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> >> > Bruce, or somebody else, might you give me an example of
>> >> >> >> >> > how
>> >> >> >> >> > to
>> >> >> >> >> > give
>> >> >> >> >> > the
>> >> >> >> >> > proc
>> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
>> >> >> >> >> > will
>> >> >> >> >> > display
>> >> >> >> >> > them?
>> >> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> >> > times?
>> >> >> >> >> > If
>> >> >> >> >> > so,
>> >> >> >> >> > how
>> >> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> >> parameter
>> >> >> >> >> >> (you
>> >> >> >> >> >> can
>> >> >> >> >> >> make
>> >> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >> >>
>> >> >> >> >> >> Then call it three times in RS with a static value and
>> >> >> >> >> >> create
>> >> >> >> >> >> three
>> >> >> >> >> >> datasets.
>> >> >> >> >> >> For instance dataset1
>> >> >> >> >> >> yourproc 1
>> >> >> >> >> >>
>> >> >> >> >> >> Dataset2
>> >> >> >> >> >> yourproc 2
>> >> >> >> >> >>
>> >> >> >> >> >> etc.
>> >> >> >> >> >>
>> >> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> >> resultset
>> >> >> >> >> >> based
>> >> >> >> >> >> on
>> >> >> >> >> >> the
>> >> >> >> >> >> parameter.
>> >> >> >> >> >>
>> >> >> >> >> >> Downside is that your sp is being run three times.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a
>> >> >> >> >> >> > little
>> >> >> >> >> >> > more,
>> >> >> >> >> >> > please,
>> >> >> >> >> >> > on
>> >> >> >> >> >> > the second, possibly third procedure?
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> This is three resultsets. RS does not have the ability
>> >> >> >> >> >> >> to
>> >> >> >> >> >> >> handle
>> >> >> >> >> >> >> that.
>> >> >> >> >> >> >> There
>> >> >> >> >> >> >> is no work around from RS side. You could create
>> >> >> >> >> >> >> another
>> >> >> >> >> >> >> stored
>> >> >> >> >> >> >> procedure
>> >> >> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> >> >> resultsets.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> >> >> stored
>> >> >> >> >> >> >> procedure
>> >> >> >> >> >> >> call can only return one.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> --
>> >> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in
>> >> >> >> >> >> >> message
>> >> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
>> >> >> >> >> >> >> > simple
>> >> >> >> >> >> >> > as
>> >> >> >> >> >> >> > that.
>> >> >> >> >> >> >> > one
>> >> >> >> >> >> >> > remaining problem, though. one of my reports is like|||yep, i had tried this last week, but it failed w/ a cpl different errors. i
will try it again right now.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Ok, what is happening is that it is detecting the first resultset. What you
> can do it is add the fields manually. In the field list add a new field and
> name it correctly for what will be coming back. (Right mouse click in the
> field list).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> > Bruce, every time I refresh the fields, it pops the 1st three back in the
> > list. They're the first three in the report, and i guess they're the only
> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> > same
> > 3 fields are listed. i remove them per dataset, hit refresh, and the same
> > 3
> > come back.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> For each of your datasets make sure there is a field list. Sometimes you
> >> have to click on the refresh fields button (to the right of the ...).
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> > oh my goodness this is frustrating me....i did what you said, bruce,
> >> > and
> >> > it
> >> > almost worked. the preview report shows me three values which
> >> > correspond,
> >> > i
> >> > believe, to the only three fields in my report. see, they're all
> >> > calculated
> >> > fields. the output of the rpt is this:
> >> >
> >> > Build complete -- 0 errors, 0 warnings
> >> > The data set 'DataSet3' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet4' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet2' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > Preview complete -- 0 errors, 3 warnings
> >> >
> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
> >> > and
> >> > 4. The report, or the query, is not auto-generating my other fields as
> >> > it
> >> > did for three that I do see. The 'Futures_Volume' is one of the fields
> >> > that
> >> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> >> > just
> >> > need to manually add in the other fields? Please do let me know what
> >> > you
> >> > think.
> >> >
> >> > and thank you, bruce, for helping me through this. i truly do
> >> > appreciate
> >> > it. i know i am close...and i got the other reports for my server jobs
> >> > and
> >> > one of the other company reports to work. it's just these
> >> > multi-resultset
> >> > reports are fighting me.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Query parameters and report parameters seem to be the same thing but
> >> >> they
> >> >> are not. RS automatically creates a report parameter for each query
> >> >> parameter but instead you can map the query parameter to a constant.
> >> >> Click
> >> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> >> will
> >> >> see it mapping to the report parameter, click on that and select
> >> >> expression.
> >> >> In expression put = 1 (assuming it is an integert expression) for the
> >> >> first
> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> parameters
> >> >> and then delete the report parameters created for you.
> >> >>
> >> >> You are very very close to the solution.
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> >> > there,
> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
> >> >> > my
> >> >> > 'whole
> >> >> > report' in four small subsets of data. how do i get this to happen
> >> >> > on
> >> >> > the
> >> >> > report page automatically without needing user input?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Are you going against SQL Server?
> >> >> >>
> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> just
> >> >> >> put
> >> >> >> in
> >> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> >> anything
> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> should
> >> >> >> also
> >> >> >> create a report parameter as well for you.
> >> >> >>
> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> continue
> >> >> >> to
> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >>
> >> >> >> create procedure dbo.testproc
> >> >> >> @.PARAM1 int
> >> >> >> as
> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> return
> >> >> >>
> >> >> >> Get the above procedure to work for you so you know how to call a
> >> >> >> stored
> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> > not
> >> >> >> > detecting
> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > name
> >> >> >> > is in the query string. i assumed i would put the 1st parameter
> >> >> >> > in
> >> >> >> > on
> >> >> >> > the
> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> > datasets,
> >> >> >> > so
> >> >> >> > i
> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
> >> >> >> > it
> >> >> >> > threw
> >> >> >> > me a
> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> procedure
> >> >> >> >> this
> >> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> >> parameters.
> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> >> parameters)
> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> myproc ?
> >> >> >> >>
> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> stored
> >> >> >> >> procedure for each one.
> >> >> >> >>
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> >> > parameters,
> >> >> >> >> > it
> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> >> > results,
> >> >> >> >> > works
> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> >> > RUN
> >> >> >> >> > in
> >> >> >> >> > Data
> >> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> >> > designer
> >> >> >> >> > does
> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> >> > 'OK'
> >> >> >> >> > and
> >> >> >> >> > my
> >> >> >> >> > results are still returned to me. On 'Preview' tab, however,
> >> >> >> >> > I
> >> >> >> >> > get
> >> >> >> >> > no
> >> >> >> >> > data/results at all.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> >> datasets.
> >> >> >> >> >> Go
> >> >> >> >> >> to
> >> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> >> dataset,
> >> >> >> >> >> you
> >> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >> >>
> >> >> >> >> >> In your stored procedure
> >> >> >> >> >>
> >> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> >> begin
> >> >> >> >> >> --return the first resultset here
> >> >> >> >> >> end
> >> >> >> >> >> etc
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
> >> >> >> >> >> > how
> >> >> >> >> >> > to
> >> >> >> >> >> > give
> >> >> >> >> >> > the
> >> >> >> >> >> > proc
> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
> >> >> >> >> >> > will
> >> >> >> >> >> > display
> >> >> >> >> >> > them?
> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> >> > times?
> >> >> >> >> >> > If
> >> >> >> >> >> > so,
> >> >> >> >> >> > how
> >> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> >> parameter
> >> >> >> >> >> >> (you
> >> >> >> >> >> >> can
> >> >> >> >> >> >> make
> >> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then call it three times in RS with a static value and
> >> >> >> >> >> >> create
> >> >> >> >> >> >> three
> >> >> >> >> >> >> datasets.
> >> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> >> yourproc 1
> >> >> >> >> >> >>
> >> >> >> >> >> >> Dataset2
> >> >> >> >> >> >> yourproc 2
> >> >> >> >> >> >>
> >> >> >> >> >> >> etc.
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> >> resultset
> >> >> >> >> >> >> based
> >> >> >> >> >> >> on
> >> >> >> >> >> >> the
> >> >> >> >> >> >> parameter.|||Bruce, i apologize, this is going on and on. I attempt to add the fields
in...just as they are in dataset1, except with new values, and it fails with
this:
'The properties for the currently selected item are not valid. Please
correct all errors before continuing.'
Now, all of these values are calculated...Volume (sum of another value), #
of Trades (count of another value), etc...but the same thing applies to
dataset 1, and those fields are listed as database fields, not calculated
fields. please can you tell me what the right way to do this is?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Ok, what is happening is that it is detecting the first resultset. What you
> can do it is add the fields manually. In the field list add a new field and
> name it correctly for what will be coming back. (Right mouse click in the
> field list).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> > Bruce, every time I refresh the fields, it pops the 1st three back in the
> > list. They're the first three in the report, and i guess they're the only
> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> > same
> > 3 fields are listed. i remove them per dataset, hit refresh, and the same
> > 3
> > come back.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> For each of your datasets make sure there is a field list. Sometimes you
> >> have to click on the refresh fields button (to the right of the ...).
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> > oh my goodness this is frustrating me....i did what you said, bruce,
> >> > and
> >> > it
> >> > almost worked. the preview report shows me three values which
> >> > correspond,
> >> > i
> >> > believe, to the only three fields in my report. see, they're all
> >> > calculated
> >> > fields. the output of the rpt is this:
> >> >
> >> > Build complete -- 0 errors, 0 warnings
> >> > The data set 'DataSet3' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet4' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet2' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > Preview complete -- 0 errors, 3 warnings
> >> >
> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
> >> > and
> >> > 4. The report, or the query, is not auto-generating my other fields as
> >> > it
> >> > did for three that I do see. The 'Futures_Volume' is one of the fields
> >> > that
> >> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> >> > just
> >> > need to manually add in the other fields? Please do let me know what
> >> > you
> >> > think.
> >> >
> >> > and thank you, bruce, for helping me through this. i truly do
> >> > appreciate
> >> > it. i know i am close...and i got the other reports for my server jobs
> >> > and
> >> > one of the other company reports to work. it's just these
> >> > multi-resultset
> >> > reports are fighting me.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Query parameters and report parameters seem to be the same thing but
> >> >> they
> >> >> are not. RS automatically creates a report parameter for each query
> >> >> parameter but instead you can map the query parameter to a constant.
> >> >> Click
> >> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> >> will
> >> >> see it mapping to the report parameter, click on that and select
> >> >> expression.
> >> >> In expression put = 1 (assuming it is an integert expression) for the
> >> >> first
> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> parameters
> >> >> and then delete the report parameters created for you.
> >> >>
> >> >> You are very very close to the solution.
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> >> > there,
> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
> >> >> > my
> >> >> > 'whole
> >> >> > report' in four small subsets of data. how do i get this to happen
> >> >> > on
> >> >> > the
> >> >> > report page automatically without needing user input?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Are you going against SQL Server?
> >> >> >>
> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> just
> >> >> >> put
> >> >> >> in
> >> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> >> anything
> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> should
> >> >> >> also
> >> >> >> create a report parameter as well for you.
> >> >> >>
> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> continue
> >> >> >> to
> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >>
> >> >> >> create procedure dbo.testproc
> >> >> >> @.PARAM1 int
> >> >> >> as
> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> return
> >> >> >>
> >> >> >> Get the above procedure to work for you so you know how to call a
> >> >> >> stored
> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> > not
> >> >> >> > detecting
> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > name
> >> >> >> > is in the query string. i assumed i would put the 1st parameter
> >> >> >> > in
> >> >> >> > on
> >> >> >> > the
> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> > datasets,
> >> >> >> > so
> >> >> >> > i
> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
> >> >> >> > it
> >> >> >> > threw
> >> >> >> > me a
> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> procedure
> >> >> >> >> this
> >> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> >> parameters.
> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> >> parameters)
> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> myproc ?
> >> >> >> >>
> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> stored
> >> >> >> >> procedure for each one.
> >> >> >> >>
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> >> > parameters,
> >> >> >> >> > it
> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> >> > results,
> >> >> >> >> > works
> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> >> > RUN
> >> >> >> >> > in
> >> >> >> >> > Data
> >> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> >> > designer
> >> >> >> >> > does
> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> >> > 'OK'
> >> >> >> >> > and
> >> >> >> >> > my
> >> >> >> >> > results are still returned to me. On 'Preview' tab, however,
> >> >> >> >> > I
> >> >> >> >> > get
> >> >> >> >> > no
> >> >> >> >> > data/results at all.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> >> datasets.
> >> >> >> >> >> Go
> >> >> >> >> >> to
> >> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> >> dataset,
> >> >> >> >> >> you
> >> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >> >>
> >> >> >> >> >> In your stored procedure
> >> >> >> >> >>
> >> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> >> begin
> >> >> >> >> >> --return the first resultset here
> >> >> >> >> >> end
> >> >> >> >> >> etc
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
> >> >> >> >> >> > how
> >> >> >> >> >> > to
> >> >> >> >> >> > give
> >> >> >> >> >> > the
> >> >> >> >> >> > proc
> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
> >> >> >> >> >> > will
> >> >> >> >> >> > display
> >> >> >> >> >> > them?
> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> >> > times?
> >> >> >> >> >> > If
> >> >> >> >> >> > so,
> >> >> >> >> >> > how
> >> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> >> parameter
> >> >> >> >> >> >> (you
> >> >> >> >> >> >> can
> >> >> >> >> >> >> make
> >> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then call it three times in RS with a static value and
> >> >> >> >> >> >> create
> >> >> >> >> >> >> three
> >> >> >> >> >> >> datasets.
> >> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> >> yourproc 1
> >> >> >> >> >> >>
> >> >> >> >> >> >> Dataset2
> >> >> >> >> >> >> yourproc 2
> >> >> >> >> >> >>
> >> >> >> >> >> >> etc.
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> >> resultset
> >> >> >> >> >> >> based
> >> >> >> >> >> >> on
> >> >> >> >> >> >> the
> >> >> >> >> >> >> parameter.|||Just because they are calculated in the stored procedure does not mean they
are calculated when you manually add them to the field list. You put the
name same as the name of the field being returned and mark them as database
field. If you name them appropriately and say they are are database fields
it will work.
So, let's say you are in dataset2 which is called the stored procedure with
a parameter value of 2. When you click the execute the data comes back. Plus
you can see the name of the fields in the dataset (but not in the field
list). Add then appropriate field names to the field list.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> Bruce, i apologize, this is going on and on. I attempt to add the fields
> in...just as they are in dataset1, except with new values, and it fails
> with
> this:
> 'The properties for the currently selected item are not valid. Please
> correct all errors before continuing.'
> Now, all of these values are calculated...Volume (sum of another value), #
> of Trades (count of another value), etc...but the same thing applies to
> dataset 1, and those fields are listed as database fields, not calculated
> fields. please can you tell me what the right way to do this is?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Ok, what is happening is that it is detecting the first resultset. What
>> you
>> can do it is add the fields manually. In the field list add a new field
>> and
>> name it correctly for what will be coming back. (Right mouse click in the
>> field list).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
>> > Bruce, every time I refresh the fields, it pops the 1st three back in
>> > the
>> > list. They're the first three in the report, and i guess they're the
>> > only
>> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
>> > the
>> > same
>> > 3 fields are listed. i remove them per dataset, hit refresh, and the
>> > same
>> > 3
>> > come back.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> For each of your datasets make sure there is a field list. Sometimes
>> >> you
>> >> have to click on the refresh fields button (to the right of the ...).
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> >> > oh my goodness this is frustrating me....i did what you said,
>> >> > bruce,
>> >> > and
>> >> > it
>> >> > almost worked. the preview report shows me three values which
>> >> > correspond,
>> >> > i
>> >> > believe, to the only three fields in my report. see, they're all
>> >> > calculated
>> >> > fields. the output of the rpt is this:
>> >> >
>> >> > Build complete -- 0 errors, 0 warnings
>> >> > The data set 'DataSet3' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > The data set 'DataSet4' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > The data set 'DataSet2' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > Preview complete -- 0 errors, 3 warnings
>> >> >
>> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
>> >> > 3
>> >> > and
>> >> > 4. The report, or the query, is not auto-generating my other fields
>> >> > as
>> >> > it
>> >> > did for three that I do see. The 'Futures_Volume' is one of the
>> >> > fields
>> >> > that
>> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
>> >> > I
>> >> > just
>> >> > need to manually add in the other fields? Please do let me know
>> >> > what
>> >> > you
>> >> > think.
>> >> >
>> >> > and thank you, bruce, for helping me through this. i truly do
>> >> > appreciate
>> >> > it. i know i am close...and i got the other reports for my server
>> >> > jobs
>> >> > and
>> >> > one of the other company reports to work. it's just these
>> >> > multi-resultset
>> >> > reports are fighting me.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Query parameters and report parameters seem to be the same thing
>> >> >> but
>> >> >> they
>> >> >> are not. RS automatically creates a report parameter for each query
>> >> >> parameter but instead you can map the query parameter to a
>> >> >> constant.
>> >> >> Click
>> >> >> on the ... for the dataset, go to the parameters tab. On the right
>> >> >> you
>> >> >> will
>> >> >> see it mapping to the report parameter, click on that and select
>> >> >> expression.
>> >> >> In expression put = 1 (assuming it is an integert expression) for
>> >> >> the
>> >> >> first
>> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> >> parameters
>> >> >> and then delete the report parameters created for you.
>> >> >>
>> >> >> You are very very close to the solution.
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
>> >> >> > in
>> >> >> > there,
>> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
>> >> >> > getting
>> >> >> > my
>> >> >> > 'whole
>> >> >> > report' in four small subsets of data. how do i get this to
>> >> >> > happen
>> >> >> > on
>> >> >> > the
>> >> >> > report page automatically without needing user input?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Are you going against SQL Server?
>> >> >> >>
>> >> >> >> If so, then just select tored procedure for the command type and
>> >> >> >> just
>> >> >> >> put
>> >> >> >> in
>> >> >> >> the name of the stored procedure. Do not put exec in from of it
>> >> >> >> or
>> >> >> >> anything
>> >> >> >> else. It should detect the parameter and prompt you for it. It
>> >> >> >> should
>> >> >> >> also
>> >> >> >> create a report parameter as well for you.
>> >> >> >>
>> >> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> >> continue
>> >> >> >> to
>> >> >> >> have problems create a new stored procedure just for testing .
>> >> >> >>
>> >> >> >> create procedure dbo.testproc
>> >> >> >> @.PARAM1 int
>> >> >> >> as
>> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> >> return
>> >> >> >>
>> >> >> >> Get the above procedure to work for you so you know how to call
>> >> >> >> a
>> >> >> >> stored
>> >> >> >> procedure they way I am telling you (do not use exec).
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
>> >> >> >> > not
>> >> >> >> > detecting
>> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
>> >> >> >> > and
>> >> >> >> > the
>> >> >> >> > proc
>> >> >> >> > name
>> >> >> >> > is in the query string. i assumed i would put the 1st
>> >> >> >> > parameter
>> >> >> >> > in
>> >> >> >> > on
>> >> >> >> > the
>> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> >> >> > datasets,
>> >> >> >> > so
>> >> >> >> > i
>> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
>> >> >> >> > it,
>> >> >> >> > it
>> >> >> >> > threw
>> >> >> >> > me a
>> >> >> >> > 'define query parameters box asking me to put the '1' in it.
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> >> procedure
>> >> >> >> >> this
>> >> >> >> >> way. Pick command type of stored procedure. RS will detect
>> >> >> >> >> the
>> >> >> >> >> parameters.
>> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
>> >> >> >> >> for
>> >> >> >> >> parameters)
>> >> >> >> >> then pick text as the command type and do this:
>> >> >> >> >> myproc ?
>> >> >> >> >>
>> >> >> >> >> Create multiple datasets and for each one you should call the
>> >> >> >> >> stored
>> >> >> >> >> procedure for each one.
>> >> >> >> >>
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
>> >> >> >> >> > one
>> >> >> >> >> > parameters,
>> >> >> >> >> > it
>> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
>> >> >> >> >> > the
>> >> >> >> >> > results,
>> >> >> >> >> > works
>> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
>> >> >> >> >> > hit
>> >> >> >> >> > RUN
>> >> >> >> >> > in
>> >> >> >> >> > Data
>> >> >> >> >> > tab it returns an error: SQL Syntax Errors
>> >> >> >> >> > Encountered...The
>> >> >> >> >> > designer
>> >> >> >> >> > does
>> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
>> >> >> >> >> > hit
>> >> >> >> >> > 'OK'
>> >> >> >> >> > and
>> >> >> >> >> > my
>> >> >> >> >> > results are still returned to me. On 'Preview' tab,
>> >> >> >> >> > however,
>> >> >> >> >> > I
>> >> >> >> >> > get
>> >> >> >> >> > no
>> >> >> >> >> > data/results at all.
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Yes, you are calling it three times. In RS you create
>> >> >> >> >> >> three
>> >> >> >> >> >> datasets.
>> >> >> >> >> >> Go
>> >> >> >> >> >> to
>> >> >> >> >> >> the dataset tab and there is a combo box with the name of
>> >> >> >> >> >> the
>> >> >> >> >> >> dataset,
>> >> >> >> >> >> you
>> >> >> >> >> >> can click on that and there is a an option for a new.
>> >> >> >> >> >>
>> >> >> >> >> >> In your stored procedure
>> >> >> >> >> >>
>> >> >> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> >> >> begin
>> >> >> >> >> >> --return the first resultset here
>> >> >> >> >> >> end
>> >> >> >> >> >> etc
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
>> >> >> >> >> >> > how
>> >> >> >> >> >> > to
>> >> >> >> >> >> > give
>> >> >> >> >> >> > the
>> >> >> >> >> >> > proc
>> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that
>> >> >> >> >> >> > RS
>> >> >> >> >> >> > will
>> >> >> >> >> >> > display
>> >> >> >> >> >> > them?
>> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> >> >> > times?
>> >> >> >> >> >> > If
>> >> >> >> >> >> > so,
>> >> >> >> >> >> > how
>> >> >> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> >> >> parameter
>> >> >> >> >> >> >> (you
>> >> >> >> >> >> >> can
>> >> >> >> >> >> >> make
>> >> >> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Then call it three times in RS with a static value and
>> >> >> >> >> >> >> create
>> >> >> >> >> >> >> three
>> >> >> >> >> >> >> datasets.
>> >> >> >> >> >> >> For instance dataset1
>> >> >> >> >> >> >> yourproc 1
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Dataset2
>> >> >> >> >> >> >> yourproc 2
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> etc.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> >> >> resultset
>> >> >> >> >> >> >> based
>> >> >> >> >> >> >> on
>> >> >> >> >> >> >> the
>> >> >> >> >> >> >> parameter.|||i'm sorry, bruce, possibly this is too burdensome for you. i'm just not
getting beyond this. i delete the fields, add the new ones, the thing runs
when i hit the run...but i hit refresh and the old fields come back, the new
ones i just added are gone. even if i save everything when they're
there...they just keep blowing out.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||i think i may be almost there, bruce. hopefully...
i've added all the fields from the diff datasets into the rpt, 4 diff
tables. now when i go to preview, it doesn't show me anything, but up top
left there is a parameter box asking me for a value. and on the far right
there's a 'view report' button.
what should i do?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||d:\...\...\blah report.rdl The data set name is missing in the data region
â'data set nameâ'.
d:\...\...\blah report.rdl The data set â'DataSet2â' contains a definition
for the field â'Futures_Volumeâ'. This field is missing from the returned
result set from the data source.
'Futures_Volume' was/is in the 1st dataset, i deleted from the other three,
adding all the correct fields manually. each rpt runs fine in Data tab when i
hit the run exclamation point. but if i try to preview, i get those two
erros, the second one i get three times for each dataset (2, 3 and 4).
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||The datasets 2, 3 and 4 contain definition for futures volume...the field is
missing from the returned resultset from the data source.
possibly i'm looking at this wrong, and i should have four separate
datasets, each with different group of fields, and a single report in which
all fields (from all 4 datasets) are combined?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||You are trying to learn many things all at once. You cannot combine datasets
together however you can use the First aggegate funtion (think of it like
Sum except it returns the first value which if the dataset has a single row
is the data you want.
Normally with multiple datasets you would have multiple table controls on
your form (or a list control).
Not sure if you solved the problem of it wiping out your field list. If so,
here is a work around. Make sure your stored procedure works. Then go to
layout view. Show the dataset/fieldlist from there and delete / add fields
to the field list from there.
Note, when wanting to essentially join data into a single dataset another
technique is to use subreports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:8781DA41-EE73-4E1D-8195-42A8355BF10E@.microsoft.com...
> The datasets 2, 3 and 4 contain definition for futures volume...the field
> is
> missing from the returned resultset from the data source.
> possibly i'm looking at this wrong, and i should have four separate
> datasets, each with different group of fields, and a single report in
> which
> all fields (from all 4 datasets) are combined?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Just because they are calculated in the stored procedure does not mean
>> they
>> are calculated when you manually add them to the field list. You put the
>> name same as the name of the field being returned and mark them as
>> database
>> field. If you name them appropriately and say they are are database
>> fields
>> it will work.
>> So, let's say you are in dataset2 which is called the stored procedure
>> with
>> a parameter value of 2. When you click the execute the data comes back.
>> Plus
>> you can see the name of the fields in the dataset (but not in the field
>> list). Add then appropriate field names to the field list.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
>> > Bruce, i apologize, this is going on and on. I attempt to add the
>> > fields
>> > in...just as they are in dataset1, except with new values, and it fails
>> > with
>> > this:
>> >
>> > 'The properties for the currently selected item are not valid. Please
>> > correct all errors before continuing.'
>> >
>> > Now, all of these values are calculated...Volume (sum of another
>> > value), #
>> > of Trades (count of another value), etc...but the same thing applies
>> > to
>> > dataset 1, and those fields are listed as database fields, not
>> > calculated
>> > fields. please can you tell me what the right way to do this is?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Ok, what is happening is that it is detecting the first resultset.
>> >> What
>> >> you
>> >> can do it is add the fields manually. In the field list add a new
>> >> field
>> >> and
>> >> name it correctly for what will be coming back. (Right mouse click in
>> >> the
>> >> field list).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
>> >> > Bruce, every time I refresh the fields, it pops the 1st three back
>> >> > in
>> >> > the
>> >> > list. They're the first three in the report, and i guess they're
>> >> > the
>> >> > only
>> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
>> >> > the
>> >> > same
>> >> > 3 fields are listed. i remove them per dataset, hit refresh, and
>> >> > the
>> >> > same
>> >> > 3
>> >> > come back.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> For each of your datasets make sure there is a field list.
>> >> >> Sometimes
>> >> >> you
>> >> >> have to click on the refresh fields button (to the right of the
>> >> >> ...).
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> >> >> > oh my goodness this is frustrating me....i did what you said,
>> >> >> > bruce,
>> >> >> > and
>> >> >> > it
>> >> >> > almost worked. the preview report shows me three values which
>> >> >> > correspond,
>> >> >> > i
>> >> >> > believe, to the only three fields in my report. see, they're all
>> >> >> > calculated
>> >> >> > fields. the output of the rpt is this:
>> >> >> >
>> >> >> > Build complete -- 0 errors, 0 warnings
>> >> >> > The data set 'DataSet3' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > The data set 'DataSet4' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > The data set 'DataSet2' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > Preview complete -- 0 errors, 3 warnings
>> >> >> >
>> >> >> > Now, I created the4 datasets, the parameter for each is simply 1,
>> >> >> > 2,
>> >> >> > 3
>> >> >> > and
>> >> >> > 4. The report, or the query, is not auto-generating my other
>> >> >> > fields
>> >> >> > as
>> >> >> > it
>> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
>> >> >> > fields
>> >> >> > that
>> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it
>> >> >> > that
>> >> >> > I
>> >> >> > just
>> >> >> > need to manually add in the other fields? Please do let me know
>> >> >> > what
>> >> >> > you
>> >> >> > think.
>> >> >> >
>> >> >> > and thank you, bruce, for helping me through this. i truly do
>> >> >> > appreciate
>> >> >> > it. i know i am close...and i got the other reports for my
>> >> >> > server
>> >> >> > jobs
>> >> >> > and
>> >> >> > one of the other company reports to work. it's just these
>> >> >> > multi-resultset
>> >> >> > reports are fighting me.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Query parameters and report parameters seem to be the same thing
>> >> >> >> but
>> >> >> >> they
>> >> >> >> are not. RS automatically creates a report parameter for each
>> >> >> >> query
>> >> >> >> parameter but instead you can map the query parameter to a
>> >> >> >> constant.
>> >> >> >> Click
>> >> >> >> on the ... for the dataset, go to the parameters tab. On the
>> >> >> >> right
>> >> >> >> you
>> >> >> >> will
>> >> >> >> see it mapping to the report parameter, click on that and select
>> >> >> >> expression.
>> >> >> >> In expression put = 1 (assuming it is an integert expression)
>> >> >> >> for
>> >> >> >> the
>> >> >> >> first
>> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> >> >> parameters
>> >> >> >> and then delete the report parameters created for you.
>> >> >> >>
>> >> >> >> You are very very close to the solution.
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> >> >> > last one for a while, bruce, i promise. i've got all 4
>> >> >> >> > datasets
>> >> >> >> > in
>> >> >> >> > there,
>> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
>> >> >> >> > getting
>> >> >> >> > my
>> >> >> >> > 'whole
>> >> >> >> > report' in four small subsets of data. how do i get this to
>> >> >> >> > happen
>> >> >> >> > on
>> >> >> >> > the
>> >> >> >> > report page automatically without needing user input?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Are you going against SQL Server?
>> >> >> >> >>
>> >> >> >> >> If so, then just select tored procedure for the command type
>> >> >> >> >> and
>> >> >> >> >> just
>> >> >> >> >> put
>> >> >> >> >> in
>> >> >> >> >> the name of the stored procedure. Do not put exec in from of
>> >> >> >> >> it
>> >> >> >> >> or
>> >> >> >> >> anything
>> >> >> >> >> else. It should detect the parameter and prompt you for it.
>> >> >> >> >> It
>> >> >> >> >> should
>> >> >> >> >> also
>> >> >> >> >> create a report parameter as well for you.
>> >> >> >> >>
>> >> >> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> >> >> continue
>> >> >> >> >> to
>> >> >> >> >> have problems create a new stored procedure just for testing
>> >> >> >> >> .
>> >> >> >> >>
>> >> >> >> >> create procedure dbo.testproc
>> >> >> >> >> @.PARAM1 int
>> >> >> >> >> as
>> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> >> >> return
>> >> >> >> >>
>> >> >> >> >> Get the above procedure to work for you so you know how to
>> >> >> >> >> call
>> >> >> >> >> a
>> >> >> >> >> stored
>> >> >> >> >> procedure they way I am telling you (do not use exec).
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs
>> >> >> >> >> > is
>> >> >> >> >> > not
>> >> >> >> >> > detecting
>> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
>> >> >> >> >> > and
>> >> >> >> >> > the
>> >> >> >> >> > proc
>> >> >> >> >> > name
>> >> >> >> >> > is in the query string. i assumed i would put the 1st
>> >> >> >> >> > parameter
>> >> >> >> >> > in
>> >> >> >> >> > on
>> >> >> >> >> > the
>> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3
>> >> >> >> >> > other
>> >> >> >> >> > datasets,
>> >> >> >> >> > so
>> >> >> >> >> > i
>> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
>> >> >> >> >> > it,
>> >> >> >> >> > it
>> >> >> >> >> > threw
>> >> >> >> >> > me a
>> >> >> >> >> > 'define query parameters box asking me to put the '1' in
>> >> >> >> >> > it.
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> this
>> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
>> >> >> >> >> >> the
>> >> >> >> >> >> parameters.
>> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
>> >> >> >> >> >> for
>> >> >> >> >> >> parameters)
>> >> >> >> >> >> then pick text as the command type and do this:
>> >> >> >> >> >> myproc ?
>> >> >> >> >> >>
>> >> >> >> >> >> Create multiple datasets and for each one you should call
>> >> >> >> >> >> the
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure for each one.
>> >> >> >> >> >>
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
>> >> >> >> >> >> > one
>> >> >> >> >> >> > parameters,
>> >> >> >> >> >> > it
>> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
>> >> >> >> >> >> > the
>> >> >> >> >> >> > results,
>> >> >> >> >> >> > works
>> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when
>> >> >> >> >> >> > I
>> >> >> >> >> >> > hit
>> >> >> >> >> >> > RUN
>> >> >> >> >> >> > in
>> >> >> >> >> >> > Data
>> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
>> >> >> >> >> >> > Encountered...The
>> >> >> >> >> >> > designer
>> >> >> >> >> >> > does
>> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but,
>> >> >> >> >> >> > i
>> >> >> >> >> >> > hit
>> >> >> >> >> >> > 'OK'
>> >> >> >> >> >> > and
>> >> >> >> >> >> > my
>> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
>> >> >> >> >> >> > however,
>> >> >> >> >> >> > I
>> >> >> >> >> >> > get
>> >> >> >> >> >> > no
>> >> >> >> >> >> > data/results at all.
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create
Services. All of which are based on stored procedures, none of which require
any parameters. Most if not all of the report is calculated. I am
struggling badly to get even the most basic of the fields in place w/the
correct expressions. The only one I actually got to accept the expression
was a Date field, this is the calculation:
=SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
It, too, fails to preview, indicating the value expression for the field
contains an error. Again, all of the other report items are calculated
fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using the
report designer/report wizard to 'do it for me' only returns Date and a
couple fields that are not even in my resultset. like one of my values in
the report is 'Total Trades'...one of the fields listed as available is
'ID__Total__'
Further, in VS I've got the report open and am on the data tab, i hit the
Run option, I receive this error: An error occurred while retrieving the
parameters in the query. Could not locate entry in sysdatabases for database
'EXEC databasename'. No entry found with that name. Make sure that the name
is entered correctly.'
Clearly I am doing something very wrong with the stored procedure
definition. Like I said, all of these reports are based on procedures, can
anybody give me some suggestion/direction on the right way to call the procs?
They run w/out parameters...EXEC databasename.dbo.proc that's it.
Please advise.
-- LynnPick the command type as stored procedure and then just enter the name of
the stored procedure. When you click on the ! you should get back the data
and the fields. If you do not get the field list populated then click on the
refresh fields button (to the right of the ..., it looks like the refresh
button for IE).
Note that RS only works with the first resultset returned. It cannot handle
mutliple resultsets.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> Hi. I have a need to create a number of different reports via Reporting
> Services. All of which are based on stored procedures, none of which
> require
> any parameters. Most if not all of the report is calculated. I am
> struggling badly to get even the most basic of the fields in place w/the
> correct expressions. The only one I actually got to accept the expression
> was a Date field, this is the calculation:
> =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> It, too, fails to preview, indicating the value expression for the field
> contains an error. Again, all of the other report items are calculated
> fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using
> the
> report designer/report wizard to 'do it for me' only returns Date and a
> couple fields that are not even in my resultset. like one of my values in
> the report is 'Total Trades'...one of the fields listed as available is
> 'ID__Total__'
> Further, in VS I've got the report open and am on the data tab, i hit the
> Run option, I receive this error: An error occurred while retrieving the
> parameters in the query. Could not locate entry in sysdatabases for
> database
> 'EXEC databasename'. No entry found with that name. Make sure that the
> name
> is entered correctly.'
> Clearly I am doing something very wrong with the stored procedure
> definition. Like I said, all of these reports are based on procedures,
> can
> anybody give me some suggestion/direction on the right way to call the
> procs?
> They run w/out parameters...EXEC databasename.dbo.proc that's it.
> Please advise.
>
> -- Lynn|||oh, bruce, that is great. I can't believe it was as simple as that. one
remaining problem, though. one of my reports is like this:
Date Total Trades Symbols Traded Total $
-- -- -- --
02/07/2006 333,333 333 33,333,333,333.33
#Stocks Volume Total $
-- -- --
333,333 33,333,333 3,333,333,333.33
EndPoint Liquidity #Trades Volume Total $
-- -- -- -- --
AAAA Add 114,729 21,797,575 583,102,631.33
AAAA Opening 1 27
3,412.53
AAAA Remove 30,836 8,330,843 444,521,928.10
AAAA Route 41 4,543
103,291.31
BBBB Add 26,997 9,940,201 178,600,674.78
BBBB Opening 8,089 1,448,143 44,276,419.41
BBBB Remove 3,406 1,719,403 40,267,318.25
CCCC Add 83,781 22,443,732 746,570,071.43
CCCC Remove 35,756 12,250,359 483,329,796.97
CCCC Route 1,088 244,697 6,655,913.26
DDDD Route 2 62,500 2,539,375.00
DDDD Add 2,354 1,262,589 19,136,233.44
DDDD Remove 258 195,019 6,227,451.69
I only receive the top line in the resultset:
Date Total Trades Symbols Traded Total $
-- -- -- --
02/07/2006 333,333 333 33,333,333,333.33
I assume this is what you mean when you say it will only handle the 1st
resultset. All of my reports have multiple 'chunks' in the body. Do you
have any idea how I can achieve this report via reporting svcs?
Unfortunately, this is very important. Please do advise.
--Lynn
"Bruce L-C [MVP]" wrote:
> Pick the command type as stored procedure and then just enter the name of
> the stored procedure. When you click on the ! you should get back the data
> and the fields. If you do not get the field list populated then click on the
> refresh fields button (to the right of the ..., it looks like the refresh
> button for IE).
> Note that RS only works with the first resultset returned. It cannot handle
> mutliple resultsets.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> > Hi. I have a need to create a number of different reports via Reporting
> > Services. All of which are based on stored procedures, none of which
> > require
> > any parameters. Most if not all of the report is calculated. I am
> > struggling badly to get even the most basic of the fields in place w/the
> > correct expressions. The only one I actually got to accept the expression
> > was a Date field, this is the calculation:
> >
> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >
> > It, too, fails to preview, indicating the value expression for the field
> > contains an error. Again, all of the other report items are calculated
> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc. Using
> > the
> > report designer/report wizard to 'do it for me' only returns Date and a
> > couple fields that are not even in my resultset. like one of my values in
> > the report is 'Total Trades'...one of the fields listed as available is
> > 'ID__Total__'
> >
> > Further, in VS I've got the report open and am on the data tab, i hit the
> > Run option, I receive this error: An error occurred while retrieving the
> > parameters in the query. Could not locate entry in sysdatabases for
> > database
> > 'EXEC databasename'. No entry found with that name. Make sure that the
> > name
> > is entered correctly.'
> >
> > Clearly I am doing something very wrong with the stored procedure
> > definition. Like I said, all of these reports are based on procedures,
> > can
> > anybody give me some suggestion/direction on the right way to call the
> > procs?
> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
> > Please advise.
> >
> >
> > -- Lynn
>
>|||This is three resultsets. RS does not have the ability to handle that. There
is no work around from RS side. You could create another stored procedure
that calls this one and have it return just one of the resultsets.
RS can deal with multiple datasets quite well, but each stored procedure
call can only return one.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> oh, bruce, that is great. I can't believe it was as simple as that. one
> remaining problem, though. one of my reports is like this:
> Date Total Trades Symbols Traded Total $
> -- -- -- --
> 02/07/2006 333,333 333 33,333,333,333.33
> #Stocks Volume Total $
> -- -- --
> 333,333 33,333,333 3,333,333,333.33
> EndPoint Liquidity #Trades Volume Total $
> -- -- -- -- --
> AAAA Add 114,729 21,797,575
> 583,102,631.33
> AAAA Opening 1 27
> 3,412.53
> AAAA Remove 30,836 8,330,843
> 444,521,928.10
> AAAA Route 41 4,543
> 103,291.31
> BBBB Add 26,997 9,940,201
> 178,600,674.78
> BBBB Opening 8,089 1,448,143
> 44,276,419.41
> BBBB Remove 3,406 1,719,403
> 40,267,318.25
> CCCC Add 83,781 22,443,732
> 746,570,071.43
> CCCC Remove 35,756 12,250,359
> 483,329,796.97
> CCCC Route 1,088 244,697
> 6,655,913.26
> DDDD Route 2 62,500
> 2,539,375.00
> DDDD Add 2,354 1,262,589
> 19,136,233.44
> DDDD Remove 258 195,019
> 6,227,451.69
> I only receive the top line in the resultset:
> Date Total Trades Symbols Traded Total $
> -- -- -- --
> 02/07/2006 333,333 333 33,333,333,333.33
> I assume this is what you mean when you say it will only handle the 1st
> resultset. All of my reports have multiple 'chunks' in the body. Do you
> have any idea how I can achieve this report via reporting svcs?
> Unfortunately, this is very important. Please do advise.
> --Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Pick the command type as stored procedure and then just enter the name of
>> the stored procedure. When you click on the ! you should get back the
>> data
>> and the fields. If you do not get the field list populated then click on
>> the
>> refresh fields button (to the right of the ..., it looks like the refresh
>> button for IE).
>> Note that RS only works with the first resultset returned. It cannot
>> handle
>> mutliple resultsets.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> > Hi. I have a need to create a number of different reports via
>> > Reporting
>> > Services. All of which are based on stored procedures, none of which
>> > require
>> > any parameters. Most if not all of the report is calculated. I am
>> > struggling badly to get even the most basic of the fields in place
>> > w/the
>> > correct expressions. The only one I actually got to accept the
>> > expression
>> > was a Date field, this is the calculation:
>> >
>> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >
>> > It, too, fails to preview, indicating the value expression for the
>> > field
>> > contains an error. Again, all of the other report items are calculated
>> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
>> > Using
>> > the
>> > report designer/report wizard to 'do it for me' only returns Date and a
>> > couple fields that are not even in my resultset. like one of my values
>> > in
>> > the report is 'Total Trades'...one of the fields listed as available
>> > is
>> > 'ID__Total__'
>> >
>> > Further, in VS I've got the report open and am on the data tab, i hit
>> > the
>> > Run option, I receive this error: An error occurred while retrieving
>> > the
>> > parameters in the query. Could not locate entry in sysdatabases for
>> > database
>> > 'EXEC databasename'. No entry found with that name. Make sure that the
>> > name
>> > is entered correctly.'
>> >
>> > Clearly I am doing something very wrong with the stored procedure
>> > definition. Like I said, all of these reports are based on procedures,
>> > can
>> > anybody give me some suggestion/direction on the right way to call the
>> > procs?
>> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
>> > Please advise.
>> >
>> >
>> > -- Lynn
>>|||Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
the second, possibly third procedure?
-- Lynn
"Bruce L-C [MVP]" wrote:
> This is three resultsets. RS does not have the ability to handle that. There
> is no work around from RS side. You could create another stored procedure
> that calls this one and have it return just one of the resultsets.
> RS can deal with multiple datasets quite well, but each stored procedure
> call can only return one.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> > oh, bruce, that is great. I can't believe it was as simple as that. one
> > remaining problem, though. one of my reports is like this:
> >
> > Date Total Trades Symbols Traded Total $
> > -- -- -- --
> > 02/07/2006 333,333 333 33,333,333,333.33
> >
> > #Stocks Volume Total $
> > -- -- --
> > 333,333 33,333,333 3,333,333,333.33
> >
> > EndPoint Liquidity #Trades Volume Total $
> > -- -- -- -- --
> > AAAA Add 114,729 21,797,575
> > 583,102,631.33
> > AAAA Opening 1 27
> > 3,412.53
> > AAAA Remove 30,836 8,330,843
> > 444,521,928.10
> > AAAA Route 41 4,543
> > 103,291.31
> > BBBB Add 26,997 9,940,201
> > 178,600,674.78
> > BBBB Opening 8,089 1,448,143
> > 44,276,419.41
> > BBBB Remove 3,406 1,719,403
> > 40,267,318.25
> > CCCC Add 83,781 22,443,732
> > 746,570,071.43
> > CCCC Remove 35,756 12,250,359
> > 483,329,796.97
> > CCCC Route 1,088 244,697
> > 6,655,913.26
> > DDDD Route 2 62,500
> > 2,539,375.00
> > DDDD Add 2,354 1,262,589
> > 19,136,233.44
> > DDDD Remove 258 195,019
> > 6,227,451.69
> >
> > I only receive the top line in the resultset:
> >
> > Date Total Trades Symbols Traded Total $
> > -- -- -- --
> > 02/07/2006 333,333 333 33,333,333,333.33
> >
> > I assume this is what you mean when you say it will only handle the 1st
> > resultset. All of my reports have multiple 'chunks' in the body. Do you
> > have any idea how I can achieve this report via reporting svcs?
> > Unfortunately, this is very important. Please do advise.
> >
> > --Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Pick the command type as stored procedure and then just enter the name of
> >> the stored procedure. When you click on the ! you should get back the
> >> data
> >> and the fields. If you do not get the field list populated then click on
> >> the
> >> refresh fields button (to the right of the ..., it looks like the refresh
> >> button for IE).
> >>
> >> Note that RS only works with the first resultset returned. It cannot
> >> handle
> >> mutliple resultsets.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> > Hi. I have a need to create a number of different reports via
> >> > Reporting
> >> > Services. All of which are based on stored procedures, none of which
> >> > require
> >> > any parameters. Most if not all of the report is calculated. I am
> >> > struggling badly to get even the most basic of the fields in place
> >> > w/the
> >> > correct expressions. The only one I actually got to accept the
> >> > expression
> >> > was a Date field, this is the calculation:
> >> >
> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >
> >> > It, too, fails to preview, indicating the value expression for the
> >> > field
> >> > contains an error. Again, all of the other report items are calculated
> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> > Using
> >> > the
> >> > report designer/report wizard to 'do it for me' only returns Date and a
> >> > couple fields that are not even in my resultset. like one of my values
> >> > in
> >> > the report is 'Total Trades'...one of the fields listed as available
> >> > is
> >> > 'ID__Total__'
> >> >
> >> > Further, in VS I've got the report open and am on the data tab, i hit
> >> > the
> >> > Run option, I receive this error: An error occurred while retrieving
> >> > the
> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> > database
> >> > 'EXEC databasename'. No entry found with that name. Make sure that the
> >> > name
> >> > is entered correctly.'
> >> >
> >> > Clearly I am doing something very wrong with the stored procedure
> >> > definition. Like I said, all of these reports are based on procedures,
> >> > can
> >> > anybody give me some suggestion/direction on the right way to call the
> >> > procs?
> >> > They run w/out parameters...EXEC databasename.dbo.proc that's it.
> >> > Please advise.
> >> >
> >> >
> >> > -- Lynn
> >>
> >>
> >>
>
>|||Configure your existing stored procedure to accept a parameter (you can make
it optional so that it doesn't break existing code).
Then call it three times in RS with a static value and create three
datasets.
For instance dataset1
yourproc 1
Dataset2
yourproc 2
etc.
Then in your stored procedure return the appropriate resultset based on the
parameter.
Downside is that your sp is being run three times.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> the second, possibly third procedure?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> This is three resultsets. RS does not have the ability to handle that.
>> There
>> is no work around from RS side. You could create another stored procedure
>> that calls this one and have it return just one of the resultsets.
>> RS can deal with multiple datasets quite well, but each stored procedure
>> call can only return one.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> > oh, bruce, that is great. I can't believe it was as simple as that.
>> > one
>> > remaining problem, though. one of my reports is like this:
>> >
>> > Date Total Trades Symbols Traded Total $
>> > -- -- -- --
>> > 02/07/2006 333,333 333 33,333,333,333.33
>> >
>> > #Stocks Volume Total $
>> > -- -- --
>> > 333,333 33,333,333 3,333,333,333.33
>> >
>> > EndPoint Liquidity #Trades Volume Total $
>> > -- -- -- -- --
>> > AAAA Add 114,729 21,797,575
>> > 583,102,631.33
>> > AAAA Opening 1 27
>> > 3,412.53
>> > AAAA Remove 30,836 8,330,843
>> > 444,521,928.10
>> > AAAA Route 41 4,543
>> > 103,291.31
>> > BBBB Add 26,997 9,940,201
>> > 178,600,674.78
>> > BBBB Opening 8,089 1,448,143
>> > 44,276,419.41
>> > BBBB Remove 3,406 1,719,403
>> > 40,267,318.25
>> > CCCC Add 83,781 22,443,732
>> > 746,570,071.43
>> > CCCC Remove 35,756 12,250,359
>> > 483,329,796.97
>> > CCCC Route 1,088 244,697
>> > 6,655,913.26
>> > DDDD Route 2 62,500
>> > 2,539,375.00
>> > DDDD Add 2,354 1,262,589
>> > 19,136,233.44
>> > DDDD Remove 258 195,019
>> > 6,227,451.69
>> >
>> > I only receive the top line in the resultset:
>> >
>> > Date Total Trades Symbols Traded Total $
>> > -- -- -- --
>> > 02/07/2006 333,333 333 33,333,333,333.33
>> >
>> > I assume this is what you mean when you say it will only handle the 1st
>> > resultset. All of my reports have multiple 'chunks' in the body. Do
>> > you
>> > have any idea how I can achieve this report via reporting svcs?
>> > Unfortunately, this is very important. Please do advise.
>> >
>> > --Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Pick the command type as stored procedure and then just enter the name
>> >> of
>> >> the stored procedure. When you click on the ! you should get back the
>> >> data
>> >> and the fields. If you do not get the field list populated then click
>> >> on
>> >> the
>> >> refresh fields button (to the right of the ..., it looks like the
>> >> refresh
>> >> button for IE).
>> >>
>> >> Note that RS only works with the first resultset returned. It cannot
>> >> handle
>> >> mutliple resultsets.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> > Hi. I have a need to create a number of different reports via
>> >> > Reporting
>> >> > Services. All of which are based on stored procedures, none of
>> >> > which
>> >> > require
>> >> > any parameters. Most if not all of the report is calculated. I am
>> >> > struggling badly to get even the most basic of the fields in place
>> >> > w/the
>> >> > correct expressions. The only one I actually got to accept the
>> >> > expression
>> >> > was a Date field, this is the calculation:
>> >> >
>> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >
>> >> > It, too, fails to preview, indicating the value expression for the
>> >> > field
>> >> > contains an error. Again, all of the other report items are
>> >> > calculated
>> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
>> >> > Using
>> >> > the
>> >> > report designer/report wizard to 'do it for me' only returns Date
>> >> > and a
>> >> > couple fields that are not even in my resultset. like one of my
>> >> > values
>> >> > in
>> >> > the report is 'Total Trades'...one of the fields listed as
>> >> > available
>> >> > is
>> >> > 'ID__Total__'
>> >> >
>> >> > Further, in VS I've got the report open and am on the data tab, i
>> >> > hit
>> >> > the
>> >> > Run option, I receive this error: An error occurred while
>> >> > retrieving
>> >> > the
>> >> > parameters in the query. Could not locate entry in sysdatabases for
>> >> > database
>> >> > 'EXEC databasename'. No entry found with that name. Make sure that
>> >> > the
>> >> > name
>> >> > is entered correctly.'
>> >> >
>> >> > Clearly I am doing something very wrong with the stored procedure
>> >> > definition. Like I said, all of these reports are based on
>> >> > procedures,
>> >> > can
>> >> > anybody give me some suggestion/direction on the right way to call
>> >> > the
>> >> > procs?
>> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
>> >> > it.
>> >> > Please advise.
>> >> >
>> >> >
>> >> > -- Lynn
>> >>
>> >>
>> >>
>>|||well, bruce, i'm still not sure i know what to do w/these parameters...how
will i get one parameter to do one resultset and get the other resultsets
w/parameters 2 and 3? but, i will see if i can walk through this.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Hi again, Bruce. Is there any way you can give me an example of how to
change my proc to accept the 3 parameters? I know how to pass parameters to
a procedure, I just don't understand how I can do it to make my procedure gen
three different resultsets.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Bruce, or somebody else, might you give me an example of how to give the proc
3 parameters, producing three resultsets in a way that RS will display them?
Or, am I giving it three parameters and calling it three times? If so, how
would i call the 3 procs in RS?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Configure your existing stored procedure to accept a parameter (you can make
> it optional so that it doesn't break existing code).
> Then call it three times in RS with a static value and create three
> datasets.
> For instance dataset1
> yourproc 1
> Dataset2
> yourproc 2
> etc.
> Then in your stored procedure return the appropriate resultset based on the
> parameter.
> Downside is that your sp is being run three times.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> > Bruce, I'm not sure I follow. Can you elaborate a little more, please, on
> > the second, possibly third procedure?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> This is three resultsets. RS does not have the ability to handle that.
> >> There
> >> is no work around from RS side. You could create another stored procedure
> >> that calls this one and have it return just one of the resultsets.
> >>
> >> RS can deal with multiple datasets quite well, but each stored procedure
> >> call can only return one.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> > one
> >> > remaining problem, though. one of my reports is like this:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > #Stocks Volume Total $
> >> > -- -- --
> >> > 333,333 33,333,333 3,333,333,333.33
> >> >
> >> > EndPoint Liquidity #Trades Volume Total $
> >> > -- -- -- -- --
> >> > AAAA Add 114,729 21,797,575
> >> > 583,102,631.33
> >> > AAAA Opening 1 27
> >> > 3,412.53
> >> > AAAA Remove 30,836 8,330,843
> >> > 444,521,928.10
> >> > AAAA Route 41 4,543
> >> > 103,291.31
> >> > BBBB Add 26,997 9,940,201
> >> > 178,600,674.78
> >> > BBBB Opening 8,089 1,448,143
> >> > 44,276,419.41
> >> > BBBB Remove 3,406 1,719,403
> >> > 40,267,318.25
> >> > CCCC Add 83,781 22,443,732
> >> > 746,570,071.43
> >> > CCCC Remove 35,756 12,250,359
> >> > 483,329,796.97
> >> > CCCC Route 1,088 244,697
> >> > 6,655,913.26
> >> > DDDD Route 2 62,500
> >> > 2,539,375.00
> >> > DDDD Add 2,354 1,262,589
> >> > 19,136,233.44
> >> > DDDD Remove 258 195,019
> >> > 6,227,451.69
> >> >
> >> > I only receive the top line in the resultset:
> >> >
> >> > Date Total Trades Symbols Traded Total $
> >> > -- -- -- --
> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >
> >> > I assume this is what you mean when you say it will only handle the 1st
> >> > resultset. All of my reports have multiple 'chunks' in the body. Do
> >> > you
> >> > have any idea how I can achieve this report via reporting svcs?
> >> > Unfortunately, this is very important. Please do advise.
> >> >
> >> > --Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Pick the command type as stored procedure and then just enter the name
> >> >> of
> >> >> the stored procedure. When you click on the ! you should get back the
> >> >> data
> >> >> and the fields. If you do not get the field list populated then click
> >> >> on
> >> >> the
> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> refresh
> >> >> button for IE).
> >> >>
> >> >> Note that RS only works with the first resultset returned. It cannot
> >> >> handle
> >> >> mutliple resultsets.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> > Hi. I have a need to create a number of different reports via
> >> >> > Reporting
> >> >> > Services. All of which are based on stored procedures, none of
> >> >> > which
> >> >> > require
> >> >> > any parameters. Most if not all of the report is calculated. I am
> >> >> > struggling badly to get even the most basic of the fields in place
> >> >> > w/the
> >> >> > correct expressions. The only one I actually got to accept the
> >> >> > expression
> >> >> > was a Date field, this is the calculation:
> >> >> >
> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >
> >> >> > It, too, fails to preview, indicating the value expression for the
> >> >> > field
> >> >> > contains an error. Again, all of the other report items are
> >> >> > calculated
> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs, etc.
> >> >> > Using
> >> >> > the
> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> > and a
> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> > values
> >> >> > in
> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> > available
> >> >> > is
> >> >> > 'ID__Total__'
> >> >> >
> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> > hit
> >> >> > the
> >> >> > Run option, I receive this error: An error occurred while
> >> >> > retrieving
> >> >> > the
> >> >> > parameters in the query. Could not locate entry in sysdatabases for
> >> >> > database
> >> >> > 'EXEC databasename'. No entry found with that name. Make sure that
> >> >> > the
> >> >> > name
> >> >> > is entered correctly.'
> >> >> >
> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> > definition. Like I said, all of these reports are based on
> >> >> > procedures,
> >> >> > can
> >> >> > anybody give me some suggestion/direction on the right way to call
> >> >> > the
> >> >> > procs?
> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> > it.
> >> >> > Please advise.
> >> >> >
> >> >> >
> >> >> > -- Lynn
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Yes, you are calling it three times. In RS you create three datasets. Go to
the dataset tab and there is a combo box with the name of the dataset, you
can click on that and there is a an option for a new.
In your stored procedure
if @.WHICHRESULTSET = 1
begin
--return the first resultset here
end
etc
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> Bruce, or somebody else, might you give me an example of how to give the
> proc
> 3 parameters, producing three resultsets in a way that RS will display
> them?
> Or, am I giving it three parameters and calling it three times? If so,
> how
> would i call the 3 procs in RS?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Configure your existing stored procedure to accept a parameter (you can
>> make
>> it optional so that it doesn't break existing code).
>> Then call it three times in RS with a static value and create three
>> datasets.
>> For instance dataset1
>> yourproc 1
>> Dataset2
>> yourproc 2
>> etc.
>> Then in your stored procedure return the appropriate resultset based on
>> the
>> parameter.
>> Downside is that your sp is being run three times.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
>> > on
>> > the second, possibly third procedure?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> This is three resultsets. RS does not have the ability to handle that.
>> >> There
>> >> is no work around from RS side. You could create another stored
>> >> procedure
>> >> that calls this one and have it return just one of the resultsets.
>> >>
>> >> RS can deal with multiple datasets quite well, but each stored
>> >> procedure
>> >> call can only return one.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> > oh, bruce, that is great. I can't believe it was as simple as that.
>> >> > one
>> >> > remaining problem, though. one of my reports is like this:
>> >> >
>> >> > Date Total Trades Symbols Traded Total $
>> >> > -- -- -- --
>> >> > 02/07/2006 333,333 333 33,333,333,333.33
>> >> >
>> >> > #Stocks Volume Total $
>> >> > -- -- --
>> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >
>> >> > EndPoint Liquidity #Trades Volume Total $
>> >> > -- -- -- -- --
>> >> > AAAA Add 114,729 21,797,575
>> >> > 583,102,631.33
>> >> > AAAA Opening 1 27
>> >> > 3,412.53
>> >> > AAAA Remove 30,836 8,330,843
>> >> > 444,521,928.10
>> >> > AAAA Route 41 4,543
>> >> > 103,291.31
>> >> > BBBB Add 26,997 9,940,201
>> >> > 178,600,674.78
>> >> > BBBB Opening 8,089 1,448,143
>> >> > 44,276,419.41
>> >> > BBBB Remove 3,406 1,719,403
>> >> > 40,267,318.25
>> >> > CCCC Add 83,781 22,443,732
>> >> > 746,570,071.43
>> >> > CCCC Remove 35,756 12,250,359
>> >> > 483,329,796.97
>> >> > CCCC Route 1,088 244,697
>> >> > 6,655,913.26
>> >> > DDDD Route 2 62,500
>> >> > 2,539,375.00
>> >> > DDDD Add 2,354 1,262,589
>> >> > 19,136,233.44
>> >> > DDDD Remove 258 195,019
>> >> > 6,227,451.69
>> >> >
>> >> > I only receive the top line in the resultset:
>> >> >
>> >> > Date Total Trades Symbols Traded Total $
>> >> > -- -- -- --
>> >> > 02/07/2006 333,333 333 33,333,333,333.33
>> >> >
>> >> > I assume this is what you mean when you say it will only handle the
>> >> > 1st
>> >> > resultset. All of my reports have multiple 'chunks' in the body.
>> >> > Do
>> >> > you
>> >> > have any idea how I can achieve this report via reporting svcs?
>> >> > Unfortunately, this is very important. Please do advise.
>> >> >
>> >> > --Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Pick the command type as stored procedure and then just enter the
>> >> >> name
>> >> >> of
>> >> >> the stored procedure. When you click on the ! you should get back
>> >> >> the
>> >> >> data
>> >> >> and the fields. If you do not get the field list populated then
>> >> >> click
>> >> >> on
>> >> >> the
>> >> >> refresh fields button (to the right of the ..., it looks like the
>> >> >> refresh
>> >> >> button for IE).
>> >> >>
>> >> >> Note that RS only works with the first resultset returned. It
>> >> >> cannot
>> >> >> handle
>> >> >> mutliple resultsets.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> > Hi. I have a need to create a number of different reports via
>> >> >> > Reporting
>> >> >> > Services. All of which are based on stored procedures, none of
>> >> >> > which
>> >> >> > require
>> >> >> > any parameters. Most if not all of the report is calculated. I
>> >> >> > am
>> >> >> > struggling badly to get even the most basic of the fields in
>> >> >> > place
>> >> >> > w/the
>> >> >> > correct expressions. The only one I actually got to accept the
>> >> >> > expression
>> >> >> > was a Date field, this is the calculation:
>> >> >> >
>> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >
>> >> >> > It, too, fails to preview, indicating the value expression for
>> >> >> > the
>> >> >> > field
>> >> >> > contains an error. Again, all of the other report items are
>> >> >> > calculated
>> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
>> >> >> > etc.
>> >> >> > Using
>> >> >> > the
>> >> >> > report designer/report wizard to 'do it for me' only returns Date
>> >> >> > and a
>> >> >> > couple fields that are not even in my resultset. like one of my
>> >> >> > values
>> >> >> > in
>> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> > available
>> >> >> > is
>> >> >> > 'ID__Total__'
>> >> >> >
>> >> >> > Further, in VS I've got the report open and am on the data tab, i
>> >> >> > hit
>> >> >> > the
>> >> >> > Run option, I receive this error: An error occurred while
>> >> >> > retrieving
>> >> >> > the
>> >> >> > parameters in the query. Could not locate entry in sysdatabases
>> >> >> > for
>> >> >> > database
>> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
>> >> >> > that
>> >> >> > the
>> >> >> > name
>> >> >> > is entered correctly.'
>> >> >> >
>> >> >> > Clearly I am doing something very wrong with the stored procedure
>> >> >> > definition. Like I said, all of these reports are based on
>> >> >> > procedures,
>> >> >> > can
>> >> >> > anybody give me some suggestion/direction on the right way to
>> >> >> > call
>> >> >> > the
>> >> >> > procs?
>> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
>> >> >> > it.
>> >> >> > Please advise.
>> >> >> >
>> >> >> >
>> >> >> > -- Lynn
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||bruce, i've added the parameters to the proc, now if you fire procname 1,
procname 2, procname 3 or procname 4, it returns each of the resultsets to me
in query analyzer.
in Rs i've got one dataset running this successfully:
EXEC db.dbo.procname 1
results are given, everthing looks good.
but, i go add dataset 2, it seems to do so successfully, but now the data is
not shown. not even the data from the first dataset. it just gives my
header, no results. i don't know how to fix this. should i be using
subreports, should i be using one proce multiple times w/multiple datasets,
i'm just not sure.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Yes, you are calling it three times. In RS you create three datasets. Go to
> the dataset tab and there is a combo box with the name of the dataset, you
> can click on that and there is a an option for a new.
> In your stored procedure
> if @.WHICHRESULTSET = 1
> begin
> --return the first resultset here
> end
> etc
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> > Bruce, or somebody else, might you give me an example of how to give the
> > proc
> > 3 parameters, producing three resultsets in a way that RS will display
> > them?
> > Or, am I giving it three parameters and calling it three times? If so,
> > how
> > would i call the 3 procs in RS?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Configure your existing stored procedure to accept a parameter (you can
> >> make
> >> it optional so that it doesn't break existing code).
> >>
> >> Then call it three times in RS with a static value and create three
> >> datasets.
> >> For instance dataset1
> >> yourproc 1
> >>
> >> Dataset2
> >> yourproc 2
> >>
> >> etc.
> >>
> >> Then in your stored procedure return the appropriate resultset based on
> >> the
> >> parameter.
> >>
> >> Downside is that your sp is being run three times.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
> >> > on
> >> > the second, possibly third procedure?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> This is three resultsets. RS does not have the ability to handle that.
> >> >> There
> >> >> is no work around from RS side. You could create another stored
> >> >> procedure
> >> >> that calls this one and have it return just one of the resultsets.
> >> >>
> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> procedure
> >> >> call can only return one.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> >> > one
> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > #Stocks Volume Total $
> >> >> > -- -- --
> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >
> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> > -- -- -- -- --
> >> >> > AAAA Add 114,729 21,797,575
> >> >> > 583,102,631.33
> >> >> > AAAA Opening 1 27
> >> >> > 3,412.53
> >> >> > AAAA Remove 30,836 8,330,843
> >> >> > 444,521,928.10
> >> >> > AAAA Route 41 4,543
> >> >> > 103,291.31
> >> >> > BBBB Add 26,997 9,940,201
> >> >> > 178,600,674.78
> >> >> > BBBB Opening 8,089 1,448,143
> >> >> > 44,276,419.41
> >> >> > BBBB Remove 3,406 1,719,403
> >> >> > 40,267,318.25
> >> >> > CCCC Add 83,781 22,443,732
> >> >> > 746,570,071.43
> >> >> > CCCC Remove 35,756 12,250,359
> >> >> > 483,329,796.97
> >> >> > CCCC Route 1,088 244,697
> >> >> > 6,655,913.26
> >> >> > DDDD Route 2 62,500
> >> >> > 2,539,375.00
> >> >> > DDDD Add 2,354 1,262,589
> >> >> > 19,136,233.44
> >> >> > DDDD Remove 258 195,019
> >> >> > 6,227,451.69
> >> >> >
> >> >> > I only receive the top line in the resultset:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > I assume this is what you mean when you say it will only handle the
> >> >> > 1st
> >> >> > resultset. All of my reports have multiple 'chunks' in the body.
> >> >> > Do
> >> >> > you
> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >
> >> >> > --Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Pick the command type as stored procedure and then just enter the
> >> >> >> name
> >> >> >> of
> >> >> >> the stored procedure. When you click on the ! you should get back
> >> >> >> the
> >> >> >> data
> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> click
> >> >> >> on
> >> >> >> the
> >> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> >> refresh
> >> >> >> button for IE).
> >> >> >>
> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> cannot
> >> >> >> handle
> >> >> >> mutliple resultsets.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> > Reporting
> >> >> >> > Services. All of which are based on stored procedures, none of
> >> >> >> > which
> >> >> >> > require
> >> >> >> > any parameters. Most if not all of the report is calculated. I
> >> >> >> > am
> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> > place
> >> >> >> > w/the
> >> >> >> > correct expressions. The only one I actually got to accept the
> >> >> >> > expression
> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >
> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >
> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> > the
> >> >> >> > field
> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> > calculated
> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> > etc.
> >> >> >> > Using
> >> >> >> > the
> >> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> >> > and a
> >> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> >> > values
> >> >> >> > in
> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> > available
> >> >> >> > is
> >> >> >> > 'ID__Total__'
> >> >> >> >
> >> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> >> > hit
> >> >> >> > the
> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> > retrieving
> >> >> >> > the
> >> >> >> > parameters in the query. Could not locate entry in sysdatabases
> >> >> >> > for
> >> >> >> > database
> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> > that
> >> >> >> > the
> >> >> >> > name
> >> >> >> > is entered correctly.'
> >> >> >> >
> >> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> > procedures,
> >> >> >> > can
> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> > call
> >> >> >> > the
> >> >> >> > procs?
> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> >> > it.
> >> >> >> > Please advise.
> >> >> >> >
> >> >> >> >
> >> >> >> > -- Lynn
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||And, if I blow away the 2nd dataset and just give my 1st one parameters, it
almost works. EXEC db.dbo.procname 1 for chunk one of the results, works
just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
tab it returns an error: SQL Syntax Errors Encountered...The designer does
not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
results are still returned to me. On 'Preview' tab, however, I get no
data/results at all.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Yes, you are calling it three times. In RS you create three datasets. Go to
> the dataset tab and there is a combo box with the name of the dataset, you
> can click on that and there is a an option for a new.
> In your stored procedure
> if @.WHICHRESULTSET = 1
> begin
> --return the first resultset here
> end
> etc
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> > Bruce, or somebody else, might you give me an example of how to give the
> > proc
> > 3 parameters, producing three resultsets in a way that RS will display
> > them?
> > Or, am I giving it three parameters and calling it three times? If so,
> > how
> > would i call the 3 procs in RS?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Configure your existing stored procedure to accept a parameter (you can
> >> make
> >> it optional so that it doesn't break existing code).
> >>
> >> Then call it three times in RS with a static value and create three
> >> datasets.
> >> For instance dataset1
> >> yourproc 1
> >>
> >> Dataset2
> >> yourproc 2
> >>
> >> etc.
> >>
> >> Then in your stored procedure return the appropriate resultset based on
> >> the
> >> parameter.
> >>
> >> Downside is that your sp is being run three times.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> > Bruce, I'm not sure I follow. Can you elaborate a little more, please,
> >> > on
> >> > the second, possibly third procedure?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> This is three resultsets. RS does not have the ability to handle that.
> >> >> There
> >> >> is no work around from RS side. You could create another stored
> >> >> procedure
> >> >> that calls this one and have it return just one of the resultsets.
> >> >>
> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> procedure
> >> >> call can only return one.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> > oh, bruce, that is great. I can't believe it was as simple as that.
> >> >> > one
> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > #Stocks Volume Total $
> >> >> > -- -- --
> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >
> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> > -- -- -- -- --
> >> >> > AAAA Add 114,729 21,797,575
> >> >> > 583,102,631.33
> >> >> > AAAA Opening 1 27
> >> >> > 3,412.53
> >> >> > AAAA Remove 30,836 8,330,843
> >> >> > 444,521,928.10
> >> >> > AAAA Route 41 4,543
> >> >> > 103,291.31
> >> >> > BBBB Add 26,997 9,940,201
> >> >> > 178,600,674.78
> >> >> > BBBB Opening 8,089 1,448,143
> >> >> > 44,276,419.41
> >> >> > BBBB Remove 3,406 1,719,403
> >> >> > 40,267,318.25
> >> >> > CCCC Add 83,781 22,443,732
> >> >> > 746,570,071.43
> >> >> > CCCC Remove 35,756 12,250,359
> >> >> > 483,329,796.97
> >> >> > CCCC Route 1,088 244,697
> >> >> > 6,655,913.26
> >> >> > DDDD Route 2 62,500
> >> >> > 2,539,375.00
> >> >> > DDDD Add 2,354 1,262,589
> >> >> > 19,136,233.44
> >> >> > DDDD Remove 258 195,019
> >> >> > 6,227,451.69
> >> >> >
> >> >> > I only receive the top line in the resultset:
> >> >> >
> >> >> > Date Total Trades Symbols Traded Total $
> >> >> > -- -- -- --
> >> >> > 02/07/2006 333,333 333 33,333,333,333.33
> >> >> >
> >> >> > I assume this is what you mean when you say it will only handle the
> >> >> > 1st
> >> >> > resultset. All of my reports have multiple 'chunks' in the body.
> >> >> > Do
> >> >> > you
> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >
> >> >> > --Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Pick the command type as stored procedure and then just enter the
> >> >> >> name
> >> >> >> of
> >> >> >> the stored procedure. When you click on the ! you should get back
> >> >> >> the
> >> >> >> data
> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> click
> >> >> >> on
> >> >> >> the
> >> >> >> refresh fields button (to the right of the ..., it looks like the
> >> >> >> refresh
> >> >> >> button for IE).
> >> >> >>
> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> cannot
> >> >> >> handle
> >> >> >> mutliple resultsets.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> > Reporting
> >> >> >> > Services. All of which are based on stored procedures, none of
> >> >> >> > which
> >> >> >> > require
> >> >> >> > any parameters. Most if not all of the report is calculated. I
> >> >> >> > am
> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> > place
> >> >> >> > w/the
> >> >> >> > correct expressions. The only one I actually got to accept the
> >> >> >> > expression
> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >
> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >
> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> > the
> >> >> >> > field
> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> > calculated
> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> > etc.
> >> >> >> > Using
> >> >> >> > the
> >> >> >> > report designer/report wizard to 'do it for me' only returns Date
> >> >> >> > and a
> >> >> >> > couple fields that are not even in my resultset. like one of my
> >> >> >> > values
> >> >> >> > in
> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> > available
> >> >> >> > is
> >> >> >> > 'ID__Total__'
> >> >> >> >
> >> >> >> > Further, in VS I've got the report open and am on the data tab, i
> >> >> >> > hit
> >> >> >> > the
> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> > retrieving
> >> >> >> > the
> >> >> >> > parameters in the query. Could not locate entry in sysdatabases
> >> >> >> > for
> >> >> >> > database
> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> > that
> >> >> >> > the
> >> >> >> > name
> >> >> >> > is entered correctly.'
> >> >> >> >
> >> >> >> > Clearly I am doing something very wrong with the stored procedure
> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> > procedures,
> >> >> >> > can
> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> > call
> >> >> >> > the
> >> >> >> > procs?
> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc that's
> >> >> >> > it.
> >> >> >> > Please advise.
> >> >> >> >
> >> >> >> >
> >> >> >> > -- Lynn
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||If you are going against SQL Server do not run your stored procedure this
way. Pick command type of stored procedure. RS will detect the parameters.
If going against ODBC or OLEDB driver (which uses ? format for parameters)
then pick text as the command type and do this:
myproc ?
Create multiple datasets and for each one you should call the stored
procedure for each one.
Bruce Loehle-Conger
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> And, if I blow away the 2nd dataset and just give my 1st one parameters,
> it
> almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> works
> just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
> tab it returns an error: SQL Syntax Errors Encountered...The designer
> does
> not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
> results are still returned to me. On 'Preview' tab, however, I get no
> data/results at all.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Yes, you are calling it three times. In RS you create three datasets. Go
>> to
>> the dataset tab and there is a combo box with the name of the dataset,
>> you
>> can click on that and there is a an option for a new.
>> In your stored procedure
>> if @.WHICHRESULTSET = 1
>> begin
>> --return the first resultset here
>> end
>> etc
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> > Bruce, or somebody else, might you give me an example of how to give
>> > the
>> > proc
>> > 3 parameters, producing three resultsets in a way that RS will display
>> > them?
>> > Or, am I giving it three parameters and calling it three times? If so,
>> > how
>> > would i call the 3 procs in RS?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Configure your existing stored procedure to accept a parameter (you
>> >> can
>> >> make
>> >> it optional so that it doesn't break existing code).
>> >>
>> >> Then call it three times in RS with a static value and create three
>> >> datasets.
>> >> For instance dataset1
>> >> yourproc 1
>> >>
>> >> Dataset2
>> >> yourproc 2
>> >>
>> >> etc.
>> >>
>> >> Then in your stored procedure return the appropriate resultset based
>> >> on
>> >> the
>> >> parameter.
>> >>
>> >> Downside is that your sp is being run three times.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
>> >> > please,
>> >> > on
>> >> > the second, possibly third procedure?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> This is three resultsets. RS does not have the ability to handle
>> >> >> that.
>> >> >> There
>> >> >> is no work around from RS side. You could create another stored
>> >> >> procedure
>> >> >> that calls this one and have it return just one of the resultsets.
>> >> >>
>> >> >> RS can deal with multiple datasets quite well, but each stored
>> >> >> procedure
>> >> >> call can only return one.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> > oh, bruce, that is great. I can't believe it was as simple as
>> >> >> > that.
>> >> >> > one
>> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >
>> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> > -- -- -- --
>> >> >> > 02/07/2006 333,333 333
>> >> >> > 33,333,333,333.33
>> >> >> >
>> >> >> > #Stocks Volume Total $
>> >> >> > -- -- --
>> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >
>> >> >> > EndPoint Liquidity #Trades Volume Total $
>> >> >> > -- -- -- -- --
>> >> >> > AAAA Add 114,729 21,797,575
>> >> >> > 583,102,631.33
>> >> >> > AAAA Opening 1 27
>> >> >> > 3,412.53
>> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> > 444,521,928.10
>> >> >> > AAAA Route 41 4,543
>> >> >> > 103,291.31
>> >> >> > BBBB Add 26,997 9,940,201
>> >> >> > 178,600,674.78
>> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> > 44,276,419.41
>> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> > 40,267,318.25
>> >> >> > CCCC Add 83,781 22,443,732
>> >> >> > 746,570,071.43
>> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> > 483,329,796.97
>> >> >> > CCCC Route 1,088 244,697
>> >> >> > 6,655,913.26
>> >> >> > DDDD Route 2 62,500
>> >> >> > 2,539,375.00
>> >> >> > DDDD Add 2,354 1,262,589
>> >> >> > 19,136,233.44
>> >> >> > DDDD Remove 258 195,019
>> >> >> > 6,227,451.69
>> >> >> >
>> >> >> > I only receive the top line in the resultset:
>> >> >> >
>> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> > -- -- -- --
>> >> >> > 02/07/2006 333,333 333
>> >> >> > 33,333,333,333.33
>> >> >> >
>> >> >> > I assume this is what you mean when you say it will only handle
>> >> >> > the
>> >> >> > 1st
>> >> >> > resultset. All of my reports have multiple 'chunks' in the
>> >> >> > body.
>> >> >> > Do
>> >> >> > you
>> >> >> > have any idea how I can achieve this report via reporting svcs?
>> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >
>> >> >> > --Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Pick the command type as stored procedure and then just enter
>> >> >> >> the
>> >> >> >> name
>> >> >> >> of
>> >> >> >> the stored procedure. When you click on the ! you should get
>> >> >> >> back
>> >> >> >> the
>> >> >> >> data
>> >> >> >> and the fields. If you do not get the field list populated then
>> >> >> >> click
>> >> >> >> on
>> >> >> >> the
>> >> >> >> refresh fields button (to the right of the ..., it looks like
>> >> >> >> the
>> >> >> >> refresh
>> >> >> >> button for IE).
>> >> >> >>
>> >> >> >> Note that RS only works with the first resultset returned. It
>> >> >> >> cannot
>> >> >> >> handle
>> >> >> >> mutliple resultsets.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> > Hi. I have a need to create a number of different reports via
>> >> >> >> > Reporting
>> >> >> >> > Services. All of which are based on stored procedures, none
>> >> >> >> > of
>> >> >> >> > which
>> >> >> >> > require
>> >> >> >> > any parameters. Most if not all of the report is calculated.
>> >> >> >> > I
>> >> >> >> > am
>> >> >> >> > struggling badly to get even the most basic of the fields in
>> >> >> >> > place
>> >> >> >> > w/the
>> >> >> >> > correct expressions. The only one I actually got to accept
>> >> >> >> > the
>> >> >> >> > expression
>> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >
>> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >
>> >> >> >> > It, too, fails to preview, indicating the value expression for
>> >> >> >> > the
>> >> >> >> > field
>> >> >> >> > contains an error. Again, all of the other report items are
>> >> >> >> > calculated
>> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
>> >> >> >> > etc.
>> >> >> >> > Using
>> >> >> >> > the
>> >> >> >> > report designer/report wizard to 'do it for me' only returns
>> >> >> >> > Date
>> >> >> >> > and a
>> >> >> >> > couple fields that are not even in my resultset. like one of
>> >> >> >> > my
>> >> >> >> > values
>> >> >> >> > in
>> >> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> >> > available
>> >> >> >> > is
>> >> >> >> > 'ID__Total__'
>> >> >> >> >
>> >> >> >> > Further, in VS I've got the report open and am on the data
>> >> >> >> > tab, i
>> >> >> >> > hit
>> >> >> >> > the
>> >> >> >> > Run option, I receive this error: An error occurred while
>> >> >> >> > retrieving
>> >> >> >> > the
>> >> >> >> > parameters in the query. Could not locate entry in
>> >> >> >> > sysdatabases
>> >> >> >> > for
>> >> >> >> > database
>> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
>> >> >> >> > that
>> >> >> >> > the
>> >> >> >> > name
>> >> >> >> > is entered correctly.'
>> >> >> >> >
>> >> >> >> > Clearly I am doing something very wrong with the stored
>> >> >> >> > procedure
>> >> >> >> > definition. Like I said, all of these reports are based on
>> >> >> >> > procedures,
>> >> >> >> > can
>> >> >> >> > anybody give me some suggestion/direction on the right way to
>> >> >> >> > call
>> >> >> >> > the
>> >> >> >> > procs?
>> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
>> >> >> >> > that's
>> >> >> >> > it.
>> >> >> >> > Please advise.
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > -- Lynn
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||i'm sorry, bruce, but where do i define the parameters? rs is not detecting
them. in my 1st dataset i've got cmd type stored procedure and the proc name
is in the query string. i assumed i would put the 1st parameter in on the
parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so i
gave it @.ch and the value of 1, but when i attempted to run it, it threw me a
'define query parameters box asking me to put the '1' in it.
-- Lynn
"Bruce L-C [MVP]" wrote:
> If you are going against SQL Server do not run your stored procedure this
> way. Pick command type of stored procedure. RS will detect the parameters.
> If going against ODBC or OLEDB driver (which uses ? format for parameters)
> then pick text as the command type and do this:
> myproc ?
> Create multiple datasets and for each one you should call the stored
> procedure for each one.
> Bruce Loehle-Conger
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> > And, if I blow away the 2nd dataset and just give my 1st one parameters,
> > it
> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> > works
> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in Data
> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> > does
> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and my
> > results are still returned to me. On 'Preview' tab, however, I get no
> > data/results at all.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Yes, you are calling it three times. In RS you create three datasets. Go
> >> to
> >> the dataset tab and there is a combo box with the name of the dataset,
> >> you
> >> can click on that and there is a an option for a new.
> >>
> >> In your stored procedure
> >>
> >> if @.WHICHRESULTSET = 1
> >> begin
> >> --return the first resultset here
> >> end
> >> etc
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> > Bruce, or somebody else, might you give me an example of how to give
> >> > the
> >> > proc
> >> > 3 parameters, producing three resultsets in a way that RS will display
> >> > them?
> >> > Or, am I giving it three parameters and calling it three times? If so,
> >> > how
> >> > would i call the 3 procs in RS?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> can
> >> >> make
> >> >> it optional so that it doesn't break existing code).
> >> >>
> >> >> Then call it three times in RS with a static value and create three
> >> >> datasets.
> >> >> For instance dataset1
> >> >> yourproc 1
> >> >>
> >> >> Dataset2
> >> >> yourproc 2
> >> >>
> >> >> etc.
> >> >>
> >> >> Then in your stored procedure return the appropriate resultset based
> >> >> on
> >> >> the
> >> >> parameter.
> >> >>
> >> >> Downside is that your sp is being run three times.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> > please,
> >> >> > on
> >> >> > the second, possibly third procedure?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> that.
> >> >> >> There
> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> procedure
> >> >> >> that calls this one and have it return just one of the resultsets.
> >> >> >>
> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> procedure
> >> >> >> call can only return one.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> > that.
> >> >> >> > one
> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >
> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> > -- -- -- --
> >> >> >> > 02/07/2006 333,333 333
> >> >> >> > 33,333,333,333.33
> >> >> >> >
> >> >> >> > #Stocks Volume Total $
> >> >> >> > -- -- --
> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >
> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> > -- -- -- -- --
> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> > 583,102,631.33
> >> >> >> > AAAA Opening 1 27
> >> >> >> > 3,412.53
> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> > 444,521,928.10
> >> >> >> > AAAA Route 41 4,543
> >> >> >> > 103,291.31
> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> > 178,600,674.78
> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> > 44,276,419.41
> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> > 40,267,318.25
> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> > 746,570,071.43
> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> > 483,329,796.97
> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> > 6,655,913.26
> >> >> >> > DDDD Route 2 62,500
> >> >> >> > 2,539,375.00
> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> > 19,136,233.44
> >> >> >> > DDDD Remove 258 195,019
> >> >> >> > 6,227,451.69
> >> >> >> >
> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >
> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> > -- -- -- --
> >> >> >> > 02/07/2006 333,333 333
> >> >> >> > 33,333,333,333.33
> >> >> >> >
> >> >> >> > I assume this is what you mean when you say it will only handle
> >> >> >> > the
> >> >> >> > 1st
> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> > body.
> >> >> >> > Do
> >> >> >> > you
> >> >> >> > have any idea how I can achieve this report via reporting svcs?
> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >
> >> >> >> > --Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> the
> >> >> >> >> name
> >> >> >> >> of
> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> back
> >> >> >> >> the
> >> >> >> >> data
> >> >> >> >> and the fields. If you do not get the field list populated then
> >> >> >> >> click
> >> >> >> >> on
> >> >> >> >> the
> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> the
> >> >> >> >> refresh
> >> >> >> >> button for IE).
> >> >> >> >>
> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> cannot
> >> >> >> >> handle
> >> >> >> >> mutliple resultsets.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> > Hi. I have a need to create a number of different reports via
> >> >> >> >> > Reporting
> >> >> >> >> > Services. All of which are based on stored procedures, none
> >> >> >> >> > of
> >> >> >> >> > which
> >> >> >> >> > require
> >> >> >> >> > any parameters. Most if not all of the report is calculated.
> >> >> >> >> > I
> >> >> >> >> > am
> >> >> >> >> > struggling badly to get even the most basic of the fields in
> >> >> >> >> > place
> >> >> >> >> > w/the
> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> > the
> >> >> >> >> > expression
> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >
> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >
> >> >> >> >> > It, too, fails to preview, indicating the value expression for
> >> >> >> >> > the
> >> >> >> >> > field
> >> >> >> >> > contains an error. Again, all of the other report items are
> >> >> >> >> > calculated
> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements, CASTs,
> >> >> >> >> > etc.
> >> >> >> >> > Using
> >> >> >> >> > the
> >> >> >> >> > report designer/report wizard to 'do it for me' only returns
> >> >> >> >> > Date
> >> >> >> >> > and a
> >> >> >> >> > couple fields that are not even in my resultset. like one of
> >> >> >> >> > my
> >> >> >> >> > values
> >> >> >> >> > in
> >> >> >> >> > the report is 'Total Trades'...one of the fields listed as
> >> >> >> >> > available
> >> >> >> >> > is
> >> >> >> >> > 'ID__Total__'
> >> >> >> >> >
> >> >> >> >> > Further, in VS I've got the report open and am on the data
> >> >> >> >> > tab, i
> >> >> >> >> > hit
> >> >> >> >> > the
> >> >> >> >> > Run option, I receive this error: An error occurred while
> >> >> >> >> > retrieving
> >> >> >> >> > the
> >> >> >> >> > parameters in the query. Could not locate entry in
> >> >> >> >> > sysdatabases
> >> >> >> >> > for
> >> >> >> >> > database
> >> >> >> >> > 'EXEC databasename'. No entry found with that name. Make sure
> >> >> >> >> > that
> >> >> >> >> > the
> >> >> >> >> > name
> >> >> >> >> > is entered correctly.'
> >> >> >> >> >
> >> >> >> >> > Clearly I am doing something very wrong with the stored
> >> >> >> >> > procedure
> >> >> >> >> > definition. Like I said, all of these reports are based on
> >> >> >> >> > procedures,
> >> >> >> >> > can
> >> >> >> >> > anybody give me some suggestion/direction on the right way to
> >> >> >> >> > call
> >> >> >> >> > the
> >> >> >> >> > procs?
> >> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
> >> >> >> >> > that's
> >> >> >> >> > it.
> >> >> >> >> > Please advise.
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > -- Lynn
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Are you going against SQL Server?
If so, then just select tored procedure for the command type and just put in
the name of the stored procedure. Do not put exec in from of it or anything
else. It should detect the parameter and prompt you for it. It should also
create a report parameter as well for you.
Try creating a new dataset and do this from the start. If you continue to
have problems create a new stored procedure just for testing .
create procedure dbo.testproc
@.PARAM1 int
as
select 'Parameter passed in = ' + @.PARAM1 as Message
return
Get the above procedure to work for you so you know how to call a stored
procedure they way I am telling you (do not use exec).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> i'm sorry, bruce, but where do i define the parameters? rs is not
> detecting
> them. in my 1st dataset i've got cmd type stored procedure and the proc
> name
> is in the query string. i assumed i would put the 1st parameter in on the
> parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> i
> gave it @.ch and the value of 1, but when i attempted to run it, it threw
> me a
> 'define query parameters box asking me to put the '1' in it.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> If you are going against SQL Server do not run your stored procedure this
>> way. Pick command type of stored procedure. RS will detect the
>> parameters.
>> If going against ODBC or OLEDB driver (which uses ? format for
>> parameters)
>> then pick text as the command type and do this:
>> myproc ?
>> Create multiple datasets and for each one you should call the stored
>> procedure for each one.
>> Bruce Loehle-Conger
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> > And, if I blow away the 2nd dataset and just give my 1st one
>> > parameters,
>> > it
>> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
>> > works
>> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
>> > Data
>> > tab it returns an error: SQL Syntax Errors Encountered...The designer
>> > does
>> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
>> > my
>> > results are still returned to me. On 'Preview' tab, however, I get no
>> > data/results at all.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Yes, you are calling it three times. In RS you create three datasets.
>> >> Go
>> >> to
>> >> the dataset tab and there is a combo box with the name of the dataset,
>> >> you
>> >> can click on that and there is a an option for a new.
>> >>
>> >> In your stored procedure
>> >>
>> >> if @.WHICHRESULTSET = 1
>> >> begin
>> >> --return the first resultset here
>> >> end
>> >> etc
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> > Bruce, or somebody else, might you give me an example of how to give
>> >> > the
>> >> > proc
>> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> > display
>> >> > them?
>> >> > Or, am I giving it three parameters and calling it three times? If
>> >> > so,
>> >> > how
>> >> > would i call the 3 procs in RS?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Configure your existing stored procedure to accept a parameter (you
>> >> >> can
>> >> >> make
>> >> >> it optional so that it doesn't break existing code).
>> >> >>
>> >> >> Then call it three times in RS with a static value and create three
>> >> >> datasets.
>> >> >> For instance dataset1
>> >> >> yourproc 1
>> >> >>
>> >> >> Dataset2
>> >> >> yourproc 2
>> >> >>
>> >> >> etc.
>> >> >>
>> >> >> Then in your stored procedure return the appropriate resultset
>> >> >> based
>> >> >> on
>> >> >> the
>> >> >> parameter.
>> >> >>
>> >> >> Downside is that your sp is being run three times.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
>> >> >> > please,
>> >> >> > on
>> >> >> > the second, possibly third procedure?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> This is three resultsets. RS does not have the ability to handle
>> >> >> >> that.
>> >> >> >> There
>> >> >> >> is no work around from RS side. You could create another stored
>> >> >> >> procedure
>> >> >> >> that calls this one and have it return just one of the
>> >> >> >> resultsets.
>> >> >> >>
>> >> >> >> RS can deal with multiple datasets quite well, but each stored
>> >> >> >> procedure
>> >> >> >> call can only return one.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
>> >> >> >> > that.
>> >> >> >> > one
>> >> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >> >
>> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> > -- -- -- --
>> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> > 33,333,333,333.33
>> >> >> >> >
>> >> >> >> > #Stocks Volume Total $
>> >> >> >> > -- -- --
>> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >
>> >> >> >> > EndPoint Liquidity #Trades Volume Total $
>> >> >> >> > -- -- -- -- --
>> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> > 583,102,631.33
>> >> >> >> > AAAA Opening 1 27
>> >> >> >> > 3,412.53
>> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> > 444,521,928.10
>> >> >> >> > AAAA Route 41 4,543
>> >> >> >> > 103,291.31
>> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> > 178,600,674.78
>> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> > 44,276,419.41
>> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> > 40,267,318.25
>> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> > 746,570,071.43
>> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> > 483,329,796.97
>> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> > 6,655,913.26
>> >> >> >> > DDDD Route 2 62,500
>> >> >> >> > 2,539,375.00
>> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> > 19,136,233.44
>> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> > 6,227,451.69
>> >> >> >> >
>> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >
>> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> > -- -- -- --
>> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> > 33,333,333,333.33
>> >> >> >> >
>> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> > handle
>> >> >> >> > the
>> >> >> >> > 1st
>> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
>> >> >> >> > body.
>> >> >> >> > Do
>> >> >> >> > you
>> >> >> >> > have any idea how I can achieve this report via reporting
>> >> >> >> > svcs?
>> >> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >> >
>> >> >> >> > --Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Pick the command type as stored procedure and then just enter
>> >> >> >> >> the
>> >> >> >> >> name
>> >> >> >> >> of
>> >> >> >> >> the stored procedure. When you click on the ! you should get
>> >> >> >> >> back
>> >> >> >> >> the
>> >> >> >> >> data
>> >> >> >> >> and the fields. If you do not get the field list populated
>> >> >> >> >> then
>> >> >> >> >> click
>> >> >> >> >> on
>> >> >> >> >> the
>> >> >> >> >> refresh fields button (to the right of the ..., it looks like
>> >> >> >> >> the
>> >> >> >> >> refresh
>> >> >> >> >> button for IE).
>> >> >> >> >>
>> >> >> >> >> Note that RS only works with the first resultset returned. It
>> >> >> >> >> cannot
>> >> >> >> >> handle
>> >> >> >> >> mutliple resultsets.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> >> > Hi. I have a need to create a number of different reports
>> >> >> >> >> > via
>> >> >> >> >> > Reporting
>> >> >> >> >> > Services. All of which are based on stored procedures,
>> >> >> >> >> > none
>> >> >> >> >> > of
>> >> >> >> >> > which
>> >> >> >> >> > require
>> >> >> >> >> > any parameters. Most if not all of the report is
>> >> >> >> >> > calculated.
>> >> >> >> >> > I
>> >> >> >> >> > am
>> >> >> >> >> > struggling badly to get even the most basic of the fields
>> >> >> >> >> > in
>> >> >> >> >> > place
>> >> >> >> >> > w/the
>> >> >> >> >> > correct expressions. The only one I actually got to accept
>> >> >> >> >> > the
>> >> >> >> >> > expression
>> >> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >> >
>> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >> >
>> >> >> >> >> > It, too, fails to preview, indicating the value expression
>> >> >> >> >> > for
>> >> >> >> >> > the
>> >> >> >> >> > field
>> >> >> >> >> > contains an error. Again, all of the other report items
>> >> >> >> >> > are
>> >> >> >> >> > calculated
>> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,
>> >> >> >> >> > CASTs,
>> >> >> >> >> > etc.
>> >> >> >> >> > Using
>> >> >> >> >> > the
>> >> >> >> >> > report designer/report wizard to 'do it for me' only
>> >> >> >> >> > returns
>> >> >> >> >> > Date
>> >> >> >> >> > and a
>> >> >> >> >> > couple fields that are not even in my resultset. like one
>> >> >> >> >> > of
>> >> >> >> >> > my
>> >> >> >> >> > values
>> >> >> >> >> > in
>> >> >> >> >> > the report is 'Total Trades'...one of the fields listed as
>> >> >> >> >> > available
>> >> >> >> >> > is
>> >> >> >> >> > 'ID__Total__'
>> >> >> >> >> >
>> >> >> >> >> > Further, in VS I've got the report open and am on the data
>> >> >> >> >> > tab, i
>> >> >> >> >> > hit
>> >> >> >> >> > the
>> >> >> >> >> > Run option, I receive this error: An error occurred while
>> >> >> >> >> > retrieving
>> >> >> >> >> > the
>> >> >> >> >> > parameters in the query. Could not locate entry in
>> >> >> >> >> > sysdatabases
>> >> >> >> >> > for
>> >> >> >> >> > database
>> >> >> >> >> > 'EXEC databasename'. No entry found with that name. Make
>> >> >> >> >> > sure
>> >> >> >> >> > that
>> >> >> >> >> > the
>> >> >> >> >> > name
>> >> >> >> >> > is entered correctly.'
>> >> >> >> >> >
>> >> >> >> >> > Clearly I am doing something very wrong with the stored
>> >> >> >> >> > procedure
>> >> >> >> >> > definition. Like I said, all of these reports are based on
>> >> >> >> >> > procedures,
>> >> >> >> >> > can
>> >> >> >> >> > anybody give me some suggestion/direction on the right way
>> >> >> >> >> > to
>> >> >> >> >> > call
>> >> >> >> >> > the
>> >> >> >> >> > procs?
>> >> >> >> >> > They run w/out parameters...EXEC databasename.dbo.proc
>> >> >> >> >> > that's
>> >> >> >> >> > it.
>> >> >> >> >> > Please advise.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > -- Lynn
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||yes, it's sql2k, i am somewhat of a RS newbie, but I spent last week setting
reports up for all my sql jobs, just to kind of practice in the RS arena.
everything went flawlessly. i even set up one of the company reports just
fine, but it was a proc with only a single resultset. everything else is
multiple resultsets, i'm just having a very difficult time. but, i will give
this a shot, bruce. thank you, bruce
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||i am not sure how to display each resultset/dataset in the same report
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||removing everything but the proc name in the query string in dataset fails
w/this:
Could not generate a list of fields for the query.
Check the query syntax or click Refresh Fields on the query toolbar.
Line 1: Incorrect syntax near 'usp_procname'.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||my bad, bruce, that was because i had text in cmd type. having changed it to
stored procedure, it pops up the 'define query parameters' box, asking me to
put something in. how do i pass those in dynamically?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||last one for a while, bruce, i promise. i've got all 4 datasets in there,
each asks me for a parameter, i put 1,2,3 and 4 into each, getting my 'whole
report' in four small subsets of data. how do i get this to happen on the
report page automatically without needing user input?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Are you going against SQL Server?
> If so, then just select tored procedure for the command type and just put in
> the name of the stored procedure. Do not put exec in from of it or anything
> else. It should detect the parameter and prompt you for it. It should also
> create a report parameter as well for you.
> Try creating a new dataset and do this from the start. If you continue to
> have problems create a new stored procedure just for testing .
> create procedure dbo.testproc
> @.PARAM1 int
> as
> select 'Parameter passed in = ' + @.PARAM1 as Message
> return
> Get the above procedure to work for you so you know how to call a stored
> procedure they way I am telling you (do not use exec).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> > i'm sorry, bruce, but where do i define the parameters? rs is not
> > detecting
> > them. in my 1st dataset i've got cmd type stored procedure and the proc
> > name
> > is in the query string. i assumed i would put the 1st parameter in on the
> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets, so
> > i
> > gave it @.ch and the value of 1, but when i attempted to run it, it threw
> > me a
> > 'define query parameters box asking me to put the '1' in it.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you are going against SQL Server do not run your stored procedure this
> >> way. Pick command type of stored procedure. RS will detect the
> >> parameters.
> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> parameters)
> >> then pick text as the command type and do this:
> >> myproc ?
> >>
> >> Create multiple datasets and for each one you should call the stored
> >> procedure for each one.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> > parameters,
> >> > it
> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the results,
> >> > works
> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN in
> >> > Data
> >> > tab it returns an error: SQL Syntax Errors Encountered...The designer
> >> > does
> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK' and
> >> > my
> >> > results are still returned to me. On 'Preview' tab, however, I get no
> >> > data/results at all.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Yes, you are calling it three times. In RS you create three datasets.
> >> >> Go
> >> >> to
> >> >> the dataset tab and there is a combo box with the name of the dataset,
> >> >> you
> >> >> can click on that and there is a an option for a new.
> >> >>
> >> >> In your stored procedure
> >> >>
> >> >> if @.WHICHRESULTSET = 1
> >> >> begin
> >> >> --return the first resultset here
> >> >> end
> >> >> etc
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> > Bruce, or somebody else, might you give me an example of how to give
> >> >> > the
> >> >> > proc
> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> > display
> >> >> > them?
> >> >> > Or, am I giving it three parameters and calling it three times? If
> >> >> > so,
> >> >> > how
> >> >> > would i call the 3 procs in RS?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Configure your existing stored procedure to accept a parameter (you
> >> >> >> can
> >> >> >> make
> >> >> >> it optional so that it doesn't break existing code).
> >> >> >>
> >> >> >> Then call it three times in RS with a static value and create three
> >> >> >> datasets.
> >> >> >> For instance dataset1
> >> >> >> yourproc 1
> >> >> >>
> >> >> >> Dataset2
> >> >> >> yourproc 2
> >> >> >>
> >> >> >> etc.
> >> >> >>
> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> based
> >> >> >> on
> >> >> >> the
> >> >> >> parameter.
> >> >> >>
> >> >> >> Downside is that your sp is being run three times.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little more,
> >> >> >> > please,
> >> >> >> > on
> >> >> >> > the second, possibly third procedure?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> This is three resultsets. RS does not have the ability to handle
> >> >> >> >> that.
> >> >> >> >> There
> >> >> >> >> is no work around from RS side. You could create another stored
> >> >> >> >> procedure
> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> resultsets.
> >> >> >> >>
> >> >> >> >> RS can deal with multiple datasets quite well, but each stored
> >> >> >> >> procedure
> >> >> >> >> call can only return one.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple as
> >> >> >> >> > that.
> >> >> >> >> > one
> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> > -- -- --
> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > EndPoint Liquidity #Trades Volume Total $
> >> >> >> >> > -- -- -- -- --
> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> > 583,102,631.33
> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> > 3,412.53
> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> > 444,521,928.10
> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> > 103,291.31
> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> > 178,600,674.78
> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> > 44,276,419.41
> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> > 40,267,318.25
> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> > 746,570,071.43
> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> > 483,329,796.97
> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> > 6,655,913.26
> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> > 2,539,375.00
> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> > 19,136,233.44
> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> > 6,227,451.69
> >> >> >> >> >
> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >
> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> > -- -- -- --
> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >
> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> > handle
> >> >> >> >> > the
> >> >> >> >> > 1st
> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in the
> >> >> >> >> > body.
> >> >> >> >> > Do
> >> >> >> >> > you
> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> > svcs?
> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >
> >> >> >> >> > --Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Pick the command type as stored procedure and then just enter
> >> >> >> >> >> the
> >> >> >> >> >> name
> >> >> >> >> >> of
> >> >> >> >> >> the stored procedure. When you click on the ! you should get
> >> >> >> >> >> back
> >> >> >> >> >> the
> >> >> >> >> >> data
> >> >> >> >> >> and the fields. If you do not get the field list populated
> >> >> >> >> >> then
> >> >> >> >> >> click
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> refresh fields button (to the right of the ..., it looks like
> >> >> >> >> >> the
> >> >> >> >> >> refresh
> >> >> >> >> >> button for IE).
> >> >> >> >> >>
> >> >> >> >> >> Note that RS only works with the first resultset returned. It
> >> >> >> >> >> cannot
> >> >> >> >> >> handle
> >> >> >> >> >> mutliple resultsets.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
> >> >> >> >> >> > Hi. I have a need to create a number of different reports
> >> >> >> >> >> > via
> >> >> >> >> >> > Reporting
> >> >> >> >> >> > Services. All of which are based on stored procedures,
> >> >> >> >> >> > none
> >> >> >> >> >> > of
> >> >> >> >> >> > which
> >> >> >> >> >> > require
> >> >> >> >> >> > any parameters. Most if not all of the report is
> >> >> >> >> >> > calculated.
> >> >> >> >> >> > I
> >> >> >> >> >> > am
> >> >> >> >> >> > struggling badly to get even the most basic of the fields
> >> >> >> >> >> > in
> >> >> >> >> >> > place
> >> >> >> >> >> > w/the
> >> >> >> >> >> > correct expressions. The only one I actually got to accept
> >> >> >> >> >> > the
> >> >> >> >> >> > expression
> >> >> >> >> >> > was a Date field, this is the calculation:
> >> >> >> >> >> >
> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
> >> >> >> >> >> >
> >> >> >> >> >> > It, too, fails to preview, indicating the value expression
> >> >> >> >> >> > for
> >> >> >> >> >> > the
> >> >> >> >> >> > field
> >> >> >> >> >> > contains an error. Again, all of the other report items
> >> >> >> >> >> > are
> >> >> >> >> >> > calculated
> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||Query parameters and report parameters seem to be the same thing but they
are not. RS automatically creates a report parameter for each query
parameter but instead you can map the query parameter to a constant. Click
on the ... for the dataset, go to the parameters tab. On the right you will
see it mapping to the report parameter, click on that and select expression.
In expression put = 1 (assuming it is an integert expression) for the first
dataset, =2 etc. Then go to report layout, report menu-> report parameters
and then delete the report parameters created for you.
You are very very close to the solution.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> last one for a while, bruce, i promise. i've got all 4 datasets in there,
> each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> 'whole
> report' in four small subsets of data. how do i get this to happen on the
> report page automatically without needing user input?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Are you going against SQL Server?
>> If so, then just select tored procedure for the command type and just put
>> in
>> the name of the stored procedure. Do not put exec in from of it or
>> anything
>> else. It should detect the parameter and prompt you for it. It should
>> also
>> create a report parameter as well for you.
>> Try creating a new dataset and do this from the start. If you continue to
>> have problems create a new stored procedure just for testing .
>> create procedure dbo.testproc
>> @.PARAM1 int
>> as
>> select 'Parameter passed in = ' + @.PARAM1 as Message
>> return
>> Get the above procedure to work for you so you know how to call a stored
>> procedure they way I am telling you (do not use exec).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> > i'm sorry, bruce, but where do i define the parameters? rs is not
>> > detecting
>> > them. in my 1st dataset i've got cmd type stored procedure and the
>> > proc
>> > name
>> > is in the query string. i assumed i would put the 1st parameter in on
>> > the
>> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets,
>> > so
>> > i
>> > gave it @.ch and the value of 1, but when i attempted to run it, it
>> > threw
>> > me a
>> > 'define query parameters box asking me to put the '1' in it.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> If you are going against SQL Server do not run your stored procedure
>> >> this
>> >> way. Pick command type of stored procedure. RS will detect the
>> >> parameters.
>> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> parameters)
>> >> then pick text as the command type and do this:
>> >> myproc ?
>> >>
>> >> Create multiple datasets and for each one you should call the stored
>> >> procedure for each one.
>> >>
>> >> Bruce Loehle-Conger
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> > parameters,
>> >> > it
>> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> > results,
>> >> > works
>> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN
>> >> > in
>> >> > Data
>> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> > designer
>> >> > does
>> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK'
>> >> > and
>> >> > my
>> >> > results are still returned to me. On 'Preview' tab, however, I get
>> >> > no
>> >> > data/results at all.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> datasets.
>> >> >> Go
>> >> >> to
>> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> dataset,
>> >> >> you
>> >> >> can click on that and there is a an option for a new.
>> >> >>
>> >> >> In your stored procedure
>> >> >>
>> >> >> if @.WHICHRESULTSET = 1
>> >> >> begin
>> >> >> --return the first resultset here
>> >> >> end
>> >> >> etc
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> > Bruce, or somebody else, might you give me an example of how to
>> >> >> > give
>> >> >> > the
>> >> >> > proc
>> >> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> >> > display
>> >> >> > them?
>> >> >> > Or, am I giving it three parameters and calling it three times?
>> >> >> > If
>> >> >> > so,
>> >> >> > how
>> >> >> > would i call the 3 procs in RS?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Configure your existing stored procedure to accept a parameter
>> >> >> >> (you
>> >> >> >> can
>> >> >> >> make
>> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >>
>> >> >> >> Then call it three times in RS with a static value and create
>> >> >> >> three
>> >> >> >> datasets.
>> >> >> >> For instance dataset1
>> >> >> >> yourproc 1
>> >> >> >>
>> >> >> >> Dataset2
>> >> >> >> yourproc 2
>> >> >> >>
>> >> >> >> etc.
>> >> >> >>
>> >> >> >> Then in your stored procedure return the appropriate resultset
>> >> >> >> based
>> >> >> >> on
>> >> >> >> the
>> >> >> >> parameter.
>> >> >> >>
>> >> >> >> Downside is that your sp is being run three times.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
>> >> >> >> > more,
>> >> >> >> > please,
>> >> >> >> > on
>> >> >> >> > the second, possibly third procedure?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> This is three resultsets. RS does not have the ability to
>> >> >> >> >> handle
>> >> >> >> >> that.
>> >> >> >> >> There
>> >> >> >> >> is no work around from RS side. You could create another
>> >> >> >> >> stored
>> >> >> >> >> procedure
>> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> resultsets.
>> >> >> >> >>
>> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> stored
>> >> >> >> >> procedure
>> >> >> >> >> call can only return one.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple
>> >> >> >> >> > as
>> >> >> >> >> > that.
>> >> >> >> >> > one
>> >> >> >> >> > remaining problem, though. one of my reports is like this:
>> >> >> >> >> >
>> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> > -- -- -- --
>> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > #Stocks Volume Total $
>> >> >> >> >> > -- -- --
>> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > EndPoint Liquidity #Trades Volume
>> >> >> >> >> > Total $
>> >> >> >> >> > -- -- -- -- --
>> >> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> >> > 583,102,631.33
>> >> >> >> >> > AAAA Opening 1 27
>> >> >> >> >> > 3,412.53
>> >> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> >> > 444,521,928.10
>> >> >> >> >> > AAAA Route 41 4,543
>> >> >> >> >> > 103,291.31
>> >> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> >> > 178,600,674.78
>> >> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> >> > 44,276,419.41
>> >> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> >> > 40,267,318.25
>> >> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> >> > 746,570,071.43
>> >> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> >> > 483,329,796.97
>> >> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> >> > 6,655,913.26
>> >> >> >> >> > DDDD Route 2 62,500
>> >> >> >> >> > 2,539,375.00
>> >> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> >> > 19,136,233.44
>> >> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> >> > 6,227,451.69
>> >> >> >> >> >
>> >> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >> >
>> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> > -- -- -- --
>> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >
>> >> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> >> > handle
>> >> >> >> >> > the
>> >> >> >> >> > 1st
>> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
>> >> >> >> >> > the
>> >> >> >> >> > body.
>> >> >> >> >> > Do
>> >> >> >> >> > you
>> >> >> >> >> > have any idea how I can achieve this report via reporting
>> >> >> >> >> > svcs?
>> >> >> >> >> > Unfortunately, this is very important. Please do advise.
>> >> >> >> >> >
>> >> >> >> >> > --Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Pick the command type as stored procedure and then just
>> >> >> >> >> >> enter
>> >> >> >> >> >> the
>> >> >> >> >> >> name
>> >> >> >> >> >> of
>> >> >> >> >> >> the stored procedure. When you click on the ! you should
>> >> >> >> >> >> get
>> >> >> >> >> >> back
>> >> >> >> >> >> the
>> >> >> >> >> >> data
>> >> >> >> >> >> and the fields. If you do not get the field list populated
>> >> >> >> >> >> then
>> >> >> >> >> >> click
>> >> >> >> >> >> on
>> >> >> >> >> >> the
>> >> >> >> >> >> refresh fields button (to the right of the ..., it looks
>> >> >> >> >> >> like
>> >> >> >> >> >> the
>> >> >> >> >> >> refresh
>> >> >> >> >> >> button for IE).
>> >> >> >> >> >>
>> >> >> >> >> >> Note that RS only works with the first resultset returned.
>> >> >> >> >> >> It
>> >> >> >> >> >> cannot
>> >> >> >> >> >> handle
>> >> >> >> >> >> mutliple resultsets.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:EF6A6CBC-083B-4537-83D9-D763A8ABA056@.microsoft.com...
>> >> >> >> >> >> > Hi. I have a need to create a number of different
>> >> >> >> >> >> > reports
>> >> >> >> >> >> > via
>> >> >> >> >> >> > Reporting
>> >> >> >> >> >> > Services. All of which are based on stored procedures,
>> >> >> >> >> >> > none
>> >> >> >> >> >> > of
>> >> >> >> >> >> > which
>> >> >> >> >> >> > require
>> >> >> >> >> >> > any parameters. Most if not all of the report is
>> >> >> >> >> >> > calculated.
>> >> >> >> >> >> > I
>> >> >> >> >> >> > am
>> >> >> >> >> >> > struggling badly to get even the most basic of the
>> >> >> >> >> >> > fields
>> >> >> >> >> >> > in
>> >> >> >> >> >> > place
>> >> >> >> >> >> > w/the
>> >> >> >> >> >> > correct expressions. The only one I actually got to
>> >> >> >> >> >> > accept
>> >> >> >> >> >> > the
>> >> >> >> >> >> > expression
>> >> >> >> >> >> > was a Date field, this is the calculation:
>> >> >> >> >> >> >
>> >> >> >> >> >> > =SELECT CONVERT(char(10),dateadd(dd,-0,GetDate()),1)
>> >> >> >> >> >> >
>> >> >> >> >> >> > It, too, fails to preview, indicating the value
>> >> >> >> >> >> > expression
>> >> >> >> >> >> > for
>> >> >> >> >> >> > the
>> >> >> >> >> >> > field
>> >> >> >> >> >> > contains an error. Again, all of the other report items
>> >> >> >> >> >> > are
>> >> >> >> >> >> > calculated
>> >> >> >> >> >> > fields. SUMs, totals, money formats, CASE statements,|||oh my goodness this is frustrating me....i did what you said, bruce, and it
almost worked. the preview report shows me three values which correspond, i
believe, to the only three fields in my report. see, they're all calculated
fields. the output of the rpt is this:
Build complete -- 0 errors, 0 warnings
The data set â'DataSet3â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
The data set â'DataSet4â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
The data set â'DataSet2â' contains a definition for the field
â'Futures_Volumeâ'. This field is missing from the returned result set from the
data source.
Preview complete -- 0 errors, 3 warnings
Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
4. The report, or the query, is not auto-generating my other fields as it
did for three that I do see. The 'Futures_Volume' is one of the fields that
was auto-generated for me, and it is in the 1st dataset. Is it that I just
need to manually add in the other fields? Please do let me know what you
think.
and thank you, bruce, for helping me through this. i truly do appreciate
it. i know i am close...and i got the other reports for my server jobs and
one of the other company reports to work. it's just these multi-resultset
reports are fighting me.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Query parameters and report parameters seem to be the same thing but they
> are not. RS automatically creates a report parameter for each query
> parameter but instead you can map the query parameter to a constant. Click
> on the ... for the dataset, go to the parameters tab. On the right you will
> see it mapping to the report parameter, click on that and select expression.
> In expression put = 1 (assuming it is an integert expression) for the first
> dataset, =2 etc. Then go to report layout, report menu-> report parameters
> and then delete the report parameters created for you.
> You are very very close to the solution.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> > last one for a while, bruce, i promise. i've got all 4 datasets in there,
> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> > 'whole
> > report' in four small subsets of data. how do i get this to happen on the
> > report page automatically without needing user input?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Are you going against SQL Server?
> >>
> >> If so, then just select tored procedure for the command type and just put
> >> in
> >> the name of the stored procedure. Do not put exec in from of it or
> >> anything
> >> else. It should detect the parameter and prompt you for it. It should
> >> also
> >> create a report parameter as well for you.
> >>
> >> Try creating a new dataset and do this from the start. If you continue to
> >> have problems create a new stored procedure just for testing .
> >>
> >> create procedure dbo.testproc
> >> @.PARAM1 int
> >> as
> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> return
> >>
> >> Get the above procedure to work for you so you know how to call a stored
> >> procedure they way I am telling you (do not use exec).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
> >> > detecting
> >> > them. in my 1st dataset i've got cmd type stored procedure and the
> >> > proc
> >> > name
> >> > is in the query string. i assumed i would put the 1st parameter in on
> >> > the
> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other datasets,
> >> > so
> >> > i
> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
> >> > threw
> >> > me a
> >> > 'define query parameters box asking me to put the '1' in it.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> If you are going against SQL Server do not run your stored procedure
> >> >> this
> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> parameters.
> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> parameters)
> >> >> then pick text as the command type and do this:
> >> >> myproc ?
> >> >>
> >> >> Create multiple datasets and for each one you should call the stored
> >> >> procedure for each one.
> >> >>
> >> >> Bruce Loehle-Conger
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> > parameters,
> >> >> > it
> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> > results,
> >> >> > works
> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit RUN
> >> >> > in
> >> >> > Data
> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> > designer
> >> >> > does
> >> >> > not graphically support the EXEC SQL Construct' but, i hit 'OK'
> >> >> > and
> >> >> > my
> >> >> > results are still returned to me. On 'Preview' tab, however, I get
> >> >> > no
> >> >> > data/results at all.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> datasets.
> >> >> >> Go
> >> >> >> to
> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> dataset,
> >> >> >> you
> >> >> >> can click on that and there is a an option for a new.
> >> >> >>
> >> >> >> In your stored procedure
> >> >> >>
> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> begin
> >> >> >> --return the first resultset here
> >> >> >> end
> >> >> >> etc
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> > Bruce, or somebody else, might you give me an example of how to
> >> >> >> > give
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> >> > display
> >> >> >> > them?
> >> >> >> > Or, am I giving it three parameters and calling it three times?
> >> >> >> > If
> >> >> >> > so,
> >> >> >> > how
> >> >> >> > would i call the 3 procs in RS?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Configure your existing stored procedure to accept a parameter
> >> >> >> >> (you
> >> >> >> >> can
> >> >> >> >> make
> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >>
> >> >> >> >> Then call it three times in RS with a static value and create
> >> >> >> >> three
> >> >> >> >> datasets.
> >> >> >> >> For instance dataset1
> >> >> >> >> yourproc 1
> >> >> >> >>
> >> >> >> >> Dataset2
> >> >> >> >> yourproc 2
> >> >> >> >>
> >> >> >> >> etc.
> >> >> >> >>
> >> >> >> >> Then in your stored procedure return the appropriate resultset
> >> >> >> >> based
> >> >> >> >> on
> >> >> >> >> the
> >> >> >> >> parameter.
> >> >> >> >>
> >> >> >> >> Downside is that your sp is being run three times.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
> >> >> >> >> > more,
> >> >> >> >> > please,
> >> >> >> >> > on
> >> >> >> >> > the second, possibly third procedure?
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> This is three resultsets. RS does not have the ability to
> >> >> >> >> >> handle
> >> >> >> >> >> that.
> >> >> >> >> >> There
> >> >> >> >> >> is no work around from RS side. You could create another
> >> >> >> >> >> stored
> >> >> >> >> >> procedure
> >> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> >> resultsets.
> >> >> >> >> >>
> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
> >> >> >> >> >> stored
> >> >> >> >> >> procedure
> >> >> >> >> >> call can only return one.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as simple
> >> >> >> >> >> > as
> >> >> >> >> >> > that.
> >> >> >> >> >> > one
> >> >> >> >> >> > remaining problem, though. one of my reports is like this:
> >> >> >> >> >> >
> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> >> > -- -- -- --
> >> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > #Stocks Volume Total $
> >> >> >> >> >> > -- -- --
> >> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > EndPoint Liquidity #Trades Volume
> >> >> >> >> >> > Total $
> >> >> >> >> >> > -- -- -- -- --
> >> >> >> >> >> > AAAA Add 114,729 21,797,575
> >> >> >> >> >> > 583,102,631.33
> >> >> >> >> >> > AAAA Opening 1 27
> >> >> >> >> >> > 3,412.53
> >> >> >> >> >> > AAAA Remove 30,836 8,330,843
> >> >> >> >> >> > 444,521,928.10
> >> >> >> >> >> > AAAA Route 41 4,543
> >> >> >> >> >> > 103,291.31
> >> >> >> >> >> > BBBB Add 26,997 9,940,201
> >> >> >> >> >> > 178,600,674.78
> >> >> >> >> >> > BBBB Opening 8,089 1,448,143
> >> >> >> >> >> > 44,276,419.41
> >> >> >> >> >> > BBBB Remove 3,406 1,719,403
> >> >> >> >> >> > 40,267,318.25
> >> >> >> >> >> > CCCC Add 83,781 22,443,732
> >> >> >> >> >> > 746,570,071.43
> >> >> >> >> >> > CCCC Remove 35,756 12,250,359
> >> >> >> >> >> > 483,329,796.97
> >> >> >> >> >> > CCCC Route 1,088 244,697
> >> >> >> >> >> > 6,655,913.26
> >> >> >> >> >> > DDDD Route 2 62,500
> >> >> >> >> >> > 2,539,375.00
> >> >> >> >> >> > DDDD Add 2,354 1,262,589
> >> >> >> >> >> > 19,136,233.44
> >> >> >> >> >> > DDDD Remove 258 195,019
> >> >> >> >> >> > 6,227,451.69
> >> >> >> >> >> >
> >> >> >> >> >> > I only receive the top line in the resultset:
> >> >> >> >> >> >
> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
> >> >> >> >> >> > -- -- -- --
> >> >> >> >> >> > 02/07/2006 333,333 333
> >> >> >> >> >> > 33,333,333,333.33
> >> >> >> >> >> >
> >> >> >> >> >> > I assume this is what you mean when you say it will only
> >> >> >> >> >> > handle
> >> >> >> >> >> > the
> >> >> >> >> >> > 1st
> >> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
> >> >> >> >> >> > the
> >> >> >> >> >> > body.
> >> >> >> >> >> > Do
> >> >> >> >> >> > you
> >> >> >> >> >> > have any idea how I can achieve this report via reporting
> >> >> >> >> >> > svcs?
> >> >> >> >> >> > Unfortunately, this is very important. Please do advise.
> >> >> >> >> >> >
> >> >> >> >> >> > --Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Pick the command type as stored procedure and then just
> >> >> >> >> >> >> enter
> >> >> >> >> >> >> the
> >> >> >> >> >> >> name
> >> >> >> >> >> >> of
> >> >> >> >> >> >> the stored procedure. When you click on the ! you should
> >> >> >> >> >> >> get
> >> >> >> >> >> >> back|||For each of your datasets make sure there is a field list. Sometimes you
have to click on the refresh fields button (to the right of the ...).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> oh my goodness this is frustrating me....i did what you said, bruce, and
> it
> almost worked. the preview report shows me three values which correspond,
> i
> believe, to the only three fields in my report. see, they're all
> calculated
> fields. the output of the rpt is this:
> Build complete -- 0 errors, 0 warnings
> The data set 'DataSet3' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> The data set 'DataSet4' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> The data set 'DataSet2' contains a definition for the field
> 'Futures_Volume'. This field is missing from the returned result set from
> the
> data source.
> Preview complete -- 0 errors, 3 warnings
> Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
> 4. The report, or the query, is not auto-generating my other fields as it
> did for three that I do see. The 'Futures_Volume' is one of the fields
> that
> was auto-generated for me, and it is in the 1st dataset. Is it that I
> just
> need to manually add in the other fields? Please do let me know what you
> think.
> and thank you, bruce, for helping me through this. i truly do appreciate
> it. i know i am close...and i got the other reports for my server jobs
> and
> one of the other company reports to work. it's just these multi-resultset
> reports are fighting me.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Query parameters and report parameters seem to be the same thing but they
>> are not. RS automatically creates a report parameter for each query
>> parameter but instead you can map the query parameter to a constant.
>> Click
>> on the ... for the dataset, go to the parameters tab. On the right you
>> will
>> see it mapping to the report parameter, click on that and select
>> expression.
>> In expression put = 1 (assuming it is an integert expression) for the
>> first
>> dataset, =2 etc. Then go to report layout, report menu-> report
>> parameters
>> and then delete the report parameters created for you.
>> You are very very close to the solution.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> > last one for a while, bruce, i promise. i've got all 4 datasets in
>> > there,
>> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
>> > 'whole
>> > report' in four small subsets of data. how do i get this to happen on
>> > the
>> > report page automatically without needing user input?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Are you going against SQL Server?
>> >>
>> >> If so, then just select tored procedure for the command type and just
>> >> put
>> >> in
>> >> the name of the stored procedure. Do not put exec in from of it or
>> >> anything
>> >> else. It should detect the parameter and prompt you for it. It should
>> >> also
>> >> create a report parameter as well for you.
>> >>
>> >> Try creating a new dataset and do this from the start. If you continue
>> >> to
>> >> have problems create a new stored procedure just for testing .
>> >>
>> >> create procedure dbo.testproc
>> >> @.PARAM1 int
>> >> as
>> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> return
>> >>
>> >> Get the above procedure to work for you so you know how to call a
>> >> stored
>> >> procedure they way I am telling you (do not use exec).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
>> >> > detecting
>> >> > them. in my 1st dataset i've got cmd type stored procedure and the
>> >> > proc
>> >> > name
>> >> > is in the query string. i assumed i would put the 1st parameter in
>> >> > on
>> >> > the
>> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> > datasets,
>> >> > so
>> >> > i
>> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
>> >> > threw
>> >> > me a
>> >> > 'define query parameters box asking me to put the '1' in it.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> If you are going against SQL Server do not run your stored
>> >> >> procedure
>> >> >> this
>> >> >> way. Pick command type of stored procedure. RS will detect the
>> >> >> parameters.
>> >> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> >> parameters)
>> >> >> then pick text as the command type and do this:
>> >> >> myproc ?
>> >> >>
>> >> >> Create multiple datasets and for each one you should call the
>> >> >> stored
>> >> >> procedure for each one.
>> >> >>
>> >> >> Bruce Loehle-Conger
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> >> > parameters,
>> >> >> > it
>> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> >> > results,
>> >> >> > works
>> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
>> >> >> > RUN
>> >> >> > in
>> >> >> > Data
>> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> >> > designer
>> >> >> > does
>> >> >> > not graphically support the EXEC SQL Construct' but, i hit
>> >> >> > 'OK'
>> >> >> > and
>> >> >> > my
>> >> >> > results are still returned to me. On 'Preview' tab, however, I
>> >> >> > get
>> >> >> > no
>> >> >> > data/results at all.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> >> datasets.
>> >> >> >> Go
>> >> >> >> to
>> >> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> >> dataset,
>> >> >> >> you
>> >> >> >> can click on that and there is a an option for a new.
>> >> >> >>
>> >> >> >> In your stored procedure
>> >> >> >>
>> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> begin
>> >> >> >> --return the first resultset here
>> >> >> >> end
>> >> >> >> etc
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> > Bruce, or somebody else, might you give me an example of how
>> >> >> >> > to
>> >> >> >> > give
>> >> >> >> > the
>> >> >> >> > proc
>> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
>> >> >> >> > display
>> >> >> >> > them?
>> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> > times?
>> >> >> >> > If
>> >> >> >> > so,
>> >> >> >> > how
>> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> parameter
>> >> >> >> >> (you
>> >> >> >> >> can
>> >> >> >> >> make
>> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >>
>> >> >> >> >> Then call it three times in RS with a static value and create
>> >> >> >> >> three
>> >> >> >> >> datasets.
>> >> >> >> >> For instance dataset1
>> >> >> >> >> yourproc 1
>> >> >> >> >>
>> >> >> >> >> Dataset2
>> >> >> >> >> yourproc 2
>> >> >> >> >>
>> >> >> >> >> etc.
>> >> >> >> >>
>> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> resultset
>> >> >> >> >> based
>> >> >> >> >> on
>> >> >> >> >> the
>> >> >> >> >> parameter.
>> >> >> >> >>
>> >> >> >> >> Downside is that your sp is being run three times.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
>> >> >> >> >> > more,
>> >> >> >> >> > please,
>> >> >> >> >> > on
>> >> >> >> >> > the second, possibly third procedure?
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> This is three resultsets. RS does not have the ability to
>> >> >> >> >> >> handle
>> >> >> >> >> >> that.
>> >> >> >> >> >> There
>> >> >> >> >> >> is no work around from RS side. You could create another
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> >> resultsets.
>> >> >> >> >> >>
>> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> call can only return one.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
>> >> >> >> >> >> > simple
>> >> >> >> >> >> > as
>> >> >> >> >> >> > that.
>> >> >> >> >> >> > one
>> >> >> >> >> >> > remaining problem, though. one of my reports is like
>> >> >> >> >> >> > this:
>> >> >> >> >> >> >
>> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> >> > -- -- -- --
>> >> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > #Stocks Volume Total $
>> >> >> >> >> >> > -- -- --
>> >> >> >> >> >> > 333,333 33,333,333 3,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > EndPoint Liquidity #Trades Volume
>> >> >> >> >> >> > Total $
>> >> >> >> >> >> > -- -- -- -- --
>> >> >> >> >> >> > AAAA Add 114,729 21,797,575
>> >> >> >> >> >> > 583,102,631.33
>> >> >> >> >> >> > AAAA Opening 1 27
>> >> >> >> >> >> > 3,412.53
>> >> >> >> >> >> > AAAA Remove 30,836 8,330,843
>> >> >> >> >> >> > 444,521,928.10
>> >> >> >> >> >> > AAAA Route 41 4,543
>> >> >> >> >> >> > 103,291.31
>> >> >> >> >> >> > BBBB Add 26,997 9,940,201
>> >> >> >> >> >> > 178,600,674.78
>> >> >> >> >> >> > BBBB Opening 8,089 1,448,143
>> >> >> >> >> >> > 44,276,419.41
>> >> >> >> >> >> > BBBB Remove 3,406 1,719,403
>> >> >> >> >> >> > 40,267,318.25
>> >> >> >> >> >> > CCCC Add 83,781 22,443,732
>> >> >> >> >> >> > 746,570,071.43
>> >> >> >> >> >> > CCCC Remove 35,756 12,250,359
>> >> >> >> >> >> > 483,329,796.97
>> >> >> >> >> >> > CCCC Route 1,088 244,697
>> >> >> >> >> >> > 6,655,913.26
>> >> >> >> >> >> > DDDD Route 2 62,500
>> >> >> >> >> >> > 2,539,375.00
>> >> >> >> >> >> > DDDD Add 2,354 1,262,589
>> >> >> >> >> >> > 19,136,233.44
>> >> >> >> >> >> > DDDD Remove 258 195,019
>> >> >> >> >> >> > 6,227,451.69
>> >> >> >> >> >> >
>> >> >> >> >> >> > I only receive the top line in the resultset:
>> >> >> >> >> >> >
>> >> >> >> >> >> > Date Total Trades Symbols Traded Total $
>> >> >> >> >> >> > -- -- -- --
>> >> >> >> >> >> > 02/07/2006 333,333 333
>> >> >> >> >> >> > 33,333,333,333.33
>> >> >> >> >> >> >
>> >> >> >> >> >> > I assume this is what you mean when you say it will only
>> >> >> >> >> >> > handle
>> >> >> >> >> >> > the
>> >> >> >> >> >> > 1st
>> >> >> >> >> >> > resultset. All of my reports have multiple 'chunks' in
>> >> >> >> >> >> > the
>> >> >> >> >> >> > body.
>> >> >> >> >> >> > Do
>> >> >> >> >> >> > you
>> >> >> >> >> >> > have any idea how I can achieve this report via
>> >> >> >> >> >> > reporting
>> >> >> >> >> >> > svcs?
>> >> >> >> >> >> > Unfortunately, this is very important. Please do
>> >> >> >> >> >> > advise.
>> >> >> >> >> >> >
>> >> >> >> >> >> > --Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Pick the command type as stored procedure and then just
>> >> >> >> >> >> >> enter
>> >> >> >> >> >> >> the
>> >> >> >> >> >> >> name
>> >> >> >> >> >> >> of
>> >> >> >> >> >> >> the stored procedure. When you click on the ! you
>> >> >> >> >> >> >> should
>> >> >> >> >> >> >> get
>> >> >> >> >> >> >> back|||Bruce, every time I refresh the fields, it pops the 1st three back in the
list. They're the first three in the report, and i guess they're the only
ones in that first resultset. So, I go into dataset 2, 3 and 4, all the same
3 fields are listed. i remove them per dataset, hit refresh, and the same 3
come back.
-- Lynn
"Bruce L-C [MVP]" wrote:
> For each of your datasets make sure there is a field list. Sometimes you
> have to click on the refresh fields button (to the right of the ...).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> > oh my goodness this is frustrating me....i did what you said, bruce, and
> > it
> > almost worked. the preview report shows me three values which correspond,
> > i
> > believe, to the only three fields in my report. see, they're all
> > calculated
> > fields. the output of the rpt is this:
> >
> > Build complete -- 0 errors, 0 warnings
> > The data set 'DataSet3' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > The data set 'DataSet4' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > The data set 'DataSet2' contains a definition for the field
> > 'Futures_Volume'. This field is missing from the returned result set from
> > the
> > data source.
> > Preview complete -- 0 errors, 3 warnings
> >
> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3 and
> > 4. The report, or the query, is not auto-generating my other fields as it
> > did for three that I do see. The 'Futures_Volume' is one of the fields
> > that
> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> > just
> > need to manually add in the other fields? Please do let me know what you
> > think.
> >
> > and thank you, bruce, for helping me through this. i truly do appreciate
> > it. i know i am close...and i got the other reports for my server jobs
> > and
> > one of the other company reports to work. it's just these multi-resultset
> > reports are fighting me.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Query parameters and report parameters seem to be the same thing but they
> >> are not. RS automatically creates a report parameter for each query
> >> parameter but instead you can map the query parameter to a constant.
> >> Click
> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> will
> >> see it mapping to the report parameter, click on that and select
> >> expression.
> >> In expression put = 1 (assuming it is an integert expression) for the
> >> first
> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> parameters
> >> and then delete the report parameters created for you.
> >>
> >> You are very very close to the solution.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> > there,
> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting my
> >> > 'whole
> >> > report' in four small subsets of data. how do i get this to happen on
> >> > the
> >> > report page automatically without needing user input?
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Are you going against SQL Server?
> >> >>
> >> >> If so, then just select tored procedure for the command type and just
> >> >> put
> >> >> in
> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> anything
> >> >> else. It should detect the parameter and prompt you for it. It should
> >> >> also
> >> >> create a report parameter as well for you.
> >> >>
> >> >> Try creating a new dataset and do this from the start. If you continue
> >> >> to
> >> >> have problems create a new stored procedure just for testing .
> >> >>
> >> >> create procedure dbo.testproc
> >> >> @.PARAM1 int
> >> >> as
> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> return
> >> >>
> >> >> Get the above procedure to work for you so you know how to call a
> >> >> stored
> >> >> procedure they way I am telling you (do not use exec).
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is not
> >> >> > detecting
> >> >> > them. in my 1st dataset i've got cmd type stored procedure and the
> >> >> > proc
> >> >> > name
> >> >> > is in the query string. i assumed i would put the 1st parameter in
> >> >> > on
> >> >> > the
> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> > datasets,
> >> >> > so
> >> >> > i
> >> >> > gave it @.ch and the value of 1, but when i attempted to run it, it
> >> >> > threw
> >> >> > me a
> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> procedure
> >> >> >> this
> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> parameters.
> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> parameters)
> >> >> >> then pick text as the command type and do this:
> >> >> >> myproc ?
> >> >> >>
> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> stored
> >> >> >> procedure for each one.
> >> >> >>
> >> >> >> Bruce Loehle-Conger
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> > parameters,
> >> >> >> > it
> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> > results,
> >> >> >> > works
> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> > RUN
> >> >> >> > in
> >> >> >> > Data
> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> > designer
> >> >> >> > does
> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> > 'OK'
> >> >> >> > and
> >> >> >> > my
> >> >> >> > results are still returned to me. On 'Preview' tab, however, I
> >> >> >> > get
> >> >> >> > no
> >> >> >> > data/results at all.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> datasets.
> >> >> >> >> Go
> >> >> >> >> to
> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> dataset,
> >> >> >> >> you
> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >>
> >> >> >> >> In your stored procedure
> >> >> >> >>
> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> begin
> >> >> >> >> --return the first resultset here
> >> >> >> >> end
> >> >> >> >> etc
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> > Bruce, or somebody else, might you give me an example of how
> >> >> >> >> > to
> >> >> >> >> > give
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS will
> >> >> >> >> > display
> >> >> >> >> > them?
> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> > times?
> >> >> >> >> > If
> >> >> >> >> > so,
> >> >> >> >> > how
> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> parameter
> >> >> >> >> >> (you
> >> >> >> >> >> can
> >> >> >> >> >> make
> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >>
> >> >> >> >> >> Then call it three times in RS with a static value and create
> >> >> >> >> >> three
> >> >> >> >> >> datasets.
> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> yourproc 1
> >> >> >> >> >>
> >> >> >> >> >> Dataset2
> >> >> >> >> >> yourproc 2
> >> >> >> >> >>
> >> >> >> >> >> etc.
> >> >> >> >> >>
> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> resultset
> >> >> >> >> >> based
> >> >> >> >> >> on
> >> >> >> >> >> the
> >> >> >> >> >> parameter.
> >> >> >> >> >>
> >> >> >> >> >> Downside is that your sp is being run three times.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
> >> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a little
> >> >> >> >> >> > more,
> >> >> >> >> >> > please,
> >> >> >> >> >> > on
> >> >> >> >> >> > the second, possibly third procedure?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> This is three resultsets. RS does not have the ability to
> >> >> >> >> >> >> handle
> >> >> >> >> >> >> that.
> >> >> >> >> >> >> There
> >> >> >> >> >> >> is no work around from RS side. You could create another
> >> >> >> >> >> >> stored
> >> >> >> >> >> >> procedure
> >> >> >> >> >> >> that calls this one and have it return just one of the
> >> >> >> >> >> >> resultsets.
> >> >> >> >> >> >>
> >> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
> >> >> >> >> >> >> stored
> >> >> >> >> >> >> procedure
> >> >> >> >> >> >> call can only return one.
> >> >> >> >> >> >>
> >> >> >> >> >> >>
> >> >> >> >> >> >> --
> >> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >> >>
> >> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
> >> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
> >> >> >> >> >> >> > simple
> >> >> >> >> >> >> > as
> >> >> >> >> >> >> > that.
> >> >> >> >> >> >> > one
> >> >> >> >> >> >> > remaining problem, though. one of my reports is like|||Ok, what is happening is that it is detecting the first resultset. What you
can do it is add the fields manually. In the field list add a new field and
name it correctly for what will be coming back. (Right mouse click in the
field list).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> Bruce, every time I refresh the fields, it pops the 1st three back in the
> list. They're the first three in the report, and i guess they're the only
> ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> same
> 3 fields are listed. i remove them per dataset, hit refresh, and the same
> 3
> come back.
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> For each of your datasets make sure there is a field list. Sometimes you
>> have to click on the refresh fields button (to the right of the ...).
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> > oh my goodness this is frustrating me....i did what you said, bruce,
>> > and
>> > it
>> > almost worked. the preview report shows me three values which
>> > correspond,
>> > i
>> > believe, to the only three fields in my report. see, they're all
>> > calculated
>> > fields. the output of the rpt is this:
>> >
>> > Build complete -- 0 errors, 0 warnings
>> > The data set 'DataSet3' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > The data set 'DataSet4' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > The data set 'DataSet2' contains a definition for the field
>> > 'Futures_Volume'. This field is missing from the returned result set
>> > from
>> > the
>> > data source.
>> > Preview complete -- 0 errors, 3 warnings
>> >
>> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
>> > and
>> > 4. The report, or the query, is not auto-generating my other fields as
>> > it
>> > did for three that I do see. The 'Futures_Volume' is one of the fields
>> > that
>> > was auto-generated for me, and it is in the 1st dataset. Is it that I
>> > just
>> > need to manually add in the other fields? Please do let me know what
>> > you
>> > think.
>> >
>> > and thank you, bruce, for helping me through this. i truly do
>> > appreciate
>> > it. i know i am close...and i got the other reports for my server jobs
>> > and
>> > one of the other company reports to work. it's just these
>> > multi-resultset
>> > reports are fighting me.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Query parameters and report parameters seem to be the same thing but
>> >> they
>> >> are not. RS automatically creates a report parameter for each query
>> >> parameter but instead you can map the query parameter to a constant.
>> >> Click
>> >> on the ... for the dataset, go to the parameters tab. On the right you
>> >> will
>> >> see it mapping to the report parameter, click on that and select
>> >> expression.
>> >> In expression put = 1 (assuming it is an integert expression) for the
>> >> first
>> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> parameters
>> >> and then delete the report parameters created for you.
>> >>
>> >> You are very very close to the solution.
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
>> >> > there,
>> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
>> >> > my
>> >> > 'whole
>> >> > report' in four small subsets of data. how do i get this to happen
>> >> > on
>> >> > the
>> >> > report page automatically without needing user input?
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Are you going against SQL Server?
>> >> >>
>> >> >> If so, then just select tored procedure for the command type and
>> >> >> just
>> >> >> put
>> >> >> in
>> >> >> the name of the stored procedure. Do not put exec in from of it or
>> >> >> anything
>> >> >> else. It should detect the parameter and prompt you for it. It
>> >> >> should
>> >> >> also
>> >> >> create a report parameter as well for you.
>> >> >>
>> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> continue
>> >> >> to
>> >> >> have problems create a new stored procedure just for testing .
>> >> >>
>> >> >> create procedure dbo.testproc
>> >> >> @.PARAM1 int
>> >> >> as
>> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> return
>> >> >>
>> >> >> Get the above procedure to work for you so you know how to call a
>> >> >> stored
>> >> >> procedure they way I am telling you (do not use exec).
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
>> >> >> > not
>> >> >> > detecting
>> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
>> >> >> > the
>> >> >> > proc
>> >> >> > name
>> >> >> > is in the query string. i assumed i would put the 1st parameter
>> >> >> > in
>> >> >> > on
>> >> >> > the
>> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> >> > datasets,
>> >> >> > so
>> >> >> > i
>> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
>> >> >> > it
>> >> >> > threw
>> >> >> > me a
>> >> >> > 'define query parameters box asking me to put the '1' in it.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> procedure
>> >> >> >> this
>> >> >> >> way. Pick command type of stored procedure. RS will detect the
>> >> >> >> parameters.
>> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
>> >> >> >> parameters)
>> >> >> >> then pick text as the command type and do this:
>> >> >> >> myproc ?
>> >> >> >>
>> >> >> >> Create multiple datasets and for each one you should call the
>> >> >> >> stored
>> >> >> >> procedure for each one.
>> >> >> >>
>> >> >> >> Bruce Loehle-Conger
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
>> >> >> >> > parameters,
>> >> >> >> > it
>> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
>> >> >> >> > results,
>> >> >> >> > works
>> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
>> >> >> >> > RUN
>> >> >> >> > in
>> >> >> >> > Data
>> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
>> >> >> >> > designer
>> >> >> >> > does
>> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
>> >> >> >> > 'OK'
>> >> >> >> > and
>> >> >> >> > my
>> >> >> >> > results are still returned to me. On 'Preview' tab, however,
>> >> >> >> > I
>> >> >> >> > get
>> >> >> >> > no
>> >> >> >> > data/results at all.
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Yes, you are calling it three times. In RS you create three
>> >> >> >> >> datasets.
>> >> >> >> >> Go
>> >> >> >> >> to
>> >> >> >> >> the dataset tab and there is a combo box with the name of the
>> >> >> >> >> dataset,
>> >> >> >> >> you
>> >> >> >> >> can click on that and there is a an option for a new.
>> >> >> >> >>
>> >> >> >> >> In your stored procedure
>> >> >> >> >>
>> >> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> >> begin
>> >> >> >> >> --return the first resultset here
>> >> >> >> >> end
>> >> >> >> >> etc
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> >> > Bruce, or somebody else, might you give me an example of
>> >> >> >> >> > how
>> >> >> >> >> > to
>> >> >> >> >> > give
>> >> >> >> >> > the
>> >> >> >> >> > proc
>> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
>> >> >> >> >> > will
>> >> >> >> >> > display
>> >> >> >> >> > them?
>> >> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> >> > times?
>> >> >> >> >> > If
>> >> >> >> >> > so,
>> >> >> >> >> > how
>> >> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> >> parameter
>> >> >> >> >> >> (you
>> >> >> >> >> >> can
>> >> >> >> >> >> make
>> >> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >> >>
>> >> >> >> >> >> Then call it three times in RS with a static value and
>> >> >> >> >> >> create
>> >> >> >> >> >> three
>> >> >> >> >> >> datasets.
>> >> >> >> >> >> For instance dataset1
>> >> >> >> >> >> yourproc 1
>> >> >> >> >> >>
>> >> >> >> >> >> Dataset2
>> >> >> >> >> >> yourproc 2
>> >> >> >> >> >>
>> >> >> >> >> >> etc.
>> >> >> >> >> >>
>> >> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> >> resultset
>> >> >> >> >> >> based
>> >> >> >> >> >> on
>> >> >> >> >> >> the
>> >> >> >> >> >> parameter.
>> >> >> >> >> >>
>> >> >> >> >> >> Downside is that your sp is being run three times.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:E8E34B6C-A36A-4576-BE8C-AB61866EEC80@.microsoft.com...
>> >> >> >> >> >> > Bruce, I'm not sure I follow. Can you elaborate a
>> >> >> >> >> >> > little
>> >> >> >> >> >> > more,
>> >> >> >> >> >> > please,
>> >> >> >> >> >> > on
>> >> >> >> >> >> > the second, possibly third procedure?
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> This is three resultsets. RS does not have the ability
>> >> >> >> >> >> >> to
>> >> >> >> >> >> >> handle
>> >> >> >> >> >> >> that.
>> >> >> >> >> >> >> There
>> >> >> >> >> >> >> is no work around from RS side. You could create
>> >> >> >> >> >> >> another
>> >> >> >> >> >> >> stored
>> >> >> >> >> >> >> procedure
>> >> >> >> >> >> >> that calls this one and have it return just one of the
>> >> >> >> >> >> >> resultsets.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> RS can deal with multiple datasets quite well, but each
>> >> >> >> >> >> >> stored
>> >> >> >> >> >> >> procedure
>> >> >> >> >> >> >> call can only return one.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> --
>> >> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in
>> >> >> >> >> >> >> message
>> >> >> >> >> >> >> news:E1AFA910-1FF4-4DC8-A3F0-FC1EADE8DFD5@.microsoft.com...
>> >> >> >> >> >> >> > oh, bruce, that is great. I can't believe it was as
>> >> >> >> >> >> >> > simple
>> >> >> >> >> >> >> > as
>> >> >> >> >> >> >> > that.
>> >> >> >> >> >> >> > one
>> >> >> >> >> >> >> > remaining problem, though. one of my reports is like|||yep, i had tried this last week, but it failed w/ a cpl different errors. i
will try it again right now.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Ok, what is happening is that it is detecting the first resultset. What you
> can do it is add the fields manually. In the field list add a new field and
> name it correctly for what will be coming back. (Right mouse click in the
> field list).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> > Bruce, every time I refresh the fields, it pops the 1st three back in the
> > list. They're the first three in the report, and i guess they're the only
> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> > same
> > 3 fields are listed. i remove them per dataset, hit refresh, and the same
> > 3
> > come back.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> For each of your datasets make sure there is a field list. Sometimes you
> >> have to click on the refresh fields button (to the right of the ...).
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> > oh my goodness this is frustrating me....i did what you said, bruce,
> >> > and
> >> > it
> >> > almost worked. the preview report shows me three values which
> >> > correspond,
> >> > i
> >> > believe, to the only three fields in my report. see, they're all
> >> > calculated
> >> > fields. the output of the rpt is this:
> >> >
> >> > Build complete -- 0 errors, 0 warnings
> >> > The data set 'DataSet3' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet4' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet2' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > Preview complete -- 0 errors, 3 warnings
> >> >
> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
> >> > and
> >> > 4. The report, or the query, is not auto-generating my other fields as
> >> > it
> >> > did for three that I do see. The 'Futures_Volume' is one of the fields
> >> > that
> >> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> >> > just
> >> > need to manually add in the other fields? Please do let me know what
> >> > you
> >> > think.
> >> >
> >> > and thank you, bruce, for helping me through this. i truly do
> >> > appreciate
> >> > it. i know i am close...and i got the other reports for my server jobs
> >> > and
> >> > one of the other company reports to work. it's just these
> >> > multi-resultset
> >> > reports are fighting me.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Query parameters and report parameters seem to be the same thing but
> >> >> they
> >> >> are not. RS automatically creates a report parameter for each query
> >> >> parameter but instead you can map the query parameter to a constant.
> >> >> Click
> >> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> >> will
> >> >> see it mapping to the report parameter, click on that and select
> >> >> expression.
> >> >> In expression put = 1 (assuming it is an integert expression) for the
> >> >> first
> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> parameters
> >> >> and then delete the report parameters created for you.
> >> >>
> >> >> You are very very close to the solution.
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> >> > there,
> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
> >> >> > my
> >> >> > 'whole
> >> >> > report' in four small subsets of data. how do i get this to happen
> >> >> > on
> >> >> > the
> >> >> > report page automatically without needing user input?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Are you going against SQL Server?
> >> >> >>
> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> just
> >> >> >> put
> >> >> >> in
> >> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> >> anything
> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> should
> >> >> >> also
> >> >> >> create a report parameter as well for you.
> >> >> >>
> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> continue
> >> >> >> to
> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >>
> >> >> >> create procedure dbo.testproc
> >> >> >> @.PARAM1 int
> >> >> >> as
> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> return
> >> >> >>
> >> >> >> Get the above procedure to work for you so you know how to call a
> >> >> >> stored
> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> > not
> >> >> >> > detecting
> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > name
> >> >> >> > is in the query string. i assumed i would put the 1st parameter
> >> >> >> > in
> >> >> >> > on
> >> >> >> > the
> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> > datasets,
> >> >> >> > so
> >> >> >> > i
> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
> >> >> >> > it
> >> >> >> > threw
> >> >> >> > me a
> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> procedure
> >> >> >> >> this
> >> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> >> parameters.
> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> >> parameters)
> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> myproc ?
> >> >> >> >>
> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> stored
> >> >> >> >> procedure for each one.
> >> >> >> >>
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> >> > parameters,
> >> >> >> >> > it
> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> >> > results,
> >> >> >> >> > works
> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> >> > RUN
> >> >> >> >> > in
> >> >> >> >> > Data
> >> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> >> > designer
> >> >> >> >> > does
> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> >> > 'OK'
> >> >> >> >> > and
> >> >> >> >> > my
> >> >> >> >> > results are still returned to me. On 'Preview' tab, however,
> >> >> >> >> > I
> >> >> >> >> > get
> >> >> >> >> > no
> >> >> >> >> > data/results at all.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> >> datasets.
> >> >> >> >> >> Go
> >> >> >> >> >> to
> >> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> >> dataset,
> >> >> >> >> >> you
> >> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >> >>
> >> >> >> >> >> In your stored procedure
> >> >> >> >> >>
> >> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> >> begin
> >> >> >> >> >> --return the first resultset here
> >> >> >> >> >> end
> >> >> >> >> >> etc
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
> >> >> >> >> >> > how
> >> >> >> >> >> > to
> >> >> >> >> >> > give
> >> >> >> >> >> > the
> >> >> >> >> >> > proc
> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
> >> >> >> >> >> > will
> >> >> >> >> >> > display
> >> >> >> >> >> > them?
> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> >> > times?
> >> >> >> >> >> > If
> >> >> >> >> >> > so,
> >> >> >> >> >> > how
> >> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> >> parameter
> >> >> >> >> >> >> (you
> >> >> >> >> >> >> can
> >> >> >> >> >> >> make
> >> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then call it three times in RS with a static value and
> >> >> >> >> >> >> create
> >> >> >> >> >> >> three
> >> >> >> >> >> >> datasets.
> >> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> >> yourproc 1
> >> >> >> >> >> >>
> >> >> >> >> >> >> Dataset2
> >> >> >> >> >> >> yourproc 2
> >> >> >> >> >> >>
> >> >> >> >> >> >> etc.
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> >> resultset
> >> >> >> >> >> >> based
> >> >> >> >> >> >> on
> >> >> >> >> >> >> the
> >> >> >> >> >> >> parameter.|||Bruce, i apologize, this is going on and on. I attempt to add the fields
in...just as they are in dataset1, except with new values, and it fails with
this:
'The properties for the currently selected item are not valid. Please
correct all errors before continuing.'
Now, all of these values are calculated...Volume (sum of another value), #
of Trades (count of another value), etc...but the same thing applies to
dataset 1, and those fields are listed as database fields, not calculated
fields. please can you tell me what the right way to do this is?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Ok, what is happening is that it is detecting the first resultset. What you
> can do it is add the fields manually. In the field list add a new field and
> name it correctly for what will be coming back. (Right mouse click in the
> field list).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> > Bruce, every time I refresh the fields, it pops the 1st three back in the
> > list. They're the first three in the report, and i guess they're the only
> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all the
> > same
> > 3 fields are listed. i remove them per dataset, hit refresh, and the same
> > 3
> > come back.
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> For each of your datasets make sure there is a field list. Sometimes you
> >> have to click on the refresh fields button (to the right of the ...).
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> > oh my goodness this is frustrating me....i did what you said, bruce,
> >> > and
> >> > it
> >> > almost worked. the preview report shows me three values which
> >> > correspond,
> >> > i
> >> > believe, to the only three fields in my report. see, they're all
> >> > calculated
> >> > fields. the output of the rpt is this:
> >> >
> >> > Build complete -- 0 errors, 0 warnings
> >> > The data set 'DataSet3' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet4' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > The data set 'DataSet2' contains a definition for the field
> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> > from
> >> > the
> >> > data source.
> >> > Preview complete -- 0 errors, 3 warnings
> >> >
> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2, 3
> >> > and
> >> > 4. The report, or the query, is not auto-generating my other fields as
> >> > it
> >> > did for three that I do see. The 'Futures_Volume' is one of the fields
> >> > that
> >> > was auto-generated for me, and it is in the 1st dataset. Is it that I
> >> > just
> >> > need to manually add in the other fields? Please do let me know what
> >> > you
> >> > think.
> >> >
> >> > and thank you, bruce, for helping me through this. i truly do
> >> > appreciate
> >> > it. i know i am close...and i got the other reports for my server jobs
> >> > and
> >> > one of the other company reports to work. it's just these
> >> > multi-resultset
> >> > reports are fighting me.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Query parameters and report parameters seem to be the same thing but
> >> >> they
> >> >> are not. RS automatically creates a report parameter for each query
> >> >> parameter but instead you can map the query parameter to a constant.
> >> >> Click
> >> >> on the ... for the dataset, go to the parameters tab. On the right you
> >> >> will
> >> >> see it mapping to the report parameter, click on that and select
> >> >> expression.
> >> >> In expression put = 1 (assuming it is an integert expression) for the
> >> >> first
> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> parameters
> >> >> and then delete the report parameters created for you.
> >> >>
> >> >> You are very very close to the solution.
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets in
> >> >> > there,
> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each, getting
> >> >> > my
> >> >> > 'whole
> >> >> > report' in four small subsets of data. how do i get this to happen
> >> >> > on
> >> >> > the
> >> >> > report page automatically without needing user input?
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Are you going against SQL Server?
> >> >> >>
> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> just
> >> >> >> put
> >> >> >> in
> >> >> >> the name of the stored procedure. Do not put exec in from of it or
> >> >> >> anything
> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> should
> >> >> >> also
> >> >> >> create a report parameter as well for you.
> >> >> >>
> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> continue
> >> >> >> to
> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >>
> >> >> >> create procedure dbo.testproc
> >> >> >> @.PARAM1 int
> >> >> >> as
> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> return
> >> >> >>
> >> >> >> Get the above procedure to work for you so you know how to call a
> >> >> >> stored
> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> > not
> >> >> >> > detecting
> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure and
> >> >> >> > the
> >> >> >> > proc
> >> >> >> > name
> >> >> >> > is in the query string. i assumed i would put the 1st parameter
> >> >> >> > in
> >> >> >> > on
> >> >> >> > the
> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> > datasets,
> >> >> >> > so
> >> >> >> > i
> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run it,
> >> >> >> > it
> >> >> >> > threw
> >> >> >> > me a
> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> procedure
> >> >> >> >> this
> >> >> >> >> way. Pick command type of stored procedure. RS will detect the
> >> >> >> >> parameters.
> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format for
> >> >> >> >> parameters)
> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> myproc ?
> >> >> >> >>
> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> stored
> >> >> >> >> procedure for each one.
> >> >> >> >>
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st one
> >> >> >> >> > parameters,
> >> >> >> >> > it
> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of the
> >> >> >> >> > results,
> >> >> >> >> > works
> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I hit
> >> >> >> >> > RUN
> >> >> >> >> > in
> >> >> >> >> > Data
> >> >> >> >> > tab it returns an error: SQL Syntax Errors Encountered...The
> >> >> >> >> > designer
> >> >> >> >> > does
> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i hit
> >> >> >> >> > 'OK'
> >> >> >> >> > and
> >> >> >> >> > my
> >> >> >> >> > results are still returned to me. On 'Preview' tab, however,
> >> >> >> >> > I
> >> >> >> >> > get
> >> >> >> >> > no
> >> >> >> >> > data/results at all.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> Yes, you are calling it three times. In RS you create three
> >> >> >> >> >> datasets.
> >> >> >> >> >> Go
> >> >> >> >> >> to
> >> >> >> >> >> the dataset tab and there is a combo box with the name of the
> >> >> >> >> >> dataset,
> >> >> >> >> >> you
> >> >> >> >> >> can click on that and there is a an option for a new.
> >> >> >> >> >>
> >> >> >> >> >> In your stored procedure
> >> >> >> >> >>
> >> >> >> >> >> if @.WHICHRESULTSET = 1
> >> >> >> >> >> begin
> >> >> >> >> >> --return the first resultset here
> >> >> >> >> >> end
> >> >> >> >> >> etc
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
> >> >> >> >> >> > how
> >> >> >> >> >> > to
> >> >> >> >> >> > give
> >> >> >> >> >> > the
> >> >> >> >> >> > proc
> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that RS
> >> >> >> >> >> > will
> >> >> >> >> >> > display
> >> >> >> >> >> > them?
> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
> >> >> >> >> >> > times?
> >> >> >> >> >> > If
> >> >> >> >> >> > so,
> >> >> >> >> >> > how
> >> >> >> >> >> > would i call the 3 procs in RS?
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Configure your existing stored procedure to accept a
> >> >> >> >> >> >> parameter
> >> >> >> >> >> >> (you
> >> >> >> >> >> >> can
> >> >> >> >> >> >> make
> >> >> >> >> >> >> it optional so that it doesn't break existing code).
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then call it three times in RS with a static value and
> >> >> >> >> >> >> create
> >> >> >> >> >> >> three
> >> >> >> >> >> >> datasets.
> >> >> >> >> >> >> For instance dataset1
> >> >> >> >> >> >> yourproc 1
> >> >> >> >> >> >>
> >> >> >> >> >> >> Dataset2
> >> >> >> >> >> >> yourproc 2
> >> >> >> >> >> >>
> >> >> >> >> >> >> etc.
> >> >> >> >> >> >>
> >> >> >> >> >> >> Then in your stored procedure return the appropriate
> >> >> >> >> >> >> resultset
> >> >> >> >> >> >> based
> >> >> >> >> >> >> on
> >> >> >> >> >> >> the
> >> >> >> >> >> >> parameter.|||Just because they are calculated in the stored procedure does not mean they
are calculated when you manually add them to the field list. You put the
name same as the name of the field being returned and mark them as database
field. If you name them appropriately and say they are are database fields
it will work.
So, let's say you are in dataset2 which is called the stored procedure with
a parameter value of 2. When you click the execute the data comes back. Plus
you can see the name of the fields in the dataset (but not in the field
list). Add then appropriate field names to the field list.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> Bruce, i apologize, this is going on and on. I attempt to add the fields
> in...just as they are in dataset1, except with new values, and it fails
> with
> this:
> 'The properties for the currently selected item are not valid. Please
> correct all errors before continuing.'
> Now, all of these values are calculated...Volume (sum of another value), #
> of Trades (count of another value), etc...but the same thing applies to
> dataset 1, and those fields are listed as database fields, not calculated
> fields. please can you tell me what the right way to do this is?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Ok, what is happening is that it is detecting the first resultset. What
>> you
>> can do it is add the fields manually. In the field list add a new field
>> and
>> name it correctly for what will be coming back. (Right mouse click in the
>> field list).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
>> > Bruce, every time I refresh the fields, it pops the 1st three back in
>> > the
>> > list. They're the first three in the report, and i guess they're the
>> > only
>> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
>> > the
>> > same
>> > 3 fields are listed. i remove them per dataset, hit refresh, and the
>> > same
>> > 3
>> > come back.
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> For each of your datasets make sure there is a field list. Sometimes
>> >> you
>> >> have to click on the refresh fields button (to the right of the ...).
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> >> > oh my goodness this is frustrating me....i did what you said,
>> >> > bruce,
>> >> > and
>> >> > it
>> >> > almost worked. the preview report shows me three values which
>> >> > correspond,
>> >> > i
>> >> > believe, to the only three fields in my report. see, they're all
>> >> > calculated
>> >> > fields. the output of the rpt is this:
>> >> >
>> >> > Build complete -- 0 errors, 0 warnings
>> >> > The data set 'DataSet3' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > The data set 'DataSet4' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > The data set 'DataSet2' contains a definition for the field
>> >> > 'Futures_Volume'. This field is missing from the returned result set
>> >> > from
>> >> > the
>> >> > data source.
>> >> > Preview complete -- 0 errors, 3 warnings
>> >> >
>> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
>> >> > 3
>> >> > and
>> >> > 4. The report, or the query, is not auto-generating my other fields
>> >> > as
>> >> > it
>> >> > did for three that I do see. The 'Futures_Volume' is one of the
>> >> > fields
>> >> > that
>> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
>> >> > I
>> >> > just
>> >> > need to manually add in the other fields? Please do let me know
>> >> > what
>> >> > you
>> >> > think.
>> >> >
>> >> > and thank you, bruce, for helping me through this. i truly do
>> >> > appreciate
>> >> > it. i know i am close...and i got the other reports for my server
>> >> > jobs
>> >> > and
>> >> > one of the other company reports to work. it's just these
>> >> > multi-resultset
>> >> > reports are fighting me.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> Query parameters and report parameters seem to be the same thing
>> >> >> but
>> >> >> they
>> >> >> are not. RS automatically creates a report parameter for each query
>> >> >> parameter but instead you can map the query parameter to a
>> >> >> constant.
>> >> >> Click
>> >> >> on the ... for the dataset, go to the parameters tab. On the right
>> >> >> you
>> >> >> will
>> >> >> see it mapping to the report parameter, click on that and select
>> >> >> expression.
>> >> >> In expression put = 1 (assuming it is an integert expression) for
>> >> >> the
>> >> >> first
>> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> >> parameters
>> >> >> and then delete the report parameters created for you.
>> >> >>
>> >> >> You are very very close to the solution.
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
>> >> >> > in
>> >> >> > there,
>> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
>> >> >> > getting
>> >> >> > my
>> >> >> > 'whole
>> >> >> > report' in four small subsets of data. how do i get this to
>> >> >> > happen
>> >> >> > on
>> >> >> > the
>> >> >> > report page automatically without needing user input?
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Are you going against SQL Server?
>> >> >> >>
>> >> >> >> If so, then just select tored procedure for the command type and
>> >> >> >> just
>> >> >> >> put
>> >> >> >> in
>> >> >> >> the name of the stored procedure. Do not put exec in from of it
>> >> >> >> or
>> >> >> >> anything
>> >> >> >> else. It should detect the parameter and prompt you for it. It
>> >> >> >> should
>> >> >> >> also
>> >> >> >> create a report parameter as well for you.
>> >> >> >>
>> >> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> >> continue
>> >> >> >> to
>> >> >> >> have problems create a new stored procedure just for testing .
>> >> >> >>
>> >> >> >> create procedure dbo.testproc
>> >> >> >> @.PARAM1 int
>> >> >> >> as
>> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> >> return
>> >> >> >>
>> >> >> >> Get the above procedure to work for you so you know how to call
>> >> >> >> a
>> >> >> >> stored
>> >> >> >> procedure they way I am telling you (do not use exec).
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
>> >> >> >> > not
>> >> >> >> > detecting
>> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
>> >> >> >> > and
>> >> >> >> > the
>> >> >> >> > proc
>> >> >> >> > name
>> >> >> >> > is in the query string. i assumed i would put the 1st
>> >> >> >> > parameter
>> >> >> >> > in
>> >> >> >> > on
>> >> >> >> > the
>> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
>> >> >> >> > datasets,
>> >> >> >> > so
>> >> >> >> > i
>> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
>> >> >> >> > it,
>> >> >> >> > it
>> >> >> >> > threw
>> >> >> >> > me a
>> >> >> >> > 'define query parameters box asking me to put the '1' in it.
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> >> procedure
>> >> >> >> >> this
>> >> >> >> >> way. Pick command type of stored procedure. RS will detect
>> >> >> >> >> the
>> >> >> >> >> parameters.
>> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
>> >> >> >> >> for
>> >> >> >> >> parameters)
>> >> >> >> >> then pick text as the command type and do this:
>> >> >> >> >> myproc ?
>> >> >> >> >>
>> >> >> >> >> Create multiple datasets and for each one you should call the
>> >> >> >> >> stored
>> >> >> >> >> procedure for each one.
>> >> >> >> >>
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
>> >> >> >> >> > one
>> >> >> >> >> > parameters,
>> >> >> >> >> > it
>> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
>> >> >> >> >> > the
>> >> >> >> >> > results,
>> >> >> >> >> > works
>> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
>> >> >> >> >> > hit
>> >> >> >> >> > RUN
>> >> >> >> >> > in
>> >> >> >> >> > Data
>> >> >> >> >> > tab it returns an error: SQL Syntax Errors
>> >> >> >> >> > Encountered...The
>> >> >> >> >> > designer
>> >> >> >> >> > does
>> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
>> >> >> >> >> > hit
>> >> >> >> >> > 'OK'
>> >> >> >> >> > and
>> >> >> >> >> > my
>> >> >> >> >> > results are still returned to me. On 'Preview' tab,
>> >> >> >> >> > however,
>> >> >> >> >> > I
>> >> >> >> >> > get
>> >> >> >> >> > no
>> >> >> >> >> > data/results at all.
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> Yes, you are calling it three times. In RS you create
>> >> >> >> >> >> three
>> >> >> >> >> >> datasets.
>> >> >> >> >> >> Go
>> >> >> >> >> >> to
>> >> >> >> >> >> the dataset tab and there is a combo box with the name of
>> >> >> >> >> >> the
>> >> >> >> >> >> dataset,
>> >> >> >> >> >> you
>> >> >> >> >> >> can click on that and there is a an option for a new.
>> >> >> >> >> >>
>> >> >> >> >> >> In your stored procedure
>> >> >> >> >> >>
>> >> >> >> >> >> if @.WHICHRESULTSET = 1
>> >> >> >> >> >> begin
>> >> >> >> >> >> --return the first resultset here
>> >> >> >> >> >> end
>> >> >> >> >> >> etc
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:81E3A442-6694-442D-B151-F083E4750ADB@.microsoft.com...
>> >> >> >> >> >> > Bruce, or somebody else, might you give me an example of
>> >> >> >> >> >> > how
>> >> >> >> >> >> > to
>> >> >> >> >> >> > give
>> >> >> >> >> >> > the
>> >> >> >> >> >> > proc
>> >> >> >> >> >> > 3 parameters, producing three resultsets in a way that
>> >> >> >> >> >> > RS
>> >> >> >> >> >> > will
>> >> >> >> >> >> > display
>> >> >> >> >> >> > them?
>> >> >> >> >> >> > Or, am I giving it three parameters and calling it three
>> >> >> >> >> >> > times?
>> >> >> >> >> >> > If
>> >> >> >> >> >> > so,
>> >> >> >> >> >> > how
>> >> >> >> >> >> > would i call the 3 procs in RS?
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Configure your existing stored procedure to accept a
>> >> >> >> >> >> >> parameter
>> >> >> >> >> >> >> (you
>> >> >> >> >> >> >> can
>> >> >> >> >> >> >> make
>> >> >> >> >> >> >> it optional so that it doesn't break existing code).
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Then call it three times in RS with a static value and
>> >> >> >> >> >> >> create
>> >> >> >> >> >> >> three
>> >> >> >> >> >> >> datasets.
>> >> >> >> >> >> >> For instance dataset1
>> >> >> >> >> >> >> yourproc 1
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Dataset2
>> >> >> >> >> >> >> yourproc 2
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> etc.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Then in your stored procedure return the appropriate
>> >> >> >> >> >> >> resultset
>> >> >> >> >> >> >> based
>> >> >> >> >> >> >> on
>> >> >> >> >> >> >> the
>> >> >> >> >> >> >> parameter.|||i'm sorry, bruce, possibly this is too burdensome for you. i'm just not
getting beyond this. i delete the fields, add the new ones, the thing runs
when i hit the run...but i hit refresh and the old fields come back, the new
ones i just added are gone. even if i save everything when they're
there...they just keep blowing out.
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||i think i may be almost there, bruce. hopefully...
i've added all the fields from the diff datasets into the rpt, 4 diff
tables. now when i go to preview, it doesn't show me anything, but up top
left there is a parameter box asking me for a value. and on the far right
there's a 'view report' button.
what should i do?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||d:\...\...\blah report.rdl The data set name is missing in the data region
â'data set nameâ'.
d:\...\...\blah report.rdl The data set â'DataSet2â' contains a definition
for the field â'Futures_Volumeâ'. This field is missing from the returned
result set from the data source.
'Futures_Volume' was/is in the 1st dataset, i deleted from the other three,
adding all the correct fields manually. each rpt runs fine in Data tab when i
hit the run exclamation point. but if i try to preview, i get those two
erros, the second one i get three times for each dataset (2, 3 and 4).
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||The datasets 2, 3 and 4 contain definition for futures volume...the field is
missing from the returned resultset from the data source.
possibly i'm looking at this wrong, and i should have four separate
datasets, each with different group of fields, and a single report in which
all fields (from all 4 datasets) are combined?
-- Lynn
"Bruce L-C [MVP]" wrote:
> Just because they are calculated in the stored procedure does not mean they
> are calculated when you manually add them to the field list. You put the
> name same as the name of the field being returned and mark them as database
> field. If you name them appropriately and say they are are database fields
> it will work.
> So, let's say you are in dataset2 which is called the stored procedure with
> a parameter value of 2. When you click the execute the data comes back. Plus
> you can see the name of the fields in the dataset (but not in the field
> list). Add then appropriate field names to the field list.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
> > Bruce, i apologize, this is going on and on. I attempt to add the fields
> > in...just as they are in dataset1, except with new values, and it fails
> > with
> > this:
> >
> > 'The properties for the currently selected item are not valid. Please
> > correct all errors before continuing.'
> >
> > Now, all of these values are calculated...Volume (sum of another value), #
> > of Trades (count of another value), etc...but the same thing applies to
> > dataset 1, and those fields are listed as database fields, not calculated
> > fields. please can you tell me what the right way to do this is?
> > -- Lynn
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Ok, what is happening is that it is detecting the first resultset. What
> >> you
> >> can do it is add the fields manually. In the field list add a new field
> >> and
> >> name it correctly for what will be coming back. (Right mouse click in the
> >> field list).
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
> >> > Bruce, every time I refresh the fields, it pops the 1st three back in
> >> > the
> >> > list. They're the first three in the report, and i guess they're the
> >> > only
> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
> >> > the
> >> > same
> >> > 3 fields are listed. i remove them per dataset, hit refresh, and the
> >> > same
> >> > 3
> >> > come back.
> >> > -- Lynn
> >> >
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> For each of your datasets make sure there is a field list. Sometimes
> >> >> you
> >> >> have to click on the refresh fields button (to the right of the ...).
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
> >> >> > oh my goodness this is frustrating me....i did what you said,
> >> >> > bruce,
> >> >> > and
> >> >> > it
> >> >> > almost worked. the preview report shows me three values which
> >> >> > correspond,
> >> >> > i
> >> >> > believe, to the only three fields in my report. see, they're all
> >> >> > calculated
> >> >> > fields. the output of the rpt is this:
> >> >> >
> >> >> > Build complete -- 0 errors, 0 warnings
> >> >> > The data set 'DataSet3' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet4' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > The data set 'DataSet2' contains a definition for the field
> >> >> > 'Futures_Volume'. This field is missing from the returned result set
> >> >> > from
> >> >> > the
> >> >> > data source.
> >> >> > Preview complete -- 0 errors, 3 warnings
> >> >> >
> >> >> > Now, I created the4 datasets, the parameter for each is simply 1, 2,
> >> >> > 3
> >> >> > and
> >> >> > 4. The report, or the query, is not auto-generating my other fields
> >> >> > as
> >> >> > it
> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
> >> >> > fields
> >> >> > that
> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it that
> >> >> > I
> >> >> > just
> >> >> > need to manually add in the other fields? Please do let me know
> >> >> > what
> >> >> > you
> >> >> > think.
> >> >> >
> >> >> > and thank you, bruce, for helping me through this. i truly do
> >> >> > appreciate
> >> >> > it. i know i am close...and i got the other reports for my server
> >> >> > jobs
> >> >> > and
> >> >> > one of the other company reports to work. it's just these
> >> >> > multi-resultset
> >> >> > reports are fighting me.
> >> >> > -- Lynn
> >> >> >
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> Query parameters and report parameters seem to be the same thing
> >> >> >> but
> >> >> >> they
> >> >> >> are not. RS automatically creates a report parameter for each query
> >> >> >> parameter but instead you can map the query parameter to a
> >> >> >> constant.
> >> >> >> Click
> >> >> >> on the ... for the dataset, go to the parameters tab. On the right
> >> >> >> you
> >> >> >> will
> >> >> >> see it mapping to the report parameter, click on that and select
> >> >> >> expression.
> >> >> >> In expression put = 1 (assuming it is an integert expression) for
> >> >> >> the
> >> >> >> first
> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
> >> >> >> parameters
> >> >> >> and then delete the report parameters created for you.
> >> >> >>
> >> >> >> You are very very close to the solution.
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
> >> >> >> > last one for a while, bruce, i promise. i've got all 4 datasets
> >> >> >> > in
> >> >> >> > there,
> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
> >> >> >> > getting
> >> >> >> > my
> >> >> >> > 'whole
> >> >> >> > report' in four small subsets of data. how do i get this to
> >> >> >> > happen
> >> >> >> > on
> >> >> >> > the
> >> >> >> > report page automatically without needing user input?
> >> >> >> > -- Lynn
> >> >> >> >
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> Are you going against SQL Server?
> >> >> >> >>
> >> >> >> >> If so, then just select tored procedure for the command type and
> >> >> >> >> just
> >> >> >> >> put
> >> >> >> >> in
> >> >> >> >> the name of the stored procedure. Do not put exec in from of it
> >> >> >> >> or
> >> >> >> >> anything
> >> >> >> >> else. It should detect the parameter and prompt you for it. It
> >> >> >> >> should
> >> >> >> >> also
> >> >> >> >> create a report parameter as well for you.
> >> >> >> >>
> >> >> >> >> Try creating a new dataset and do this from the start. If you
> >> >> >> >> continue
> >> >> >> >> to
> >> >> >> >> have problems create a new stored procedure just for testing .
> >> >> >> >>
> >> >> >> >> create procedure dbo.testproc
> >> >> >> >> @.PARAM1 int
> >> >> >> >> as
> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
> >> >> >> >> return
> >> >> >> >>
> >> >> >> >> Get the above procedure to work for you so you know how to call
> >> >> >> >> a
> >> >> >> >> stored
> >> >> >> >> procedure they way I am telling you (do not use exec).
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs is
> >> >> >> >> > not
> >> >> >> >> > detecting
> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
> >> >> >> >> > and
> >> >> >> >> > the
> >> >> >> >> > proc
> >> >> >> >> > name
> >> >> >> >> > is in the query string. i assumed i would put the 1st
> >> >> >> >> > parameter
> >> >> >> >> > in
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3 other
> >> >> >> >> > datasets,
> >> >> >> >> > so
> >> >> >> >> > i
> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
> >> >> >> >> > it,
> >> >> >> >> > it
> >> >> >> >> > threw
> >> >> >> >> > me a
> >> >> >> >> > 'define query parameters box asking me to put the '1' in it.
> >> >> >> >> > -- Lynn
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> If you are going against SQL Server do not run your stored
> >> >> >> >> >> procedure
> >> >> >> >> >> this
> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
> >> >> >> >> >> the
> >> >> >> >> >> parameters.
> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
> >> >> >> >> >> for
> >> >> >> >> >> parameters)
> >> >> >> >> >> then pick text as the command type and do this:
> >> >> >> >> >> myproc ?
> >> >> >> >> >>
> >> >> >> >> >> Create multiple datasets and for each one you should call the
> >> >> >> >> >> stored
> >> >> >> >> >> procedure for each one.
> >> >> >> >> >>
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >>
> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
> >> >> >> >> >> > one
> >> >> >> >> >> > parameters,
> >> >> >> >> >> > it
> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
> >> >> >> >> >> > the
> >> >> >> >> >> > results,
> >> >> >> >> >> > works
> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when I
> >> >> >> >> >> > hit
> >> >> >> >> >> > RUN
> >> >> >> >> >> > in
> >> >> >> >> >> > Data
> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
> >> >> >> >> >> > Encountered...The
> >> >> >> >> >> > designer
> >> >> >> >> >> > does
> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but, i
> >> >> >> >> >> > hit
> >> >> >> >> >> > 'OK'
> >> >> >> >> >> > and
> >> >> >> >> >> > my
> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
> >> >> >> >> >> > however,
> >> >> >> >> >> > I
> >> >> >> >> >> > get
> >> >> >> >> >> > no
> >> >> >> >> >> > data/results at all.
> >> >> >> >> >> > -- Lynn
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >> >
> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create|||You are trying to learn many things all at once. You cannot combine datasets
together however you can use the First aggegate funtion (think of it like
Sum except it returns the first value which if the dataset has a single row
is the data you want.
Normally with multiple datasets you would have multiple table controls on
your form (or a list control).
Not sure if you solved the problem of it wiping out your field list. If so,
here is a work around. Make sure your stored procedure works. Then go to
layout view. Show the dataset/fieldlist from there and delete / add fields
to the field list from there.
Note, when wanting to essentially join data into a single dataset another
technique is to use subreports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Lynn" <Lynn@.discussions.microsoft.com> wrote in message
news:8781DA41-EE73-4E1D-8195-42A8355BF10E@.microsoft.com...
> The datasets 2, 3 and 4 contain definition for futures volume...the field
> is
> missing from the returned resultset from the data source.
> possibly i'm looking at this wrong, and i should have four separate
> datasets, each with different group of fields, and a single report in
> which
> all fields (from all 4 datasets) are combined?
> -- Lynn
>
> "Bruce L-C [MVP]" wrote:
>> Just because they are calculated in the stored procedure does not mean
>> they
>> are calculated when you manually add them to the field list. You put the
>> name same as the name of the field being returned and mark them as
>> database
>> field. If you name them appropriately and say they are are database
>> fields
>> it will work.
>> So, let's say you are in dataset2 which is called the stored procedure
>> with
>> a parameter value of 2. When you click the execute the data comes back.
>> Plus
>> you can see the name of the fields in the dataset (but not in the field
>> list). Add then appropriate field names to the field list.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> news:56F8F3F3-94C0-4E6F-9385-423CB80090EF@.microsoft.com...
>> > Bruce, i apologize, this is going on and on. I attempt to add the
>> > fields
>> > in...just as they are in dataset1, except with new values, and it fails
>> > with
>> > this:
>> >
>> > 'The properties for the currently selected item are not valid. Please
>> > correct all errors before continuing.'
>> >
>> > Now, all of these values are calculated...Volume (sum of another
>> > value), #
>> > of Trades (count of another value), etc...but the same thing applies
>> > to
>> > dataset 1, and those fields are listed as database fields, not
>> > calculated
>> > fields. please can you tell me what the right way to do this is?
>> > -- Lynn
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Ok, what is happening is that it is detecting the first resultset.
>> >> What
>> >> you
>> >> can do it is add the fields manually. In the field list add a new
>> >> field
>> >> and
>> >> name it correctly for what will be coming back. (Right mouse click in
>> >> the
>> >> field list).
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> news:D5EEA5C8-DB3A-4DB3-ADE6-D8092373DC46@.microsoft.com...
>> >> > Bruce, every time I refresh the fields, it pops the 1st three back
>> >> > in
>> >> > the
>> >> > list. They're the first three in the report, and i guess they're
>> >> > the
>> >> > only
>> >> > ones in that first resultset. So, I go into dataset 2, 3 and 4, all
>> >> > the
>> >> > same
>> >> > 3 fields are listed. i remove them per dataset, hit refresh, and
>> >> > the
>> >> > same
>> >> > 3
>> >> > come back.
>> >> > -- Lynn
>> >> >
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> For each of your datasets make sure there is a field list.
>> >> >> Sometimes
>> >> >> you
>> >> >> have to click on the refresh fields button (to the right of the
>> >> >> ...).
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> news:17C0ED6F-0E4A-4033-A1A2-A841AA7BBECF@.microsoft.com...
>> >> >> > oh my goodness this is frustrating me....i did what you said,
>> >> >> > bruce,
>> >> >> > and
>> >> >> > it
>> >> >> > almost worked. the preview report shows me three values which
>> >> >> > correspond,
>> >> >> > i
>> >> >> > believe, to the only three fields in my report. see, they're all
>> >> >> > calculated
>> >> >> > fields. the output of the rpt is this:
>> >> >> >
>> >> >> > Build complete -- 0 errors, 0 warnings
>> >> >> > The data set 'DataSet3' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > The data set 'DataSet4' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > The data set 'DataSet2' contains a definition for the field
>> >> >> > 'Futures_Volume'. This field is missing from the returned result
>> >> >> > set
>> >> >> > from
>> >> >> > the
>> >> >> > data source.
>> >> >> > Preview complete -- 0 errors, 3 warnings
>> >> >> >
>> >> >> > Now, I created the4 datasets, the parameter for each is simply 1,
>> >> >> > 2,
>> >> >> > 3
>> >> >> > and
>> >> >> > 4. The report, or the query, is not auto-generating my other
>> >> >> > fields
>> >> >> > as
>> >> >> > it
>> >> >> > did for three that I do see. The 'Futures_Volume' is one of the
>> >> >> > fields
>> >> >> > that
>> >> >> > was auto-generated for me, and it is in the 1st dataset. Is it
>> >> >> > that
>> >> >> > I
>> >> >> > just
>> >> >> > need to manually add in the other fields? Please do let me know
>> >> >> > what
>> >> >> > you
>> >> >> > think.
>> >> >> >
>> >> >> > and thank you, bruce, for helping me through this. i truly do
>> >> >> > appreciate
>> >> >> > it. i know i am close...and i got the other reports for my
>> >> >> > server
>> >> >> > jobs
>> >> >> > and
>> >> >> > one of the other company reports to work. it's just these
>> >> >> > multi-resultset
>> >> >> > reports are fighting me.
>> >> >> > -- Lynn
>> >> >> >
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> Query parameters and report parameters seem to be the same thing
>> >> >> >> but
>> >> >> >> they
>> >> >> >> are not. RS automatically creates a report parameter for each
>> >> >> >> query
>> >> >> >> parameter but instead you can map the query parameter to a
>> >> >> >> constant.
>> >> >> >> Click
>> >> >> >> on the ... for the dataset, go to the parameters tab. On the
>> >> >> >> right
>> >> >> >> you
>> >> >> >> will
>> >> >> >> see it mapping to the report parameter, click on that and select
>> >> >> >> expression.
>> >> >> >> In expression put = 1 (assuming it is an integert expression)
>> >> >> >> for
>> >> >> >> the
>> >> >> >> first
>> >> >> >> dataset, =2 etc. Then go to report layout, report menu-> report
>> >> >> >> parameters
>> >> >> >> and then delete the report parameters created for you.
>> >> >> >>
>> >> >> >> You are very very close to the solution.
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> news:61E1ED5C-B204-4024-9DC4-82635AEBD912@.microsoft.com...
>> >> >> >> > last one for a while, bruce, i promise. i've got all 4
>> >> >> >> > datasets
>> >> >> >> > in
>> >> >> >> > there,
>> >> >> >> > each asks me for a parameter, i put 1,2,3 and 4 into each,
>> >> >> >> > getting
>> >> >> >> > my
>> >> >> >> > 'whole
>> >> >> >> > report' in four small subsets of data. how do i get this to
>> >> >> >> > happen
>> >> >> >> > on
>> >> >> >> > the
>> >> >> >> > report page automatically without needing user input?
>> >> >> >> > -- Lynn
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> Are you going against SQL Server?
>> >> >> >> >>
>> >> >> >> >> If so, then just select tored procedure for the command type
>> >> >> >> >> and
>> >> >> >> >> just
>> >> >> >> >> put
>> >> >> >> >> in
>> >> >> >> >> the name of the stored procedure. Do not put exec in from of
>> >> >> >> >> it
>> >> >> >> >> or
>> >> >> >> >> anything
>> >> >> >> >> else. It should detect the parameter and prompt you for it.
>> >> >> >> >> It
>> >> >> >> >> should
>> >> >> >> >> also
>> >> >> >> >> create a report parameter as well for you.
>> >> >> >> >>
>> >> >> >> >> Try creating a new dataset and do this from the start. If you
>> >> >> >> >> continue
>> >> >> >> >> to
>> >> >> >> >> have problems create a new stored procedure just for testing
>> >> >> >> >> .
>> >> >> >> >>
>> >> >> >> >> create procedure dbo.testproc
>> >> >> >> >> @.PARAM1 int
>> >> >> >> >> as
>> >> >> >> >> select 'Parameter passed in = ' + @.PARAM1 as Message
>> >> >> >> >> return
>> >> >> >> >>
>> >> >> >> >> Get the above procedure to work for you so you know how to
>> >> >> >> >> call
>> >> >> >> >> a
>> >> >> >> >> stored
>> >> >> >> >> procedure they way I am telling you (do not use exec).
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> news:9B089D7B-1F23-465B-B443-08BD09469A3E@.microsoft.com...
>> >> >> >> >> > i'm sorry, bruce, but where do i define the parameters? rs
>> >> >> >> >> > is
>> >> >> >> >> > not
>> >> >> >> >> > detecting
>> >> >> >> >> > them. in my 1st dataset i've got cmd type stored procedure
>> >> >> >> >> > and
>> >> >> >> >> > the
>> >> >> >> >> > proc
>> >> >> >> >> > name
>> >> >> >> >> > is in the query string. i assumed i would put the 1st
>> >> >> >> >> > parameter
>> >> >> >> >> > in
>> >> >> >> >> > on
>> >> >> >> >> > the
>> >> >> >> >> > parameters tab and then do the same for 2, 3 and 4 on 3
>> >> >> >> >> > other
>> >> >> >> >> > datasets,
>> >> >> >> >> > so
>> >> >> >> >> > i
>> >> >> >> >> > gave it @.ch and the value of 1, but when i attempted to run
>> >> >> >> >> > it,
>> >> >> >> >> > it
>> >> >> >> >> > threw
>> >> >> >> >> > me a
>> >> >> >> >> > 'define query parameters box asking me to put the '1' in
>> >> >> >> >> > it.
>> >> >> >> >> > -- Lynn
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> If you are going against SQL Server do not run your stored
>> >> >> >> >> >> procedure
>> >> >> >> >> >> this
>> >> >> >> >> >> way. Pick command type of stored procedure. RS will detect
>> >> >> >> >> >> the
>> >> >> >> >> >> parameters.
>> >> >> >> >> >> If going against ODBC or OLEDB driver (which uses ? format
>> >> >> >> >> >> for
>> >> >> >> >> >> parameters)
>> >> >> >> >> >> then pick text as the command type and do this:
>> >> >> >> >> >> myproc ?
>> >> >> >> >> >>
>> >> >> >> >> >> Create multiple datasets and for each one you should call
>> >> >> >> >> >> the
>> >> >> >> >> >> stored
>> >> >> >> >> >> procedure for each one.
>> >> >> >> >> >>
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >>
>> >> >> >> >> >> "Lynn" <Lynn@.discussions.microsoft.com> wrote in message
>> >> >> >> >> >> news:79CA374D-729B-4181-8F45-5D61FCF30F28@.microsoft.com...
>> >> >> >> >> >> > And, if I blow away the 2nd dataset and just give my 1st
>> >> >> >> >> >> > one
>> >> >> >> >> >> > parameters,
>> >> >> >> >> >> > it
>> >> >> >> >> >> > almost works. EXEC db.dbo.procname 1 for chunk one of
>> >> >> >> >> >> > the
>> >> >> >> >> >> > results,
>> >> >> >> >> >> > works
>> >> >> >> >> >> > just fine. if i change the parameter to 2, 3 or 4, when
>> >> >> >> >> >> > I
>> >> >> >> >> >> > hit
>> >> >> >> >> >> > RUN
>> >> >> >> >> >> > in
>> >> >> >> >> >> > Data
>> >> >> >> >> >> > tab it returns an error: SQL Syntax Errors
>> >> >> >> >> >> > Encountered...The
>> >> >> >> >> >> > designer
>> >> >> >> >> >> > does
>> >> >> >> >> >> > not graphically support the EXEC SQL Construct' but,
>> >> >> >> >> >> > i
>> >> >> >> >> >> > hit
>> >> >> >> >> >> > 'OK'
>> >> >> >> >> >> > and
>> >> >> >> >> >> > my
>> >> >> >> >> >> > results are still returned to me. On 'Preview' tab,
>> >> >> >> >> >> > however,
>> >> >> >> >> >> > I
>> >> >> >> >> >> > get
>> >> >> >> >> >> > no
>> >> >> >> >> >> > data/results at all.
>> >> >> >> >> >> > -- Lynn
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >> >
>> >> >> >> >> >> >> Yes, you are calling it three times. In RS you create
Subscribe to:
Posts (Atom)