-->APPLIES TO: SQL Server Azure SQL Database Azure Synapse Analytics (SQL DW) Parallel Data Warehouse ![Sql Server Client For Mac Office Sql Server Client For Mac Office](/uploads/1/2/5/7/125754572/141404626.jpeg)
![For For](/uploads/1/2/5/7/125754572/937692832.jpg)
Aug 19, 2018 According to my test, if I import data from a database in Excel for Mac following the steps in this article, when I click 'Data' tab New Database Query SQL Server ODBC, there will be a window called 'Connect to SQL Server ODBC Data Source' pops up and ask me to type in Server name, Database, Authentication, User Name and Password.
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 Client For Mac Office Sql Server Client For Mac Office](/uploads/1/2/5/7/125754572/141404626.jpeg)
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
Installation How-to Topics
This post was authored by Meet Bhagdev, Program Manager, Microsoft
Hi, all. We are delighted to share the production-ready release of the Microsoft ODBC Driver 13.1 for macOS El Capitan and Sierra. The new driver enables access to SQL Server, Azure SQL Database and Azure SQL DW from any C/C++ application on macOS.
Added
- Native install experience – The driver can now be installed with brew. Instructions on how to do this are below.
- Azure AD support – You can now use Azure AD authentication (username/password) to centrally manage identities of database users and as an alternative to SQL Server authentication.
- Always Encrypted support – You can now use Always Encrypted. Always Encrypted lets you transparently encrypt the data in the application, so that SQL Server will only handle the encrypted data and not plaintext values. Even if the SQL instance or the host machine is compromised, an attacker gets ciphertext of the sensitive data.
- Table Valued Parameters (TVP) support – TVP support allows a client application to send parameterized data to the server more efficiently by sending multiple rows to the server with a single call. You can use the ODBC Driver 13.1 to encapsulate rows of data in a client application and send the data to the server in a single parameterized command.
- AlwaysOn support – This release supports AlwaysOn high availability and disaster recovery. Customers have the option to use AlwaysOn by using features with capabilities like these:
- Ability to specify whether an application is connecting to an AlwaysOn Availability Group Cluster (multi subnet failover)
- Ability to specify application intent as read-only versus read/write
- Ability to make transparent connections to AlwaysOn Availability Groups. The driver quickly discovers the current AlwaysOn topology of your server infrastructure and connects to the current active server transparently.
- BCP API support – You can use functions through the ODBC driver as described here.
- SQL Server 2017 support – This release is tested and certified against the latest SQL Server release.
- TLS 1.2 support – This release supports TLS 1.2 connections to SQL Server.
Install the ODBC Driver on macOS
- /usr/bin/ruby -e “$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)“
- brew tap microsoft/msodbcsql https://github.com/Microsoft/homebrew-mssql-release
- brew update
- brew install msodbcsql
- #for silent install ACCEPT_EULA=y brew install msodbcsql
Try our sample
![For For](/uploads/1/2/5/7/125754572/937692832.jpg)
Once you install the driver that runs on a supported macOS distro, you can use this C sample to connect to SQL Server/Azure SQL DB/Azure SQL DW. To download the sample and get started, follow these steps:
- wget“https://raw.githubusercontent.com/Microsoft/sql-server-samples/master/samples/tutorials/c/linux/sample_c_linux.c“
- gcc sample_c_linux.c -o sample_c_linux -lodbc -w #make sure you change the servername, username and password in the connections string
- ./sample_c_linux
Please file bugs, questions and issues on our Issues page. We welcome contributions, questions and issues of any kind. Happy programming!
Meet Bhagdev ([email protected])