Download Microsoft Sql Server Client For Mac

Active10 months ago

How can I connect to a remote SQL server using Mac OS X? I don't really need a GUI, but it would be nice to have for the color coding and resultset grid. I'd rather not have to use a VM.

SQLPro for MSSQL (was SQL Client) is a lightweight TDS client, allowing quick and simple access to Microsoft SQL servers (sqlserver), including those hosted in Azure. This client does not work with MySQL.

Is there a SQL client for Mac OS X that works with MS SQL Server?

closed as not constructive by casperOneJul 3 '12 at 13:47

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.

25 Answers

Let's work together on a canonical answer.

Native Apps


  • Oracle SQL Developer (free)
  • SQuirrel SQL (free, open source)
  • DBeaver (free, open source)
  • SQL Workbench/J (free, open source)
  • Metabase (free, open source)
  • Netbeans (free, open source, full development environment)


(TODO: Add others mentioned below)

The Java-based Oracle SQL Developer has a plugin module that supports SQL Server. I use it regularly on my Mac. It's free, too.

Here's how to install the SQL Server plugin:

  • Run SQL Developer
  • go to this menu item: Oracle SQL Developer/Preferences/Database/Third-party JDBC Drivers
  • Click help.
  • It will have pointers to the JAR files for MySQL, SQL Server, etc.
  • The SQL Server JAR file is available at

This will be the second question in a row I've answered with this, so I think it's worth pointing out that I have no affiliation with this product, but I use it and love it and think it's the right answer to this question too: DbVisualizer.

I thought Sequel Pro for MySQL looked pretty interesting. It's hard to find one tool that works with all those databases (especially SQL Server 2005 . . . most people use SQL Server Management Studio and that's Windows only of course).

When this question was asked there were very few tools out there were worth much. I also ended up using Fusion and a Windows client. I have tried just about everything for MAC and Linux and never found anything worthwhile. That included dbvisualizer, squirrel (particularly bad, even though the windows haters in my office swear by it), the oracle SQL developer and a bunch of others. Nothing compared to DBArtizan on Windows as far as I was concerned and I was prepared to use it with Fusion or VirtualBox. I don't use the MS product because it is only limited to MS SQL.

Bottom line is nothing free is worthwhile, nor were most commercial non windows products

However, now (March 2010) I believe there are two serious contenders and worthwhile versions for the MAC and Linux which have a low cost associated with them. The first one is Aqua Data Studio which costs about $450 per user, which is a barely acceptable, but cheap compared to DBArtizan and others with similar functionality (but MS only). The other is RazorSQL which only costs $69 per user.Aqua data studio is good, but a resource hog and basically pretty sluggish and has non essential features such as the ER diagram tool, which is pretty bad at that. The Razor is lightning fast and is only a 16meg download and has everything an SQL developer needs including a TSQL editor.

So the big winner is RazorSQL and for $69, well worth it and feature ridden. Believe me, after several years of waiting to find a cheap non windows substitute for DBartizan, I have finally found one and I have been very picky.

Download Microsoft Sql Server Management Studio

My employer produces a simple, proof-of-concept HTML5-based SQL client which can be used against any ODBC data source on the web-browser host machine, through the HTML5 WebDB-to-ODBC Bridge we also produce. These components are free, for Mac, Windows, and more.

Applicable to many of the other answers here -- the Type 1 JDBC-to-ODBC Bridge that most are referring to is the one Sun built in to and bundled with the JVM. JVM/JRE/JDK documentation has always advised against using this built-in except in experimental scenarios, or when no other option exists, because this component was built as a proof-of-concept, and was never intended for production use.

My employer makes an enterprise-grade JDBC-to-ODBC Bridge, available as either a Single-Tier (installs entirely on the client application host) or a Multi-Tier (splits components over the client application host and the ODBC data source host, enabling JDBC client applications in any JVM to use ODBC data sources on Mac, Windows, Linux, etc.). This solution isn't free.

All of the above can be used with the ODBC Drivers for Sybase & Microsoft SQL Server (or other databases) we also produce ...

Squirrel SQL is a Java based SQL client, that I've had good experience with on Windows and Linux. Since it's Java, it should do the trick.

It's open source. You can run multiple sessions with multiple databases concurrently.

I vote for RazorSQL also. It's very powerful in many respects and practically supports most databases out there. I mostly use it for SQL Server, MySQL and PostgreSQL.

DbVisualizer supports many different databases. There is a free edition that I have used previously. Download from here

I have had good success over the last two years or so using Navicat for MySQL.The UI could use a little updating, but all of the tools and options they provide make the cost justifiable for me.

I like SQLGrinder.

It's built using Cocoa, so it looks a lot better and feels more like an Mac OS X application than all the Java-based application mentioned here.

It uses JDBC drivers to connect to Microsoft SQL Server 2005, FrontBase, MySQL, OpenBase, Oracle, PostgreSQL, and Sybase.

Free trial or $59.

I use the Navicat clients for MySQL and PostgreSQL and am happy with them. 'good' is obviously subjective... how do you judge your DB clients?

I've been using Oracle SQL Developer since the Microsoft software for SQL Server is not currently available on Mac OS X. It works wonders. I would also recommend RazorSQL or SQLGrinder.

I use AquaFold at work on Windows, but it's based on Java and supports Mac OS X.

I've used (DB Solo) and I like it a lot. It's only $99 and comparable to many more expensive tools. It supports Oracle, SQL Server, Sybase, MySQL, PostgreSQL and others.

Not sure about open-source, but I've heard good things about (not tried it, I prefer to write Python scripts to try things out rather than use GUIs;-).

When this question was asked, Microsoft's Remote Desktop for OS X had been unsupported for years. It wasn't a Universal Binary, and I found it to be somewhat buggy (I recall that the application will just quit after a failed connection instead of allowing you to alter the connection info and try again).

At the time I recommended the Open Source CoRD, a good RDP client for Mac.

Since then Microsoft Remote Desktop Client for Mac 2 was released.

I use Eclipse's Database development plugins - like all Java based SQL editors, it works cross platform with any type 4 (ie pure Java) JDBC driver. It's ok for basic stuff (the main failing is it struggles to give transaction control -- auto-commit=true is always set it seems).

Microsoft have a decent JDBC type 4 driver: this can be used with all Java clients / programs on Win/Mac/Lin/etc.

Those people struggling with Java/JDBC on a Mac are presumably trying to use native drivers instead of JDBC ones -- I haven't used (or practically heard of) the ODBC driver bridge in almost 10 years.

It may not be the best solution if you don't already have it, but FileMaker 11 with the Actual SQL Server ODBC driver ( worked nicely for a client of mine today. The ODBC driver is only $29, but FileMaker is $299, which is why you might only consider it if you already have it.

This doesn't specifically answer your question, because I'm not sure in any clients exist in Mac OS X, but I generally just Remote Desktop into the server and work through that. Another option is VMware Fusion (which is much better than Parallels in my opinion) + Windows XP + SQL Server Management Studio.

I've used Eclipse with the Quantum-DB plugins for that purpose since I was already using Eclipse anyway.

Ed: phpMyAdmin is for MySQL, but the asker needs something for Microsoft SQL Server.

Most solutions that I found involve using an ODBC Driver and then whatever client application you use. For example, Gorilla SQL claims to be able to do that, even though the project seems abandoned.

Most good solutions are either using Remote Desktop or VMware/Parallels.

Try CoRD and modify what you want directly from the server.

It's open source.

For MySQL, there is Querious and Sequel Pro. The former costs US$25, and the latter is free. You can find a comparison of them here, and a list of some other Mac OS X MySQL clients here.


Download Microsoft Sql Server 2012 Free

Since there currently isn't a MS SQL client for Mac OS X, I would, as Modesty has suggested, use Remote Desktop for the Mac.

Not the answer you're looking for? Browse other questions tagged sql-servermacos or ask your own question.


APPLIES TO: SQL Server Azure SQL Database Azure SQL Data Warehouse Parallel Data Warehouse

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:



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:

Sql Server Client Mac Os

%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