How to create stored procedure data set in BIRT?

Hello All I need your help,
I am very new to Actuate BIRT reports. I have a requirement to call sybase(12.5.0.3) stored procedures in BIRT reports. Report may have more than stored procs. and at run time depends on the user's selection the report should take appropriate stored proc and show the results.

I have established the jdbc database connection. I am NOT able to create a new stored proc dataset. I have gone through help contents provided.

Does anyone know exact steps what to do in order to complete the set up? Stored proc has five parameters and all of them will be supplied through user input and should select different datasets.

Code:
exec ActivitySummary @ActivityId='WEB', @Accout1='NANO', @REGIONFLAG='US', @Date='02/21/2008', @INTERNATIONAL= 'Y'

I put following while creating stored proc. data set and I get nothing in output column (not even column names) or in preview results.

Code:
{Call ActivitySummary('WEB', 'NANO', 'US', '02/21/2008', 'Y')}

I am able to use "SQL Select Query" but that is not my requirement. I need to create data set using "SQL Stored Procedure Query".

Any help will be appreciated.

Thanks,
Sanket

Find more posts tagged with

Comments

ericpias

I had a similar problem SYBASE.

To get around it, I created a new data set of type SQL Select Query (instead of SQL Stored Proc Query) and then used something like 'execute proc_name ? ? ? ...' for the query. I hooked up my parameters and it worked.

Don't know if this will work for you, but it might.

fae1

we have identical problems. We tried using execute storeproc... but that does not work either. Any ideas?

scariou29

Hello,

Finnaly did you find a solution for your problem.
I have the same problem ,store procedure SQL SERVER which finish with a select , ok with SQL SERVER, but no way with Birt, problem for Birt is that my stored proc does not return a ResultSet Object ?

If you have an idea ...

AustinJim

I was having the same problem with stored procedures in SQL Server. The problem turned out to be that the proc was writing messages to the output which seems to have confused BIRT or the jdbc driver. I fixed it by putting SET NOCOUNT ON at the top of the proc.