May 08, 2017 The Microsoft SQL Server 2016 SP1 Feature Pack is a collection of stand-alone packages which provide additional value for Microsoft SQL Server. Installing SQL Server Native Client.; 2 minutes to read Contributors. All; In this article APPLIES TO: SQL Server Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse For content related to previous versions of SQL Server, see Installing SQL Server Native Client. Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x). SNAC, or SQL Server Native Client, is a term that has been used interchangeably to refer to ODBC and OLE DB drivers for SQL Server. NOTE: It is not recommended to use this driver for new development. The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) which will be updated with the most recent server.
- Sql Server 2016 Data Quality Client Download
- Microsoft Sql Server 2016 Download
- Download Sql Client Tools
- Sql Server 2012 Client Tools
- Sql Server 2016 Native Client Download
Microsoft SQL Server Native Client 11.0 is installed when you install SQL Server 2016 (13.x).
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
Sql Server 2016 Data Quality Client Download
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.
Microsoft Sql Server 2016 Download
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
SQL Server Management Studio (SSMS) is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. SSMS provides tools to configure, monitor, and administer instances of SQL Server and databases. Use SSMS to deploy, monitor, and upgrade the in the messages to track when a given query completed its execution.Query Execution or ResultsAllow more data to be displayed (Result to Text) and stored in cells (Result to Grid). SSMS now allows up to 2M characters for both (up from 256 and 64 K, respectively). This also addressed the issue of users not able to grab more than 43680 chars from the cells of the grid.ShowPlanAdded a new attribute in QueryPlan when inline scalar UDF feature is enabled (ContainsInlineScalarTsqlUdfs).Integration Services (SSIS)Perf optimization for SSIS package scheduler in Azure
For details about what's new in this release, see the SSMS release notes.
Supported SQL offerings (SSMS 18.2)
- This version of SSMS works with all supported versions of SQL Server 2008 - SQL Server 2019 and provides the greatest level of support for working with the latest cloud features in Azure SQL Database and Azure SQL Data Warehouse.
- Additionally, SSMS 18.x can be installed side by side with SSMS 17.x, SSMS 16.x, or SQL Server 2014 SSMS and earlier.
- SQL Server Integration Services (SSIS) - SSMS version 17.x or later doesn't support connecting to the legacy SQL Server Integration Services service. To connect to an earlier version of the legacy Integration Services, use the version of SSMS aligned with the version of SQL Server. For example, use SSMS 16.x to connect to the legacy SQL Server 2016 Integration Services service. SSMS 17.x and SSMS 16.x can be installed side by side on the same computer. Since the release of SQL Server 2012, the SSIS Catalog database, SSISDB, is the recommended way to store, manage, run, and monitor Integration Services packages. For details, see SSIS Catalog.
Supported operating systems (SSMS 18.2)
Download Sql Client Tools
This release of SSMS supports the following 64-bit platforms when used with the latest available service pack:
- Windows 10 (64-bit) *
- Windows 8.1 (64-bit)
- Windows Server 2019 (64-bit)
- Windows Server 2016 (64-bit) *
- Windows Server 2012 R2 (64-bit)
- Windows Server 2012 (64-bit)
- Windows Server 2008 R2 (64-bit)
* Requires version 1607 (10.0.14393) or later
Note
SSMS runs on Windows only. If you need a tool that runs on platforms other than Windows, take a look at Azure Data Studio. Azure Data Studio is a new cross-platform tool that runs on macOS, Linux, as well as Windows. For details, see Azure Data Studio.
Release notes (SSMS 18.2)
There are a few known issues with this release.
For details about this release, see the SSMS release notes.
Previous SSMS releases
Sql Server 2012 Client Tools
Get help for SQL tools
Sql Server 2016 Native Client Download
See also
Contribute SQL documentation
Did you know that you could edit the content yourself? If you do so, not only will our documentation improve, but you'll also be credited as a contributor to the page.