Sql Workbench For Mac

MySQL Workbench is not available for Mac but there are plenty of alternatives that runs on macOS with similar functionality. The most popular Mac alternative is DBeaver, which is both free and Open Source.If that doesn't suit you, our users have ranked more than 50 alternatives to MySQL Workbench and many of them are available for Mac so hopefully you can find a suitable replacement. To install SQL Workbench/J. Review the SQL Workbench/J software license. Go to the SQL Workbench/J website and download the appropriate package for your operating system on your client computer or Amazon EC2 instance. Go to the Installing and starting SQL Workbench/J page.

RazorSQL - Query, Edit, Browse, and Manage Databases. RazorSQL is an SQL query tool, database browser, SQL editor, and database administration tool for Windows, macOS, Mac OS X, Linux, and Solaris. RazorSQL has been tested on over 40 databases, can connect to databases via either JDBC or ODBC, and includes support for the following databases. MySQL Workbench for Mac is a unified visual tool for database architects, developers, and DBAs.MySQL Workbench provides data modeling, SQL development, and comprehensive administration tools for server configuration, user administration, backup, and much more. The tool is available on Windows, Linux and macOS. Features and Highlights Design MySQL Workbench for macOS enables a DBA. Mac Package; Source Code; Build 118 (works with Java 7) All Platforms; Mac Package for Java7; Source Code; Build 117. All Platforms; Mac Package; Mac Package for Java7; Source Code; Build 116. All Platforms; Mac Package; Mac Package for Java7; Source Code; Build 115. All Platforms; Mac Package; Mac Package for Java7; Source Code; Build 114.

Chapter 3. Installing and Launching MySQL Workbench

Table of Contents

3.1. Hardware Requirements
3.2. Software Requirements
3.3. Starting MySQL Workbench
3.3.1. Installing MySQL Workbench on Windows
3.3.2. Launching MySQL Workbench on Windows
3.3.3. Uninstalling MySQL Workbench on Windows
3.3.4. Installing MySQL Workbench on Linux
3.3.5. Launching MySQL Workbench on Linux
3.3.6. Uninstalling MySQL Workbench on Linux
3.3.7. Installing MySQL Workbench on Mac OS X
3.3.8. Launching MySQL Workbench on Mac OS X
3.3.9. Uninstalling MySQL Workbench on Mac OS X
3.4. Activation Procedure (Commercial Version)

MySQL Workbench is available for the following platforms:

Binary distributions of MySQL Workbench are avaliable for the above platforms. Source code distributions are also available as a tar.gz package, or an RPM package.

The following sections explain the installation process for each of these platforms.

MySQL Workbench requires a current system to run smoothly. The minimum hardware requirements are:

  • CPU: Intel Core or Xeon 3GHz (or Dual Core 2GHz) or equal AMD CPU

  • Cores: Single (Dual/Quad Core is recommended)

  • RAM: 4 GB (6 GB recommended)

  • Graphic Accelerators: nVidia or ATI with support of OpenGL 1.5 or higher

  • Display Resolution: 1280×1024 is recommended, 1024×768 is minimum.

The following operating systems are officially supported:

  • Windows 7 (64-bit, Professional level or higher)

  • Mac OS X 10.6.1+

  • Ubuntu 9.10 (64bit)

  • Ubuntu 8.04 (32bit/64bit)

For convenience the following builds are also available:

  • Windows XP SP3, Vista

  • Mac OSX (10.5 and 10.6) Intel

  • Ubuntu 8.04 (i386/x64)

  • Ubuntu 9.04 (i386/x64)

  • Fedora 11 (i386/x64)

MySQL Workbench also has the following general requirements:

  1. The Microsoft .NET 3.5 Framework.

  2. Cairo 1.6.0 or later

  3. glib-2.10

  4. libxml-2.6

  5. libsigc++ 2.0

  6. pcre

  7. libzip

For convenience the Windows libraries are available as the download “Dependencies for Compiling in Windows”.

On start up, the application checks the OpenGL version and selects between software and hardware rendering. To determine the rendering method that is being used, open the Help menu and choose the System Info submenu.

3.3.1. Installing MySQL Workbench on Windows
3.3.2. Launching MySQL Workbench on Windows
3.3.3. Uninstalling MySQL Workbench on Windows
3.3.4. Installing MySQL Workbench on Linux
3.3.5. Launching MySQL Workbench on Linux
3.3.6. Uninstalling MySQL Workbench on Linux
3.3.7. Installing MySQL Workbench on Mac OS X
3.3.8. Launching MySQL Workbench on Mac OS X
3.3.9. Uninstalling MySQL Workbench on Mac OS X

The procedure for launching MySQL Workbench depends on the platform. Generally, there are two ways to launch MySQL Workbench from the command line and from the graphical user interface of the host operating system. Using the command-line launching facility is useful when you want to customize some aspects of the way MySQL Workbench operates. Launching MySQL Workbench for each of the supported platforms is described in the following sections.

In addition to platform-specific command line options, MySQL Workbench has the following command line options:

  • --admin instance - Launch MySQL Workbench and load the server instance specified.

  • --query connection - Launch MySQL Workbench and load the connection specified.

  • --model modelfile - Launch MySQL Workbench and load the model specified.

  • --script script - Launch MySQL Workbench and run the script specified.

  • --run code - Launch MySQL Workbench and run the code snippet specified.

  • --quit-when-done - quits MySQL Workbench after --script or --run finishes.

MySQL Workbench may be installed using the Windows installer file or it may be installed manually from a ZIP file.

Installing MySQL Workbench Using the Installer

MySQL Workbench can be installed using the Windows Installer (.msi) installation package. The MSI package bears the name mysql-workbench-version-win32.msi, where version indicates the MySQL Workbench version number.

Installing MySQL Workbench using the installer requires either Administrator or Power User privileges. If you are using the ZIP file without an installer, you do not need Administrator or Power User privileges.

Improving the MySQL Installation Wizard depends on the support and feedback of users. If you find that the MySQL Installation Wizard is lacking some feature important to you, or if you discover a bug, please report it in our bugs database. To do this use the Report a Bug option under the Help menu.

  1. To install MySQL Workbench, right-click the MSI file and select the Install option from the pop-up menu, or simply double-click the file.

  2. In the Setup Type window you may choose a Complete or Custom installation. To use all features of MySQL Workbench choose the Complete option.

  3. Unless you choose otherwise, MySQL Workbench is installed in C:%PROGRAMFILES%MySQLMySQL Workbench 5.1 edition_type, where %PROGRAMFILES% is the default directory for programs for your locale. The %PROGRAMFILES% directory may be C:Program Files or C:programme.

Installing from the ZIP File

If you are having problems running the installer, as an alternative, you can download a ZIP file without an installer. That file is called mysql-workbench-version-win32.zip. Using a ZIP utility, unpack it to the directory of your choice. You may also want to create a shortcut on your desktop or the quick launch bar.

To install using the ZIP file, download the ZIP file to a convenient location and decompress the file. You can place the resulting directory anywhere on you system. You do not need to install or configure the application before using it.

To start MySQL Workbench on Windows select Start, Programs, MySQL and then select MySQL Workbench.

You may also start MySQL Workbench from the command line. To view the available command-line options, issue the command MySQLWorkbench -help more from the MySQL Workbench installation directory. You will see the following output:

The MySQL Workbench version number is displayed followed by a usage message and then the options. Use the -swrendering option if your video card does not support OpenGL 1.5. The -version option can be used to display the MySQL Workbench version number. The -grtversion can be used to display the GRT shell version number. The other options are self-explanatory.

When using command-line options that display output to a console window, namely -help and -version, be sure that you pipe the output through the more command otherwise nothing will be displayed.

The method for uninstalling MySQL Workbench will depend on how you install MySQL Workbench in the first place.

Rmoving MySQL Workbench when installed Using the Installer

  1. To uninstall MySQL Workbench, open the Control Panel and Choose Add or Remove Programs. Find the MySQL Workbench entry and choose the button. Doing this will remove MySQL Workbench.

  2. Any modules added to the C:Program FilesMySQLMySQL Workbench versionmodules directory will not be deleted.

It is not possible to remove MySQL Workbench from the command line if you have installed MySQL Workbench using the installer. Although you can manually remove some of the compoentns There is no command-line option for removing MySQL Workbench.

Removing the MySQL Workbench directory manually will not remove all the files belonging to MySQL Workbench.

When installed from a ZIP file

If you installed MySQL Workbench using a ZIP file, to remove MySQL Workbench you can just delete the MySQL Workbench directory.

Sql Workbench For Mac Install

If you installed any additional modules within the modules directory and you want to keep them, make sure you copy those modules to a different directory before deleting the MySQL Workbench directory.

There are several binary distributions of MySQL Workbench available for Linux. These include:

  • Fedora 10 amd64 (RPM)

  • Ubuntu 8.04 i386 (DEB)

  • Ubuntu 8.10 amd64 (DEB)

In addition to the binary distributions, it is also possible to download the MySQL Workbench source code as a tar.gz or RPM package.

Check the MySQL Workbench download page for the latest packages.

The procedure for installing on Linux depends on which Linux distribution you are using.

Installing DEB packages

On Ubuntu, and other systems that use the Debian package scheme, you can install MySQL Workbench using a command such as:

Note that package.deb will be the MySQL Workbench package, for example, mysql-workbench-oss-version_i386.deb, where version is the MySQL Workbench version number.

You may be warned that certain libraries are not available, depending on what you already have installed. Install the required libraries and then install the MySQL Workbench package again.

Installing RPM packages

On RedHat-based systems, and other systems using the RPM package format, MySQL Workbench can be installed by a command such as:

Again, note that package.rpm will be the MySQL Workbench package, for example, mysql-workbench-oss-version-1fc10.x86_64.rpm, and version is the MySQL Workbench version number.

Once MySQL Workbench has been installed it can be launched by selecting Applications, Programming, MySQL Workbench from the main menu.

MySQL Workbench can also be launched from the command line on Linux. Type the command:

This will display the available command-line options:

The procedure for uninstalling MySQL Workbench on Linux depends on the packe you are using.

Uninstalling DEB packages

For Debian packages the command is:

For

This does not remove the configuration files. If you wish to also remove the configuration files use:

Mysql Workbench Download For Mac

Uninstalling RPM packages

To uninstall RPM packages use:

This does not remove the configuration files.

MySQL Workbench is available for Mac OS X and is distributed as a DMG file. The file is named mysql-workbench-oss-version-osx10.5-i686.dmg, where version is the MySQL Workbench version.

To install MySQL Workbench on Mac OS X, simply download the file. Double-click the downloaded file. You will be presented with the installation screen:

Figure 3.1. MySQL Workbench Mac OS X Installation Screen

Drag the MySQL Workbench icon onto the Application icon as instructed. MySQL Workbench is now installed.

You can now launch MySQL Workbench from the Applications folder.

To launch MySQL Workbench on Mac OS X, simply open the Applications folder in the Finder, then double-click MySQL Workbench.

It is also possible to start MySQL Workbench from the command line:

A model file must be specified.

To uninstall MySQL Workbench for Mac OS X, simply locate MySQL Workbench in the Applications folder, right-click, and select Move to Trash. The application is uninstalled.

Here I’ll show you how to get SQL Server up and running on your Mac in less than half an hour. And the best part is, you’ll have SQL Server running locally without needing any virtualization software.

Prior to SQL Server 2017, if you wanted to run SQL Server on your Mac, you first had to create a virtual machine (using VirtualBox, Parallels Desktop, VMware Fusion, or Bootcamp), then install Windows onto that VM, then finally SQL Server. This is still a valid option depending on your requirements (here’s how to install SQL Server on a Mac with VirtualBox if you’d like to try that method).

Download Sql Workbench

Starting with SQL Server 2017, you can now install SQL Server directly on to a Linux machine. And because macOS is Unix based (and Linux is Unix based), you can run SQL Server for Linux on your Mac. The way to do this is to run SQL Server on Docker.

So let’s go ahead and install Docker. Then we’ll download and install SQL Server.

  1. Install Docker

    Download the (free) Docker Community Edition for Mac (unless you’ve already got it installed on your system). This will enable you to run SQL Server from within a Docker container.

    To download, visit the Docker CE for Mac download page and click Get Docker.

    To install, double-click on the .dmg file and then drag the Docker.app icon to your Application folder.

    What is Docker?

    Docker is a platform that enables software to run in its own isolated environment. SQL Server (from 2017) can be run on Docker in its own isolated container. Once Docker is installed, you simply download — or “pull” — the SQL Server on Linux Docker Image to your Mac, then run it as a Docker container. This container is an isolated environment that contains everything SQL Server needs to run.

  2. Launch Docker

    Launch Docker the same way you’d launch any other application (eg, via the Applications folder, the Launchpad, etc).

    When you open Docker, you might be prompted for your password so that Docker can install its networking components and links to the Docker apps. Go ahead and provide your password, as Docker needs this to run.

  3. Increase the Memory

    By default, Docker will have 2GB of memory allocated to it. SQL Server needs at least 3.25GB. To be safe, increase it to 4GB if you can.

    To do this:

    1. Select Preferences from the little Docker icon in the top menu
    2. Slide the memory slider up to at least 4GB
    3. Click Apply & Restart
  4. Download SQL Server

    Now that Docker is installed and its memory has been increased, we can download and install SQL Server for Linux.

    Open a Terminal window and run the following command.

    This downloads the latest SQL Server 2019 for Linux Docker image to your computer.

    You can also check for the latest container version on the Docker website if you wish.

    Update: When I first wrote this article, I used the following image:

    Which downloaded SQL Server 2017. Therefore, the examples below reflect that version.

  5. Launch the Docker Image

    Run the following command to launch an instance of the Docker image you just downloaded:

    But of course, use your own name and password. Also, if you downloaded a different Docker image, replace microsoft/mssql-server-linux with the one you downloaded.

    Here’s an explanation of the parameters:

    -dThis optional parameter launches the Docker container in daemon mode. This means that it runs in the background and doesn’t need its own Terminal window open. You can omit this parameter to have the container run in its own Terminal window.
    --name sql_server_demoAnother optional parameter. This parameter allows you to name the container. This can be handy when stopping and starting your container from the Terminal.
    -e 'ACCEPT_EULA=Y'The Y shows that you agree with the EULA (End User Licence Agreement). This is required in order to have SQL Server for Linux run on your Mac.
    -e 'SA_PASSWORD=reallyStrongPwd123'Required parameter that sets the sa database password.
    -p 1433:1433This maps the local port 1433 to port 1433 on the container. This is the default TCP port that SQL Server uses to listen for connections.
    microsoft/mssql-server-linuxThis tells Docker which image to use. If you downloaded a different one, use it instead.

    Password Strength

    If you get the following error at this step, try again, but with a stronger password.

    I received this error when using reallyStrongPwd as the password (but of course, it’s not a really strong password!). I was able to overcome this by adding some numbers to the end. However, if it wasn’t just a demo I’d definitely make it stronger than a few dictionary words and numbers.

  6. Check the Docker container (optional)

    You can type the following command to check that the Docker container is running.

    If it’s up and running, it should return something like this:

  7. Install sql-cli (unless already installed)

    Run the following command to install the sql-cli command line tool. This tool allows you to run queries and other commands against your SQL Server instance.

    This assumes you have NodeJs installed. If you don’t, download it from Nodejs.org first. Installing NodeJs will automatically install npm which is what we use in this command to install sql-cli.

    Permissions Error?

    If you get an error, and part of it reads something like Please try running this command again as root/Administrator, try again, but this time prepend sudo to your command:

  8. Connect to SQL Server

    Now that sql-cli is installed, we can start working with SQL Server via the Terminal window on our Mac.

    Connect to SQL Server using the mssql command, followed by the username and password parameters.

    You should see something like this:

    This means you’ve successfully connected to your instance of SQL Server.

  9. Run a Quick Test

    Run a quick test to check that SQL Server is up and running and you can query it.

    For example, you can run the following command to see which version of SQL Server your running:

    If it’s running, you should see something like this (but of course, this will depend on which version you’re running):

    If you see a message like this, congratulations — SQL Server is now up and running on your Mac!

A SQL Server GUI for your Mac – Azure Data Studio

Sql workbench free download

Azure Data Studio (formerly SQL Operations Studio) is a free GUI management tool that you can use to manage SQL Server on your Mac. You can use it to create and manage databases, write queries, backup and restore databases, and more.

Azure Data Studio is available on Windows, Mac and Linux.

Here are some articles/tutorials I’ve written for Azure Data Studio:

Another Free SQL Server GUI – DBeaver

Another SQL Server GUI tool that you can use on your Mac (and Windows/Linux/Solaris) is DBeaver.

DBeaver is a free, open source database management tool that can be used on most database management systems (such as MySQL, PostgreSQL, MariaDB, SQLite, Oracle, DB2, SQL Server, Sybase, Microsoft Access, Teradata, Firebird, Derby, and more).

I wrote a little introduction to DBeaver, or you can go straight to the DBeaver download page and try it out with your new SQL Server installation.

Limitations of SQL Server for Linux/Mac

SQL Server for Linux does have some limitations when compared to the Windows editions (although this could change over time). The Linux release doesn’t include many of the extra services that are available in the Windows release, such as Analysis Services, Reporting Services, etc. Here’s a list of what’s available and what’s not on SQL Server 2017 for Linux and here’s Microsoft’s list of Editions and supported features of SQL Server 2019 on Linux.

Another limitation is that SQL Server Management Studio is not available on Mac or Linux. SSMS a full-blown GUI management for SQL Server, and it provides many more features than Azure Data Studio and DBeaver (at least at the time of writing). You can still use SSMS on a Windows machine to connect to SQL Server on a Linux or Mac machine, but you just can’t install it locally on the Linux or Mac machine.

If you need any of the features not supported in SQL Server for Linux, you’ll need SQL Server for Windows. However, you can still run SQL Server for Windows on your Mac by using virtualization software. Here’s how to install SQL Server for Windows on a Mac using VirtualBox.