capturing the output from a stored procedure into a report

I have a stored procedure that takes some parameters. I can execute it
in the data tab in vb.net and get my results. How do i take these
results and form a report? Is there a way to capture the fields that
are returned in order to drop them into a report?
I'm doing all this in vb.net.
Thanks.Are you using the report designer and the data tab? Does the stored
procedure execute and return data from the data tab? If so, sometimes
executing the stored procedure does not fill the field list. Try clicking on
the refresh fields button (look to the right of the ... , it looks like the
fresh button for IE. Hover over it and it will tell you what the button is
for). If this doesn't cause the field list to fill in then you can put in
the fields manually in the list. Right mouse click in the field list, add
field and give it the name of the field name.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"muris" <rmuris@.hotmail.com> wrote in message
news:1112374203.464263.41490@.z14g2000cwz.googlegroups.com...
> I have a stored procedure that takes some parameters. I can execute it
> in the data tab in vb.net and get my results. How do i take these
> results and form a report? Is there a way to capture the fields that
> are returned in order to drop them into a report?
> I'm doing all this in vb.net.
> Thanks.
>|||hitting the refresh button worked!! Thank you.

Capturing Execution Results

Hi All

When running an SSIS Package from BIDS, we get to see the "Progress" tab which explains us the progress of the SSIS Package. During production, is there any way to capture this log. I am interested in using this as a log file for each run of my SSIS package.

Thanks,

S Suresh

Have you tried to enable logging in the package?

Thanks,
Ovidiu Burlacu

|||

I tried loging. But I want some Progress Reporting similar to one we see in the Execution Results. Any thoughts on this?

Thanks,

S Suresh

|||

Suresh S wrote:

I tried loging. But I want some Progress Reporting similar to one we see in the Execution Results. Any thoughts on this?

Thanks,

S Suresh

The information in the logfile is exactly the same as in teh Prgress tab.

|||

Suresh,

Just in case, here they are talking about package loging and not about SQL Server Agent loging. Package loging as it is being said, it will provide what you need.

Rafael Salas

|||

Hello,

I am not sure, I understand the difference between the two and would appreciate it if you could clarify how to implement package logging as opposed to SQL Server Agent Logging. I have enabled the package logging property, however, would like to obtain a file that is in the same format as that displayed in the 'Execution Results/Progress' tab.

Thanks,

Subah.

|||

Subah wrote:

Hello,

I am not sure, I understand the difference between the two and would appreciate it if you could clarify how to implement package logging as opposed to SQL Server Agent Logging. I have enabled the package logging property, however, would like to obtain a file that is in the same format as that displayed in the 'Execution Results/Progress' tab.

Thanks,

Subah.

You won't get a file that looks the same as that tab, but you WILL get a file with the same information (actually that's not strictly true - I know of one thing you get extra in the 'Execution Results/Progress' tab but its not something you need). It just won't be presented as nicely as it is in the 'Execution Results/Progress' tab, that's all.

-Jamie

|||Thanks Jamie. I guess I am on the right track then. :-)

Capturing Execution Results

Hi All

When running an SSIS Package from BIDS, we get to see the "Progress" tab which explains us the progress of the SSIS Package. During production, is there any way to capture this log. I am interested in using this as a log file for each run of my SSIS package.

Thanks,

S Suresh

Have you tried to enable logging in the package?

Thanks,
Ovidiu Burlacu

|||

I tried loging. But I want some Progress Reporting similar to one we see in the Execution Results. Any thoughts on this?

Thanks,

S Suresh

|||

Suresh S wrote:

I tried loging. But I want some Progress Reporting similar to one we see in the Execution Results. Any thoughts on this?

Thanks,

S Suresh

The information in the logfile is exactly the same as in teh Prgress tab.

|||

Suresh,

Just in case, here they are talking about package loging and not about SQL Server Agent loging. Package loging as it is being said, it will provide what you need.

Rafael Salas

|||

Hello,

I am not sure, I understand the difference between the two and would appreciate it if you could clarify how to implement package logging as opposed to SQL Server Agent Logging. I have enabled the package logging property, however, would like to obtain a file that is in the same format as that displayed in the 'Execution Results/Progress' tab.

Thanks,

Subah.

|||

Subah wrote:

Hello,

I am not sure, I understand the difference between the two and would appreciate it if you could clarify how to implement package logging as opposed to SQL Server Agent Logging. I have enabled the package logging property, however, would like to obtain a file that is in the same format as that displayed in the 'Execution Results/Progress' tab.

Thanks,

Subah.

You won't get a file that looks the same as that tab, but you WILL get a file with the same information (actually that's not strictly true - I know of one thing you get extra in the 'Execution Results/Progress' tab but its not something you need). It just won't be presented as nicely as it is in the 'Execution Results/Progress' tab, that's all.

-Jamie

|||Thanks Jamie. I guess I am on the right track then. :-)

Can't use TAB key in SQL Pane

Hello folks,
When working in Visual Studio 2005 Reporting Services, I have been
cursed with a small problem that I have run out of remedy ideas for.
On the data tab of a report I am no longer able to use the TAB key on
the keyboard to format my SQL. I say no longer because i was using
Visual Studio 2003 until recently and this problem did not exist. If
I hit TAB when writing code in the SQL pane the cursor just moves to
the next action object (button) as if on a form. The only band-aid
solution has been to write all my code in a SQL Management Studio
query window and than copy/paste it into the report SQL pane but this
is a nuisance, especially for short,easy report queries and when
returning to existing reports for upgrades or bug fixes. Another
workaround has been to copy a single TAB from Notepad or any other app
and paste the tab in the SQL pane when needed, but than i have to re-
copy it each time if i copy something else. Any ideas or
sympathizers, I would love to hear from you.
Thanks, and here is an example of what I mean.
/* this is what I am stuck with */
SELECT
foo.Column1,
foo.Column2
FROM
dbo.foo
/* this is what I want */
SELECT
foo.Column1,
foo.Column2
FROM
dbo.fooNo way t o use tab, you need to use spacebar with space, I understand if it
is a small query you can do it, but if it is a big query will be very
tedious.
what otherway you can do is, just click "generic query builder" and again
click what it does is, it indends automatically.
Amarnath
"Skilliam" wrote:
> Hello folks,
> When working in Visual Studio 2005 Reporting Services, I have been
> cursed with a small problem that I have run out of remedy ideas for.
> On the data tab of a report I am no longer able to use the TAB key on
> the keyboard to format my SQL. I say no longer because i was using
> Visual Studio 2003 until recently and this problem did not exist. If
> I hit TAB when writing code in the SQL pane the cursor just moves to
> the next action object (button) as if on a form. The only band-aid
> solution has been to write all my code in a SQL Management Studio
> query window and than copy/paste it into the report SQL pane but this
> is a nuisance, especially for short,easy report queries and when
> returning to existing reports for upgrades or bug fixes. Another
> workaround has been to copy a single TAB from Notepad or any other app
> and paste the tab in the SQL pane when needed, but than i have to re-
> copy it each time if i copy something else. Any ideas or
> sympathizers, I would love to hear from you.
> Thanks, and here is an example of what I mean.
> /* this is what I am stuck with */
> SELECT
> foo.Column1,
> foo.Column2
> FROM
> dbo.foo
> /* this is what I want */
> SELECT
> foo.Column1,
> foo.Column2
> FROM
> dbo.foo
>