|
I am having a SP with nested Cursors. The SP is called inside a Perl script. While running the Perl script for the first time the SP is exiting with error:
The SP runs fine when attempted twice/thrice. Could anyone please provide me some inputs?
(comments are locked)
|
|
This is probably a driver level bug. Without seeing the source - either to your Perl script neither to the underlying ODBC layer, it's difficult to tell. However, from my experience of ODBC, there isn't any requirement to call anything in between SQLExecute / SQLExecDirect and SQLFetch - so I'm not sure what the issue is. Sorry to not be much help. I agree. That's not a standard error on the server side of things.
Jun 09 '10 at 09:06 AM
Grant Fritchey ♦♦
The SSMS is running fine without any error. It seems to me that the ODBC is having the bug. Any help on how to zero down the issue.
Jun 09 '10 at 11:54 AM
Pratyus 1
(comments are locked)
|
First thing to check would be to determine whether Perl/Odbc Driver causes it or not by executing procedure from SSMS. If it returns error then it is not Perl, but the procedure itself. Without looking at your proc there is no way to tell, but it is possible that if there is something wrong with the proc when it is executed for the first time, you will get better clue from the error information in SSMS results pane.