Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. For more information, click the following article number to view the article in the Microsoft Knowledge Base:ĩ56909 The SQL Server 2008 builds that were released after SQL Server 2008 was released Status We recommend that you consider applying the most recent fix release that contains this hotfix.
![thin sql client odbc thin sql client odbc](http://www.nesscomp.com/wp-content/uploads/2012/07/High-Level-Architecture.png)
![thin sql client odbc thin sql client odbc](https://www.thatjeffsmith.com/wp-content/uploads/2014/01/oci4.png)
The ODBC driver has Oracle's standard client-server version interoperability, see Support Doc ID 207303.1. Creating a SQL Server Native Client ODBC Driver Application. Data Source Names and 64-Bit Operating Systems. The driver supports applications written using earlier versions of ODBC in the manner defined in the ODBC 3.51 specification.
#THIN SQL CLIENT ODBC HOW TO#
For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:ĩ58186 Cumulative update package 2 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Oracle's Instant Client ODBC software is a standalone package that offers the full functionality of the Oracle ODBC driver (except the Oracle service for Microsoft Transaction Server) with a simple install. The SQL Server Native Client ODBC driver complies with the Microsoft Win32 ODBC 3.51 specification. The fix for this issue was first released in Cumulative Update 2. One of the TVP’s subtypes is also bound as DAE. The application uses the SQL Server 2008 ODBC driver to bind the TVP as data-at-execution (DAE).
![thin sql client odbc thin sql client odbc](https://media.springernature.com/original/springer-static/image/chp%3A10.1007%2F978-1-4842-4321-3_9/MediaObjects/467924_1_En_9_Fig3_HTML.png)
This problem occurs if the following conditions are true: