Calling Stored Procedures - mkleehammer/pyodbc GitHub Wiki
pyodbc does not currently implement the optional .callproc
method. (It has been investigated.)
However, ODBC defines a {CALL ...} escape sequence that should be supported by well-behaved ODBC drivers.
For example, to call a stored procedure named "usp_NoParameters" that takes no parameters, we can do
crsr.execute("{CALL usp_NoParameters}")
To call a stored procedure that takes only input parameters, we can do
params = (14, "Dinsdale")
crsr.execute("{CALL usp_UpdateFirstName (?,?)}", params)
Output Parameters and Return Values
Because pyodbc does not have .callproc
we need to use a workaround for retrieving the values of output parameters and return values. The specific method will depend on what your particular ODBC driver supports, but for Microsoft's ODBC drivers for SQL Server we can use an "anonymous code block" to EXEC the stored procedure and then SELECT the output parameters and/or return values. For example, for the SQL Server stored procedure
CREATE PROCEDURE [dbo].[test_for_pyodbc]
@param_in nvarchar(max) = N'',
@param_out nvarchar(max) OUTPUT
AS
BEGIN
-- the following statement emits a rowcount as the first "result"
SELECT 1 AS foo INTO #junk;
-- since this procedure does not start with
-- SET NOCOUNT ON;
-- we will need to use that statement at the beginning of our
-- anonymous code block in Python
-- set output parameter
SELECT @param_out = N'Output parameter value: You said "' + @param_in + N'".';
-- also return a couple of result sets
SELECT N'SP result set 1, row 1' AS foo
UNION ALL
SELECT N'SP result set 1, row 2' AS foo;
SELECT N'SP result set 2, row 1' AS bar
UNION ALL
SELECT N'SP result set 2, row 2' AS bar;
END
our Python code can do this
sql = """\
SET NOCOUNT ON;
DECLARE @out nvarchar(max);
EXEC [dbo].[test_for_pyodbc] @param_in = ?, @param_out = @out OUTPUT;
SELECT @out AS the_output;
"""
params = ("Burma!", )
crsr.execute(sql, params)
rows = crsr.fetchall()
while True:
print(rows)
if crsr.nextset():
rows = crsr.fetchall()
else:
break
to produce this:
[('SP result set 1, row 1', ), ('SP result set 1, row 2', )]
[('SP result set 2, row 1', ), ('SP result set 2, row 2', )]
[('Output parameter value: You said "Burma!".', )]
Notice that the result set(s) created by the stored procedure are returned first, followed by the result set with the output parameter(s) as returned by the SELECT statement in the anonymous code block passed to the pyodbc .execute
method.
Similarly, for a SQL Server stored procedure with a RETURN value we can use something like this:
sql = """\
SET NOCOUNT ON;
DECLARE @rv int;
EXEC @rv = [dbo].[another_test_sp];
SELECT @rv AS return_value;
"""
crsr.execute(sql)
return_value = crsr.fetchval()