Oracle Express Download For Mac



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).

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.

GyazMail v.1.5.8 GyazMail 1.5.8 is an advanced e-mail client software specifically designed for Mac OS X. GyazMail is developed from scratch to be simple, easy-to-use e-mail client with many features, based on Cocoa framework. Currently it is still in development. The OpenLink ODBC Driver for Oracle (Express Edition) supports connections to Oracle 8i (8.1.7.4+) through 12c, and has been specifically designed for Apple's Mac Universal platform. This Release implements try-and-buy functionality, greatly simplifying evaluation and enabling a smooth upgrade to a full license, at a low entry-level price.

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

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.

For

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.

Install Oracle Application Express by downloading a ZIP file from the Oracle Application Express download page.

  1. For installations where the development will be in English only, download the file apex_5.1_en.zip from the Oracle Application Express download page. If the development will include languages other than English, download apex_5.1.zip from the Oracle Application Express download page. See:

    Note that the actual file name may differ if a more recent release has shipped since this document was published.

  2. Unzip downloaded zip file:
    • If English only, unzip apex_5.1_en.zip as follows, preserving directory names:

      • UNIX and Linux: $ unzip apex_5.1_en.zip

      • Windows: Double click the file apex_5.1_en.zip in Windows Explorer

    • If multiple languages, unzip apex_5.1.zip as follows, preserving directory names:

      • UNIX and Linux: $ unzipapex_5.1.zip

      • Windows: Double click the file apex_5.1.zip in Windows Explorer

    Note:

    You should keep the directory tree where you unzip the files short and not under directories that contain spaces. For example, within Windows unzip to C:TEMP.

  3. Change your working directory to apex.
  4. Start SQL*Plus and connect to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role. For example:
  5. Disable any existing password complexity rules for the default profile. See “Configuring Password Protection” in Oracle Database Security Guide.
  6. Select the appropriate installation option.

    Full development environment provides complete access to the App Builder environment to develop applications. A Runtime environment enables users to run applications that cannot be modified.

    Available installation options include:

    • Full development environment. Run apexins.sql passing the following four arguments in the order shown:

      Where:

      • tablespace_apex is the name of the tablespace for the Oracle Application Express application user.

      • tablespace_files is the name of the tablespace for the Oracle Application Express files user.

      • tablespace_temp is the name of the temporary tablespace or tablespace group.

      • images is the virtual directory for Oracle Application Express images. For installations using EPG, /i/ is the required value for the images argument. To support future Oracle Application Express upgrades, define the virtual image directory as /i/.

      Example:

      Note:

      If you receive the following error, exit SQL*Plus and change your working directory to where you unzipped the installation file, for example C:TEMP in Windows, before starting SQL*Plus:

      SP2-0310: unable to open file 'apexins.sql'

    • Runtime environment. Run apxrtins.sql passing the following arguments in the order shown:

      Where:

      • tablespace_apex is the name of the tablespace for the Oracle Application Express application user.

      • tablespace_files is the name of the tablespace for the Oracle Application Express files user.

      • tablespace_temp is the name of the temporary tablespace or tablespace group.

      • images is the virtual directory for Oracle Application Express images. To support future Oracle Application Express upgrades, define the virtual image directory as /i/.

      Example:

When Oracle Application Express installs, it creates three new database accounts:

  • APEX_050100 - The account that owns the Oracle Application Express schema and metadata.

  • FLOWS_FILES - The account that owns the Oracle Application Express uploaded files.

  • APEX_PUBLIC_USER - The minimally privileged account is used for Oracle Application Express configuration with Oracle REST Data Services or Oracle HTTP Server and mod_plsql.

Note:

In an environment where EPG is used to access Oracle Application Express, the existing minimally privileged account ANONYMOUS is used.

Oracle Mac Os

If you are upgrading from a previous release, then FLOWS_FILES already exists and APEX_PUBLIC_USER is created if it does not already exist.

Tip:

Oracle Express

Oracle Application Express must be installed from a writable directory on the file system. See 'Reviewing a Log of an Installation Session.'

Oracle Database 19c Download For Mac

See Also:

Oracle Database 12c Download For Mac

  • 'Configuring Password Protection' in Oracle Database Security Guide

  • 'About the Oracle Application Express Runtime Environment'

  • 'SQL*Plus User's Guide and Reference for more information about SQL*Plus'

  • 'Reviewing a Log of an Installation Session'