Install Microsoft Sql Server Native Client Windows
The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows to Microsoft SQL Server and Windows Azure SQL.
-->This article is an index of content that provides guidance for installing SQL Server on Windows.
For other deployment scenarios, see:
Beginning with SQL Server 2016 (13.x), SQL Server is only available as a 64-bit application. Here are important details about how to get SQL Server and how to install it. Phantom vs blademaster.
Getting started
Editions and features: Review the supported features for the different editions and versions of SQL Server to determine which best suits your business needs.
- SQL Server 2019 (15.x).
- SQL Server 2017 (14.x).
- SQL Server 2016 (13.x).
Requirements: Review hardware and software installation requirements for SQL Server 2016 & 2017, SQL Server 2019 or SQL Server on Linux, as well as system configuration checks, and security considerations in Planning a SQL Server Installation
Sample databases and sample code:
- They are not installed as part of SQL Server setup by default but can be found
- To install them for non-Express editions of SQL Server, see the Where are samples
Installation media
The download location for SQL Server depends on the edition:
- SQL Server Enterprise, Standard, and Express Editions are licensed for production use. For the Enterprise and Standard Editions, contact your software vendor for the installation media. You can find purchasing information and a directory of Microsoft partners on the Microsoft licensing page.
Other SQL Server components can be found here:
- SQL Server Reporting Services.
Considerations
Installation fails if you launch setup through Remote Desktop Connection with the media on a local resource in the RDC client. To install remotely the media must be on a network share or local to the physical or virtual machine. SQL Server installation media may be either on a network share, a mapped drive, a local drive, or presented as an ISO to a virtual machine.
SQL Server Setup installs the following software components required by the product:
- SQL Server Native Client
- SQL Server Setup support files
SQL Server installation
| Article | Description |
|---|---|
| Installation Wizard | Install SQL Server using the Installation Wizard GUI launched from the setup.exe setup media. |
| Command Prompt | Sample syntax and installation parameters for running a SQL Server installation from the command prompt. |
| Server Core | Install SQL Server on Windows Server Core. |
| Check Parameters for the System Configuration Checker | Discusses the function of the System Configuration Checker (SCC). |
| Configuration File | Sample syntax and installation parameters for running Setup through a configuration file. |
| SysPrep | Sample syntax and installation parameters for running Setup through SysPrep. |
| Add Features to an Instance | Update components of an existing instance of SQL Server. |
| SQL Server Failover Cluster Installation | Install a SQL Server failover cluster instance. |
| Repair a Failed SQL Server Installation | Repair a corrupt SQL Server installation. |
| Rename a computer with SQL Server | Update system metadata that is stored in sys.servers after the hostname of a computer hosting a stand-alone instance of SQL Server has been renamed. |
| Install SQL Server Servicing Updates | Install updates for SQL Server. |
| Setup Log Files | View and read the errors in the SQL Server setup log files. |
| Validate an Installation | Review the use of the SQL Discovery report to verify the version of SQL Server and the SQL Server features installed on the computer. |
Individual component installation
| Article | Description |
|---|---|
| SQL Server Database Engine | Install and configure the SQL Server Database Engine. |
| SQL Server Replication | Install and configure SQL Server Replication. |
| Distributed Replay | Lists articles to install the Distributed Replay feature. |
| SQL Server Management Tools with SSMS | Install and configure SQL Server management tools. |
| SQL Server PowerShell | Considerations for installing SQL Server PowerShell components. |
SQL Server configuration
| Article | Description |
|---|---|
| Configure Windows Firewall (SQL Server) | Overview of firewall configuration and how to configure the Windows firewall to allow access to SQL Server. |
| Configure the Windows Firewall (SSAS) | Configure both port and firewall settings to allow access to Analysis Services or Power Pivot for SharePoint. |
| Configure a Multi-Homed Computer | Configure SQL Server and Windows Firewall with Advanced Security to provide for network connections to an instance of SQL Server in a multi-homed environment. |
See also
Upgrade SQL Server
Uninstall SQL Server
Install SQL Server Reporting Services (SSRS)
Install SQL Server Analysis Services (SSAS)
Install SQL Server Business Intelligence Features
High Availability Solutions (SQL Server)
Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x).
Lma manager 2007 pc full version. There is no SQL Server 2016 Native Client. For more information, see SQL Server Native Client.
You can also get sqlncli.msi from the SQL Server 2012 Feature Pack web page. To download the most recent version of the SQL Server Native Client, go to Microsoft速 SQL Server速 2012 Feature Pack. If a previous version of SQL Server Native Client earlier than SQL Server 2012 is also installed on the computer, SQL Server Native Client 11.0 will be installed side-by-side with the earlier version.
The SQL Server Native Client files (sqlncli11.dll, sqlnclir11.rll, and s11ch_sqlncli.chm) are installed to the following location:
%SYSTEMROOT%system32
Note
All appropriate registry settings for the SQL Server Native Client OLE DB provider and the SQL Server Native Client ODBC driver are made as part of the installation process.
The SQL Server Native Client header and library files (sqlncli.h and sqlncli11.lib) are installed in the following location:
%PROGRAMFILES%Microsoft SQL Server110SDK
In addition to installing SQL Server Native Client as part of the SQL Server installation, there is also a redistributable installation program named sqlncli.msi, which can be found on the SQL Server installation disk in the following location: %CD%Setup.
You can distribute SQL Server Native Client through sqlncli.msi. You might have to install SQL Server Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of SQL Server Native Client. If your application targets a platform other than the one it was developed on, you can download versions of sqlncli.msi for x64, Itanium, and x86 from the Microsoft Download Center.
When you invoke sqlncli.msi, only the client components are installed by default. The client components are files that support running an application that was developed using SQL Server Native Client. To also install the SDK components, specify ADDLOCAL=All on the command line. For example:
msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
Silent Install
If you use the /passive, /qn, /qb, or /qr option with msiexec, you must also specify IACCEPTSQLNCLILICENSETERMS=YES, to explicitly indicate that you accept the terms of the end user license. This option must be specified in all capital letters.
Uninstalling SQL Server Native Client
Because applications such as SQL Server server and the SQL Server tools depend on SQL Server Native Client, it is important not to uninstall SQL Server Native Client until all dependent applications are uninstalled. To provider users with a warning that your application depends on SQL Server Native Client, use the APPGUID install option in your MSI, as follows:
msiexec /i sqlncli.msi APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
The value passed to APPGUID is your specific product code. A product code must be created when using Microsoft Installer to bundle your application setup program.
See Also
Building Applications with SQL Server Native Client
Installation How-to Topics