SQL Server Stored Procedure Problem
Moderators: chulett, rschirm, roy
-
nandakumar
- Participant
- Posts: 4
- Joined: Sat Nov 10, 2007 9:23 am
SQL Server Stored Procedure Problem
Hi ,
Hi ,
I am trying to execute stored procedure using few input parameters getting from source table . And i need to get an output from the stored procedure. I need to pass input parameters dynamically. Is anyone can help me?
Thanks,
Nanda
Hi ,
I am trying to execute stored procedure using few input parameters getting from source table . And i need to get an output from the stored procedure. I need to pass input parameters dynamically. Is anyone can help me?
Thanks,
Nanda
-
nandakumar
- Participant
- Posts: 4
- Joined: Sat Nov 10, 2007 9:23 am
Re: SQL Server Stored Procedure Problem
Thanks for your reply chulet
I am using ODBC stage to extract data from the table and need to pass that
values as inputs to my stored procedure in the next step.
If i got 100 rows from the table means i need to get 100 rows as output from the stored procedure
I am using ODBC stage to extract data from the table and need to pass that
values as inputs to my stored procedure in the next step.
If i got 100 rows from the table means i need to get 100 rows as output from the stored procedure
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
From what stage type are you calling the stored procedure? ODBC? This would mean that you are calling the stored procedure once for each row extracted from the table, presumable expecting one row of "result" in each case? However you have not provided sufficient specific detail to permit more accurate analysis than that. What does the stored procedure do? Have you imported its definition?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
nandakumar
- Participant
- Posts: 4
- Joined: Sat Nov 10, 2007 9:23 am
ray.wurlod wrote:From what stage type are you calling the stored procedure? ODBC? This would mean that you are calling the stored procedure once for each row extracted from the table, presumable expecting one row of ...
Ray,
I am extracting data from the table using ODBC stage ,then the next step is to call the stored proc using the out data from ODBC.
-
nandakumar
- Participant
- Posts: 4
- Joined: Sat Nov 10, 2007 9:23 am
chulett wrote:Version 7.5.x includes a Stored Procedure stage, have you tried that? Or ODBC? More details, please. ...
Culett,
STP stage is not supporting the SQL Server stored procedure. We can use DRS stage to call stored proc and can load data into table. But in my case after extracting data from the table and (using ODBC stage here for extraction) next step need to give this data as input to my stored proc and get an output values from stored proc . Can we handle this problem in DataStage?
Couldn't recall which 'S' it supported... Sybase. You'll need to use the ODBC stage:
1. Import the metadata from your SP in the Manager.
2. Set the Update Action in the ODBC stage to 'Call stored procedure'.
3. Set the 'Stored procedure name' by pointing to the imported metadata.
I personally don't have much truck with stored procedures in ETL. Another option would be for you to rebuild the functionality that it provides into the job itself so the procedure is no longer needed.
1. Import the metadata from your SP in the Manager.
2. Set the Update Action in the ODBC stage to 'Call stored procedure'.
3. Set the 'Stored procedure name' by pointing to the imported metadata.
I personally don't have much truck with stored procedures in ETL. Another option would be for you to rebuild the functionality that it provides into the job itself so the procedure is no longer needed.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Posting this I noticed that you also said 'and get output values' as well. That you will not be able to do. I believe that if your sproc does this, you will not be able to leverage it as a target, but then as I said I don't use stored procedures in my ETL.
If that's the case, you will then need to recreate the functionality in your job.
If that's the case, you will then need to recreate the functionality in your job.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
