SQL Server Native Client
Updated: August 8, 2016
SQL Server Native Client (SNAC) is not supported beyond SQL Server 2012. Avoid using SNAC in new development work, and plan to modify applications that currently use it. The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows to Microsoft SQL Server and Microsoft Azure SQL Database.
The last SQL Server Native Client can be downloaded from Microsoft® SQL Server® 2012 Feature Pack. Developers who wish to use an OLE DB provider to connect to the latest version of SQL Server must use the OLE DB provider that shipped in SQL Server 2012 Native Client.
For more information on ODBC Driver for SQL Server, see Microsoft ODBC Driver for SQL Server on Windows. See also, Introducing the new Microsoft ODBC Drivers for SQL Server, and ODBC Driver 13.1 for SQL Server released.
The following topics describe significant new SQL Server Native Client features in SQL Server 2012.
In addition, ODBC in SQL Server Native Client now supports three features that were added to standard ODBC in the Windows 7 SDK:
Asynchronous execution on connection-related operations. For more information, see Asynchronous Execution.
C Data Type Extensibility. For more information, see C Data Types in ODBC.
To support this feature in SQL Server Native Client, SQLGetDescField can return SQL_C_SS_TIME2 (for time types) or SQL_C_SS_TIMESTAMPOFFSET (for datetimeoffset) instead of SQL_C_BINARY, if your application uses ODBC 3.8. For more information, see Data Type Support for ODBC Date and Time Improvements.
Calling SQLGetData with a small buffer multiple times to retrieve a large parameter value. For more information, see Retrieving Output Parameters Using SQLGetData.
The following topics describe SQL Server Native Client behavior changes in SQL Server 2012.
When calling ICommandWithParameters::SetParameterInfo, the value passed to the pwszName parameter must be a valid identifier. For more information, see ICommandWithParameters.
SQLDescribeParam will now consistently return a value that conforms to the ODBC specification. For more information, see SQLDescribeParam.