Exasol

Author: M | 2025-04-24

Exasol Essentials is a comprehensive introduction to the Exasol database. Take this course first to start your Exasol education.

GitHub - exasol/pyexasol: Exasol Python driver with low

ODBC Drivers for Linux/FreeBSD This article describes the ODBC drivers provided by Exasol to connect applications running on Linux or FreeBSD with an Exasol system. The Exasol ODBC drivers for Linux and FreeBSD are tested on the following systems: Linux CentOS 7 CentOS 8 Stream OpenSUSE 15 Debian 10 Ubuntu 20.04 LTS Ubuntu 22.04 LTS FreeBSD FreeBSD 13.2 FreeBSD 14.0 The Exasol ODBC driver needs at least OpenSSL 1.1 to run. On some operating systems, OpenSSL must be installed separately. Download and install the ODBC driver Download the latest driver for your operating system from the Exasol Download Portal. Run the following commands to extract the package in a directory:For Linux/FreeBSD: tar -xzf Exasol_ODBC-.tar.gzFor Solaris: gtar -xzf Exasol_ODBC-.tar.gz For configuration information, see the readme.txt file included in the driver package. License Each driver package includes the latest version of the license for the driver. The license allows you to bundle the driver with third-party software, for example when creating plugins for a BI tool. For more details, refer to the license file which is located in the folder where the driver was installed. Configure ODBC driver and data sources To configure the driver, run the config_odbc program to generate the odbc.ini file. Change into the install directory and then run config_odbc as shown below: cd Exasol_ODBC-* ./config_odbc Running the config_odbc performs the following operations: Scan the system for available ODBC driver manager Check for missing (3rd party) packages Create an odbc.ini config file Create a wrapper script to start applications Test the database connectivity Suggest the correct DSN an application needs based on the driver manager it uses The generated odbc.ini file contains DSN entries for all supported ODBC driver managers. To further configure the options in the odbc.ini file, see Connection strings. The config_odbc program also allows non-interactive use. For details, run the following command: Known Issues Issue Reason Solution config_odbc does not start The operating system may not have the full Perl installation. Install a full Perl system and try again. Fix: minimal Debian apt-get install perl Fix: minimal CentOS 7 yum install perl-Digest-MD5 Error "Data source name not found, and no default driver specified" Wrong version of the unixODBC is used because of multiple installation instances. Specify the correct version of the unixODBC through isql -version. The unixODBC driver manager is using the wrong odbc.ini file. Specify the correct odbc.ini file through the environment variable ODBCINI. Error "Invalid UTF-8 character in input" Wrong locale defined in the LC_ALL variable. Define a locale in the LC_ALL variable that can display the characters properly. Missing or wrong characters in output of console or your ODBC application Incompatible locale defined in the odbc.ini file. Set the environment variables LC_CTYPE and LC_NUMERIC or the parameters CONNECTIONLCCTYPE and CONNECTIONLCNUMERIC in the odbc.ini file to a locale that can display the characters. Applications using the DataDirect driver manager need UTF-8 locales. Database type Dynamic Query versions Compatible Query versions Google BigQuery JDBC driver 1.2.14.1017 JDBC driver 1.2.16.1020 JDBC driver 1.2.18.1022 JDBC driver 1.2.19.1023 Not applicable Amazon Athena JDBC driver 2.0.23 Not applicable Snowflake JDBC driver 3.13.0 JDBC driver 3.13.1 JDBC driver 3.13.2 JDBC driver 3.13.3 JDBC driver 3.13.4 JDBC driver 3.13.5 JDBC driver 3.13.6 Not applicable Amazon Redshift JDBC Driver 1.2.54.1082 JDBC Driver 1.2.55.1083 JDBC Driver 2.0.0.5 Not applicable Denodo 8 server JDBC driver version 8.0 20210209 Not applicable Exasol 7.0.10 server Exasol JDBC driver version 7.0.7 Exasol JDBC driver version 7.0.11 Not applicable Trino Server 353 Trino JDBC Driver 351 Trino JDBC Driver 352 Trino JDBC Driver 353 Not applicable Trino Server 354 Trino JDBC Driver 354 Not applicable Trino Server 355 Trino JDBC Driver 355 Not applicable Trino Server 356 Trino JDBC Driver 356 Not applicable Trino Server 357 Trino JDBC Driver 357 Not applicable Trino Server 358 Trino JDBC Driver 358 Not applicable Trino Server 359 Trino JDBC Driver 359 Not applicable Trino Server 360 Trino JDBC Driver 360 Not applicable VMware Tanzu Greenplum 6.16.0 server VMware Tanzu Greenplum JDBC Driver 5.1.4.000275 Not applicable Apache Hive Server 3.1.3000.7.1.6.0-297 Hive JDBC Driver 3.1.3000.7.1.6.0-297 Not applicable Cloudera Impala 3.4 server Cloudera JDBC driver version 2.6.18.1021 Cloudera JDBC driver version 2.6.20.1024 Cloudera JDBC driver version 2.6.23.1028 Not applicable BigSQL 7.1 server IBM JCC JDBC driver version 4.29.24 Not applicable Azure Synapse Analytics 12.00.2531 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Not applicable Azure SQL 12.00.2255 Microsoft SQL Server JDBC driver version 9.2.0 Microsoft SQL Server JDBC driver version 9.4.0 Not applicable MariaDB 10.4.17 server MariaDB JDBC driver version 2.7.2 MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.4.18 server MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.5.8 server MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.5.9 server MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.5.10 server MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.6.0 server MariaDB JDBC driver version 2.7.3 Not applicable MariaDB 10.6.3 server MariaDB JDBC driver version 2.7.3 Not applicable SingleStore 7.3.6 server MariaDB JDBC driver version 2.7.3

exasol/metabase-driver: Exasol driver for Metabase - GitHub

Are used in the SELECT clause- Auto-completing a column in a sub-select may insert an alias from the outer query- Auto-completion doesn't work after INSERT INTO- Auto-completion doesn't work with the USING join syntax- The auto-completion popup may behave strangely if a database error occurs when loading table metadata- Create/Alter Table- DB Support: PostgreSQL NOT NULL can be omitted in the DDL for auto-generated columns in PostgreSQL- DB Support: ClickHouse Can't list databases in older versions of ClickHouse- DB Support: Exasol Incorrect SQL generated by the "Create User LDAP" action in Exasol- Export/Import User Settings Passwords are not included when exporting/importing SSH configurations- Key Bindings Some of the assigned key combinations may stop working until the application is restarted- OS Support: macOS Expanding database nodes using the keyboard may result in the spinning beachball on macOS Sonoma- Query Builder When loading a query containing an unsupported operator into the query builder, it is replaced with "="- SQL Commander "Enter Data for Variables" dialog does not reflect the initial state of boolean variables- SQL Editor Multi-caret select may exclude the first line when clicking outside of the editor- The delete key doesn't work in multi-caret mode- Tool Properties "Show Password" doesn't work for authentication type Public Key in Tool Properties->SSH Configurations. Exasol Essentials is a comprehensive introduction to the Exasol database. Take this course first to start your Exasol education.

Exasol for Healthcare and Pharma

On-Premises, Hybrid, or Cloud Exasol offers flexible and scalable deployment options to fit the unique needs of your business. Choose the deployment method that works best for your infrastructure and performance requirements, ensuring seamless integration and optimal performance. On-Prem On-Premises Deployment On-Premises deployment provides you with the ultimate control over your data, allowing you to leverage your existing physical or virtualized environments. With this deployment method, you can ensure maximum data security, compliance with internal policies, and the ability to tailor your environment according to your specific performance needs. Hybrid Hybrid Deployment Hybrid deployment offers a mix of on-premises and cloud-based resources, delivering the benefits of both environments. Sensitive data can remain on-premises for enhanced security and compliance, while the cloud’s scalability can be utilized to handle additional workload demands and burst capacity. SaaS Software as a Service (SaaS) SaaS deployment allows you to access Exasol’s powerful analytics capabilities as a fully-managed service. This option eliminates the need for internal infrastructure, software maintenance, and system administration, enabling your team to focus on leveraging data insights for strategic decision-making. With SaaS, you benefit from quick deployment, automatic updates, and scalable resources without the typical IT overhead. Public Cloud Cloud Deployment Leverage the power of the cloud by deploying Exasol on your preferred public cloud provider. This option provides flexibility, scalability, and reduces the need for physical infrastructure investments. Table types in Snowflake (dynamic, event, hybrid and iceberg tables)- Database Objects Tree In the database objects tree, add an indicator to nodes where all sub-nodes were hidden by an active filter- Export Use SQL syntax highlighting in the preview section in Export Grid- Automatically suggest file extensions when exporting data- General Improved support for arrays- Grid Component Display newlines and tabs as symbols rather than whitespace in text values in the data grid- Multi-thread image preview generation- SQL Commander With auto-commit off, show the actual statements when warning the user about uncommitted updates- Add support for a list of choices in custom variables- SQL Editor Add a button for newline in Find and Replace- Support newline, tab and uppercase/lowercase manipulation in Find and Replace- Handle identifier delimiters based on database type instead of user configuration- Security Add the option to reset master password also when a master password is requiredFixed:- Area Details- Auto-Completion Auto-Completion may fail when operators are used in the SELECT clause- Auto-completing a column in a sub-select may insert an alias from the outer query- Auto-completion doesn't work after INSERT INTO- Auto-completion doesn't work with the USING join syntax- The auto-completion popup may behave strangely if a database error occurs when loading table metadata- Create/Alter Table- DB Support: PostgreSQL NOT NULL can be omitted in the DDL for auto-generated columns in PostgreSQL- DB Support: ClickHouse Can't list databases in older versions of ClickHouse- DB Support: Exasol Incorrect SQL generated by the "Create User LDAP" action in Exasol- Export/Import User Settings Passwords are not included when exporting/importing SSH configurations- Key Bindings Some of the assigned key combinations may stop working until the application is restarted- OS Support: macOS Expanding database nodes using the keyboard may result in the spinning beachball on macOS Sonoma- Query Builder When loading

Exasol for Banking and Insurance

Iceberg tables)- Database Objects Tree In the database objects tree, add an indicator to nodes where all sub-nodes were hidden by an active filter- Export Use SQL syntax highlighting in the preview section in Export Grid- Automatically suggest file extensions when exporting data- General Improved support for arrays- Grid Component Display newlines and tabs as symbols rather than whitespace in text values in the data grid- Multi-thread image preview generation- SQL Commander With auto-commit off, show the actual statements when warning the user about uncommitted updates- Add support for a list of choices in custom variables- SQL Editor Add a button for newline in Find and Replace- Support newline, tab and uppercase/lowercase manipulation in Find and Replace- Handle identifier delimiters based on database type instead of user configuration- Security Add the option to reset master password also when a master password is requiredFixed:- Area Details- Auto-Completion Auto-Completion may fail when operators are used in the SELECT clause- Auto-completing a column in a sub-select may insert an alias from the outer query- Auto-completion doesn't work after INSERT INTO- Auto-completion doesn't work with the USING join syntax- The auto-completion popup may behave strangely if a database error occurs when loading table metadata- Create/Alter Table- DB Support: PostgreSQL NOT NULL can be omitted in the DDL for auto-generated columns in PostgreSQL- DB Support: ClickHouse Can't list databases in older versions of ClickHouse- DB Support: Exasol Incorrect SQL generated by the "Create User LDAP" action in Exasol- Export/Import User Settings Passwords are not included when exporting/importing SSH configurations- Key Bindings Some of the assigned key combinations may stop working until the application is restarted- OS Support: macOS Expanding database nodes using the keyboard may result in the spinning beachball on macOS Sonoma- Query Builder When loading a query containing an unsupported operator into the

Exasol for eCommerce and Retail

Released: Aug 16, 2019Updates in 2019.2.2Features Added JOIN completion based on column names. Markdown data extractor is now bundled with DataGrip. Drag-and-drop of columns now adds commas. Breadcrumbs are now also shown for SQL. Improved support for partition tables in PostgreSQL . The key enhancement: partition tables are now displayed under the main one.FixesIDE general Performance improvements. The folder path became editable in SQL Dialects settings section.Code generation Schema comparison: the same objects are not marked as different anymore. [Oracle] No more disappearing semicolon in the package code. [Oracle] Column names are not missed from view’s code anymore. [DB2] Editing procedures is available on DB2 for i (AS/400). [Sqlite] Check constraints do not disappear after the update.Data editor Fixed bugs in file import. Fixed problem with the column width when using the Material Theme plugin. BLOB fields are displayed correctly. The Forward and Back buttons don’t run queries anymore. The Ctrl/Cmd+F12 shortcut in the filter field of the data editor opens the columns list. The Go To Related Data action enabled showing only required rows.Database explorer Adding a new schema doesn’t remove items from the database explorer. [Redshift] External tables are back.Coding assistance Fixed bugs in the SQL formatter. [Exasol] DROP INDEX support.Navigation Results in Find Usages are sorted by the line number.. Exasol Essentials is a comprehensive introduction to the Exasol database. Take this course first to start your Exasol education.

Analytics Database and Warehouse - Exasol

This article describes the Skyline SQL extension. Skyline is an SQL extension for data analysis developed by Exasol. It solves the following problems with large data volumes with multi-criteria optimization: Data flooding Very large data volumes can be almost impossible to analyze. When navigating through millions of data rows, you typically sort by one dimension and regard the top n results. Because of that, you will almost never find the optimum result. Empty result You often use filters to simplify the problem of large data volumes. Most of the time they are too restrictive and lead to empty result sets. By iteratively adjusting the filters, people try to extract a controllable data set. This procedure prevents finding the optimum result. The difficulty of correlating many dimensions When many dimensions are relevant it can be impossible to find an optimum result using plain SQL. By the use of metrics, analysts try to find an adequate heuristic to weight the different attributes. By simplifying the problem to only a single number, a lot of information and correlation within the data is then lost. This strategy will seldom produce the optimum result. How Skyline works Instead of using hard filters through the WHERE clause and metrics between columns, the relevant dimensions are specified in the PREFERRING clause. Skyline uses this to provide the optimal set. The optimal set, also known as the Pareto set, which is the number of non-dominated points in the search space. By definition, a point is dominated by another