The Community Edition is the easiest way to get Exasol up and running in a short time. It is a free-to-use, one-node image of the Exasol database that can be installed on common virtualization software. The Community Edition supports all the features available in Exasol and lets you manage up to 200 GB of data. To download the Community Edition, sign up here.
This quick start guide provides you with information on how to get started with the Exasol Community edition.
Exasol Community Edition comes with community support. If you need additional assistance, you would need to purchase it. For more information, refer to our Customer Support page.
Quick Start Video
- A machine with a minimum of 4 GB RAM and any 64-bit Operating System
- A virtual machine player
Exasol is tested on Virtual Box and VMWare player.
- The virtual machine image
- ODBC or JDBC drivers for connecting your preferred SQL client
Step 1: Download and Install Virtualization Software
If you do not already use a virtual environment (such as a Virtual Box, VMWare player, KVM, etc.), you need to set one up. If you plan to load data from your local machine, you do not have to change the standard network settings. In other cases, you might want to set it to either NAT or Bridge. Refer to the documentation of your chosen virtualization software for information on how to do this.
Step 2: Import Virtual Machine Image
Import the Community Edition image using your virtualization software. Based on the Community Edition virtual image (.ova) or (.iso), the following options are available to import the virtual image.
If you download the virtual machine image (.ova), clicking this image file will open the Import Virtual Application screen. Click Import and then click Agree on the Software License Agreement screen. The virtual machine is preconfigured with default values and is ready to run.
Depending upon the browser you are using, you may have to check the security configurations on the browser or turn off the pop-up blocker to download the .OVA file.
Another way to install Exasol using the ova file is with command line.
This procedure uses ESXi Version 6.7 as an example.
- Start a terminal (bash or CMD).
- Go the directory where you want to install Exasol.
- Run the following command.
ovftool.exe --powerOn --acceptAllEulas --name=[VM Name] --memorySize:[VM Name]=8196 --numberOfCpus:[VM Name]=4 --network=[Network Name] [OVA location EXASOL-Single-Node-7.0.0.ova] "vi://[ESXi-USER]:[ESXi-PASSWORD]@[ESXi-IP]"
- Boot from exa1 in the VM.
- Wait for the database to be operational.
To install the Exasol Community Edition using the .iso, follow these steps:
- Launch the virtual box or the virtualization software you are using.
- Create a new virtual machine with the desired configuration.
- Change the boot sequence to point to the .iso file downloaded and save the changes.
- Start the virtual machine, at the command prompt enter Install to install Exasol through .iso file.
- Enter the hard drive to install to and select OK to confirm.
Encrypting a device is optional. However, we recommend you to encrypt the device. When the Encrypt device is checked, on rebooting the license server, you must provide a password for the disk.
- If there are multiple private networks, enter the number in Number of tagged private VLANs and select OK.
- Next, enter the password for the maintenance user and select OK.
- Setup the external network of the server. This is the network that will be used to connect from database clients.
- In the Advanced network configuration screen, as per the default setting, the first network interface of the box is used for the private network and the second interface for the public network. In case you want a different setup, select Configure to alter the configuration, else select OK to continue. .
- The installation process will now start. Once it has completed, the system will reboot automatically.
- Boot up the system from the local hard drive. At the command prompt, type Local and press enter.
Once you have completed these steps, you can log into the terminal using the login name maintenance and the maintenance password you set up in step 7 to obtain the IP address for the license node.
Initial System Configuration
Unlike with the .OVA installation, the virtual machine is not preconfigured with default values. You need to perform the initial system configuration.
- Launch EXAoperation by entering the IP address of the license node on your web browser. Log in as an admin user. The default values are username admin and password admin.
- Navigate to Service -> EXAStorage and start the storage service by clicking Startup Storage Service.
- Select the checkbox next to the configured node (n0010) and then select Add unused Disks option. You should now see the available storage capacity of the node.
Create the necessary data volume for the database. In the EXAStorage screen, click Add Volume and choose the appropriate volume values. For example, for single node (n0010), the volume configuration can be as shows below:
For additional information about storage management and volumes, refer to the Storage Management section.
Additionally, you can create an archive volume for backups. Archive volumes in Exasol can be of two types - Local Archive Volume and Remote Archive Volume. For more information on how to setup archive volumes, refer to the Create Local Archive Volume and Create Remote Archive Volume sections.
Once you have the initial system configuration in place, you need to configure the database.
- In EXAoperation, go to Services > EXASolution and click Add.
- Configure the database properties and click Add. The following screen shot shows a sample database configuration:
- Next, create the necessary database directories. Click the database instance you just added and in the following screen, select Create from the Actions drop-down list. Click Submit. The state of the node will be Selected or Reserved.
- Once the necessary directories are created, start the database by selecting Startup from the Actions drop-down list and click Submit. You can also start the database from the EXASolution main screen.
For additional information about database management, refer to the Database Management section.
To improve the performance of your Exasol installation you can consider changing the following default values in the virtual machine's properties:
- VM RAM: The default RAM for the Community Edition virtual machine is 4 GB. You can increase this to improve performance, but always ensure that there is enough RAM remaining for the host OS.
- Number of virtual cores: Depending on the capacity of your host system, you can increase the number of virtual cores for the virtual machine.
Do not change any other settings of the imported virtual machine.
Step 3: Start the Community Edition
Start the virtual machine to boot the Exasol Community Edition. If everything ran smoothly, the configuration screen is displayed as shown below:
The Configuration screen displays
- The DB Connection String and user details for connecting to the database instance.
- The EXAoperation URL and user details for connecting to EXAoperation.
Step 4: Connect to Exasol
You can connect to Exasol using SQL Clients, Drivers, Business Intelligence tools, and so on. For more information, refer to the Connect to Exasol section.
If you want to enable the Internet access for the database using NAT, see Enable internet access for Exasol Community Edition.
Step 5: Load Data
After you successfully connect to Exasol, you can load data into Exasol from file or from other databases. For more information, refer to the Loading Data section.
Step 6: Connect to EXAoperation
EXAoperation is Exasol's administration console that provides a complete interface for configuring, managing, and monitoring Exasol. Additionally, EXAoperation provides you with an overview of the system such as database instances, available space, and so on. You can also update Exasol license and drivers through EXAoperation.
To access EXAoperation, open a browser on your local machine and enter the EXAoperation URL from Step 4. A login page is displayed, and you can log in using the default user name / password (admin/admin).