Installation guide

4. Accessing Popular Databases

Due to the way the SQL Server Native Client works, the data from the result sets

is sent to the client before the data for the output parameters. See e.g. the IBM

Knowledge Center or StackOverflow for details.

Since mxODBC returns the output parameters immediately after executing a

statement via the

cursor.callproc(), cursors.execute() or

cursor.executedirect() APIs, the changes send to the client after the result

sets are not seen by mxODBC.

The Python DB-API 2.0 also does not allow for the output parameters to be

fetched later, e.g. after the result sets have been fetched using the

cursor.fetch*() APIs.

As a result, output and input/output parameters in stored procedures which

generate and return result sets are not updated.

Work-around:

The work-around for this is to return the output parameter values as additional

result sets and then using the

cursor.nextset() method to switch through the

available result sets.

MS SQL Server ODBC Driver for SQL Server 2000

Tested with MS SQL Server ODBC driver from MDAC 2.8 SP1.

If you still use SQL Server 2000, please get the latest ODBC driver for SQL Server

from the Micrsoft MDAC package. MDAC 2.8 SP1 can be downloaded from this

page:

http://www.microsoft.com/downloads/details.aspx?familyid=78CAC895-EFC2-

4F8E-A9E0-3A1AFBD5922E&displaylang=en

Configuring the SQL Server ODBC Driver Client Network Protocol

When configuring an ODBC data source using the MDAC SQL Server ODBC

Driver you can choose the protocol by clicking on the Client Configuration button

on the second wizard page.

Note that the MDAC ODBC drivers do not support shared memory access. Use

named pipes as best connectivity option when connecting to a database server

running on the same machine.

MS SQL Server Native Client for Linux

Homepage:

http://msdn.microsoft.com/en-us/library/hh477150%28v=sql.10%29.aspx

Tested with MS SQL Server Native Client 11 for Linux