Skip to content

Latest commit

 

History

History
81 lines (57 loc) · 7.08 KB

system-requirements-for-sql-server-native-client.md

File metadata and controls

81 lines (57 loc) · 7.08 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords
System Requirements
System Requirements for SQL Server Native Client
markingmyname
maghan
03/14/2017
sql
native-client
reference
system requirements [SQL Server Native Client]
data access [SQL Server Native Client], system requirements
SQL Server Native Client, system requirements
SQLNCLI, system requirements

System Requirements for SQL Server Native Client

[!INCLUDESQL Server Azure SQL Database Synapse Analytics PDW]

Important

[!INCLUDEsnac-removed-oledb-and-odbc]

To use data access features of [!INCLUDEssNoVersion] such as MARS, you must have the following software installed:

[!INCLUDEssNoVersion] Native Client requires Windows Installer 3.1. Windows Installer 3.1 is already installed on [!INCLUDEmsCoName] Windows operating systems. For all other platforms you need to explicitly install it. For more information, see Windows Installer 3.1 Redistributable (v2).

Note

Make sure you log on with administrator privileges before installing this software.

Operating System Requirements

For a list of operating systems that support [!INCLUDEssNoVersion] Native Client, see Support Policies for SQL Server Native Client.

SQL Server Requirements

To use [!INCLUDEssNoVersion] Native Client to access data in [!INCLUDEssNoVersion] databases, you must have an instance of [!INCLUDEssNoVersion] installed.

[!INCLUDEssSQL14] supports connections from all versions of MDAC, Windows Data Access Components, and all versions of [!INCLUDEssNoVersion] Native Client. When an older client version connects to [!INCLUDEssNoVersion], server data types not known to the client are mapped to types that are compatible with the client version. For more information, see Data Type Compatibility for Client Versions, later in this topic.

Cross-Language Requirements

The English-language version of [!INCLUDEssNoVersion] Native Client is supported on all localized versions of supported operating systems. Localized versions of [!INCLUDEssNoVersion] Native Client are supported on localized operating systems that are the same language as the localized [!INCLUDEssNoVersion] Native Client version. Localized versions of [!INCLUDEssNoVersion] Native Client are also supported on English-language versions of supported operating systems as long as the matching language settings are installed.

For upgrades:

  • English-language versions of [!INCLUDEssNoVersion] Native Client can be upgraded to any localized version of [!INCLUDEssNoVersion] Native Client.

  • Localized versions of [!INCLUDEssNoVersion] Native Client can be upgraded to localized versions of [!INCLUDEssNoVersion] Native Client of the same language.

  • Localized version of [!INCLUDEssNoVersion] Native Client can be upgraded to the English-language version of [!INCLUDEssNoVersion] Native Client.

  • Localized versions of [!INCLUDEssNoVersion] Native Client cannot be upgraded to localized [!INCLUDEssNoVersion] Native Client versions of a different localized language.

Data Type Compatibility for Client Versions

[!INCLUDEssNoVersion] and [!INCLUDEssNoVersion] Native Client map new data types to older datatypes that are compatible with down-level clients, as shown in the table below.

OLE DB and ADO applications can use the DataTypeCompatibility connection string keyword with [!INCLUDEssNoVersion] Native Client to operate with older data types. When DataTypeCompatibility=80, OLE DB clients will connect using the [!INCLUDEssVersion2005] tabular data stream (TDS) version, rather than the TDS version. This means that for [!INCLUDEsql2008-md] and later data types, down-level conversion will be performed by the server, rather than by [!INCLUDEssNoVersion] Native Client. It also means that the features available on the connection will be limited to the [!INCLUDEssVersion2005] feature set. Attempts to use new datatypes or features are detected as early as possible on API calls and errors are returned to the calling application, rather than attempting to pass invalid requests to the server.

There is no DataTypeCompatibility control for ODBC.

IDBInfo::GetKeywords will always return a keyword list that corresponds to the server version on the connection and is not affected by DataTypeCompatibility.

Data type SQL Server Native Client

SQL Server 2005		 SQL Server Native Client 11.0

[!INCLUDEssSQL14]		 Windows Data Access Components, MDAC, and

SQL Server Native Client OLE DB applications with DataTypeCompatibility=80
CLR UDT (<= 8Kb) udt Udt Varbinary
varbinary(max) varbinary varbinary Image
varchar(max) varchar varchar Text
nvarchar(max) nvarchar nvarchar Ntext
xml xml xml Ntext
CLR UDT (> 8Kb) udt varbinary Image
date date varchar Varchar
datetime2 datetime2 varchar Varchar
datetimeoffset datetimeoffset varchar Varchar
time time varchar Varchar

See Also

SQL Server Native Client Programming
Installing SQL Server Native Client