Losing exceptions generated within Stored Procedures in MS SQL Server 2012 about pyodbc HOT 6 CLOSED

@githubmlai - Essentially, yes. You'd just keep calling nextset() until it returned False. The exception, if any, would either get thrown immediately or on one of the nextset() calls.

from pyodbc.

I notice that your stored procedure does not include

SET NOCOUNT ON;

as the first executable statement. Doing so could very likely avoid the issue.

from pyodbc.

I'm experiencing a similar issue. When pyodbc executes the following stored procedure, the error (divide by 0) is not caught

Here is the stored proc

IF OBJECT_ID('dbo.spSwallowError') IS NULL
EXEC ('CREATE PROCEDURE dbo.spSwallowError AS SET NOCOUNT ON;');

GO

ALTER PROCEDURE dbo.spSwallowError
AS
BEGIN
SELECT 1;
SELECT 1 / 0;

 END;

from pyodbc.

@githubmlai - The SELECT 1; statement has already put a result set into the "pipeline" back to the client, so you won't see the exception until you call nextset() to try and retrieve the second result set:

>>> import pyodbc
>>> conn = pyodbc.connect("DSN=myDb;")
>>> crsr = conn.cursor()
>>> crsr.execute("{CALL dbo.spSwallowError}")
<pyodbc.Cursor object at 0x03041218>
>>> rows = crsr.fetchall()
>>> rows
[(1, )]
>>> crsr.nextset()
Traceback (most recent call last):
  File "<pyshell#6>", line 1, in <module>
    crsr.nextset()
pyodbc.DataError: ('22012', '[22012] [Microsoft][SQL Server Native Client 10.0][SQL Server]Divide by zero error encountered. (8134) (SQLMoreResults)')

from pyodbc.

Thanks! Any suggestions on how to guarantee pyodbc rethrows the error? Should I always fetch all the rows and then call next set repeatedly?

from pyodbc.

ERROR_NUMBER() AS ErrorNumber
ERROR_SEVERITY() AS ErrorSeverity
ERROR_STATE() AS ErrorState
ERROR_PROCEDURE() AS ErrorProcedure
ERROR_LINE() AS ErrorLine
ERROR_MESSAGE() AS ErrorMessage;

how to get these parameters in pyodbc using python? can anyone help me out please!!!!

from pyodbc.