You are currently offline, waiting for your internet to reconnect

Release manifest for Microsoft SQL Server Native Client (9.00.1399.06)

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

INTRODUCTION
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:
MORE INFORMATION

Release version number

SQL Native Client (9.00.1399.06), November 2005

Release function

This release provides the same version of SQL Native Client that was released with Microsoft SQL Server 2005.

Localization information

SQL Native Client (9.00.1399.06) will be available in the following languages:
  • U.S. English
  • Chinese (Traditional and Simplified)
  • German
  • Japanese
  • Korean
  • Brazilian Portuguese
  • Spanish
  • French
  • Italian
  • Dutch
  • Russian
  • Swedish

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 download on http://www.microsoft.com/downloads and is 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 suppliedby the operating system.

File list for SQL Native Client (9.00.1399.06)

File NameVersion (x86)Description
Sqlncli.dll2005.90.1399.0The dynamic-link 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 ODBC driver.
Sqlnclir.rll2005.90.1399.0SQL Native Client resource file.
Sqlncli.chmThe 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.hSQL Native Client header file.
Sqlncli.libSQL Native Client ODBC driver library file needed to directly call the bcp utility functions.

Installation locations

The SQL Native Client files (sqlncli.dll, sqlnclir.rll, and sqlncli.chm) are installed in the following location:
%WINDOWS%\system32
The SQL Native Client header and library files (sqlncli.h and sqlncli.lib) are installed in the following location:
%PROGRAM FILES%\Microsoft SQL Server\90\SDK
Properties

Article ID: 910016 - Last Review: 11/04/2005 21:23:25 - Revision: 1.1

Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Standard Edition, Microsoft SQL Server 2005 Express Edition, Microsoft SQL Server 2005 Workgroup Edition

  • kbinfo KB910016
Feedback
mp;t=">