October 29, 2003 at 12:03 pm
One of my steps in my DTS package fires off a stored procedure. I do some error handling within the SP. How can I see the error that I raise? It isn't in the output file. Is there a way of getting this out or do I need to use another strategy?
Thanks,
John
October 29, 2003 at 12:04 pm
Sorry, I didn't mean to hit the submit button again. Can an administrator delete this extra post?
Thanks,
John
October 29, 2003 at 3:32 pm
Do you have a return statement in you stored procedure? You can use the return statement to return a failure condition.
If you don't want to fail the package, use an output parameter, or a simple select at the end of the procedure.
Hope this helps
Phill Carter
--------------------
Colt 45 - the original point and click interface
--------------------
Colt 45 - the original point and click interface
October 30, 2003 at 6:57 am
I do not currently have a return statement in my SP. I am just raising an error. I will try putting in a return statement to see if it accomplishes what I am trying to do.
Thanks for the suggestion!
John
October 30, 2003 at 8:59 am
The Execute SQL task in DTS ignores errors returned from stored procedures. I commonly will use a Return value or an output parameter to retrieve the error value and assign it to a global variable. Then I use an On Complete workflow to an ActiveX Script Task where I evaluate the Global Variable and set the task to success or failure as needed.
Steve Hughes
Magenic Technologies
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply