This release manifest applies to the Internet release of
Microsoft SQL Server Native Client (SQL Native Client).
For more information about the SQL Native Client release, visit the following Microsoft Developer Network (MSDN) Web site:
To obtain the SQL Native Client, visit the following Microsoft Web site:
Release version number
SQL Native Client (9.00.1399.06), November 2005
This release provides the same version of SQL Native Client
that was released with Microsoft SQL Server 2005.
SQL Native Client (9.00.1399.06) will be available in the
- U.S. English
- Chinese (Traditional and Simplified)
- Brazilian Portuguese
Minimum supported configuration
- Microsoft Windows 2000 Service Pack 4 or later
- Microsoft Windows 2003 or later
- Microsoft Windows XP Service Pack 1 or later
Frequently asked questions about SQL Native Client
Q1: What is SQL Native Client?A1:
Microsoft SQL Server Native Client (SQL Native Client) contains the SQL OLE DB provider and SQL ODBC driver in one native dynamic link library (DLL) supporting applications using native-code APIs (ODBC, OLE DB and ADO) to Microsoft SQL Server. SQL Native Client should be used rather than Microsoft Data Access Components (MDAC) to create new applications or enhance existing applications that need to take advantage of new SQL Server 2005 features such as Multiple Active Result Sets (MARS), Query Notifications, User-Defined Types (UDT), and XML data type support.
Q2: What versions of SQL Server does SQL Native Client support?A2:
SQL Native Client supports Microsoft SQL Server 7.0,
2000 and SQL Server 2005.
Q3: Why would I move from MDAC (either the SQL ODBC driver or the SQL OLEDB provider)?A3:
SQL Native Client can be used to create new
applications or enhance existing applications that need to take advantage of
new SQL Server 2005 features such as Multiple Active Result Sets (MARS),
user-defined data types (UDT), query notifications, snapshot isolation, and XML
data type support.
Q4: Where can I find documentation for SQL Native Client?A4:
SQL Native Client documentation is available in the
“SQL Server Programming Reference” section of the SQL Server 2005 Books Online.
SQL Server 2005 Books Online can be viewed in the MSDN Library, available for
optionally installed with Microsoft SQL Server 2005.
Q5: Does SQL Native Client require MDAC and if so what version?A5:
The SQL Native Client ODBC driver is always used in
conjunction with the ODBC Driver Manager supplied with MDAC. The SQL Native
Client OLE DB provider may be used in conjunction with OLE DB Core Services
supplied with MDAC, but this is not a requirement – the choice to use Core
Services or not depends on the requirements of the individual application (for
example, if connection pooling is required). SQL Native Client uses the version of MDAC supplied
by the operating system.
File list for SQL Native Client (9.00.1399.06)
Collapse this tableExpand this table
|File Name||Version (x86)||Description|
library (DLL) file that contains all of the SQL Native Client functionality.
This includes the SQL Native Client OLE DB provider and the SQL Native Client
|Sqlnclir.rll||2005.90.1399.0||SQL Native Client
|Sqlncli.chm||The Data Source Wizard help file
that documents how to create a SQL Server data source using the SQL Native
Client ODBC driver or the SQL Native Client OLE DB provider.|
|Sqlncli.h||SQL Native Client header
|Sqlncli.lib||SQL Native Client ODBC driver
library file needed to directly call the bcp utility functions.|
The SQL Native Client files (sqlncli.dll, sqlnclir.rll, and
sqlncli.chm) are installed in the following location:
The SQL Native Client header and library files
(sqlncli.h and sqlncli.lib) are installed in the following location:
FILES%\Microsoft SQL Server\90\SDK