Skip to content

Exasol Integration

Integration of Exasol with Entropy Data.

The Exasol integration is managed within Entropy Data. Configure the connection and sync schedule to start syncing with Exasol.

No additional deployments are needed. Entropy Data connects over Exasol's WebSocket API, so no proprietary JDBC driver is required.

Features

  • Asset Synchronization: Sync schemas, tables and views from Exasol to Entropy Data as Assets, including column types, comments and primary keys.
  • Data Products and Data Contracts: Create data products and data contracts from Exasol assets. Exasol is available as a server type for output ports and data contracts.
  • Query Execution: Execute read-only SQL queries on Exasol data products through the MCP interface and Entropy Intelligence.

Prerequisites

You need a database user that can see the schemas, tables and views you want to sync. The integration reads the SYS.EXA_ALL_* system views, so it only finds the objects the user has privileges on.

To start, navigate to Settings > Integrations > Add Integration. This opens a wizard that guides you through configuring the integration.

Configuration

Select the Integration Type

Select the Integration Type

Select Exasol from the list of available integrations.

Configure the Connection

Provide the following connection details:

ParameterDescription
HostThe hostname or IP address of the Exasol database
PortThe port of Exasol's WebSocket API (default: 8563)
UsernameA database user that can see the schemas and tables to import
PasswordThe password for the user
Certificate FingerprintOptional. The SHA-256 fingerprint of the server certificate, if the database uses a self-signed certificate. Leave blank when the certificate is signed by a trusted CA.

Note: Credentials are stored encrypted in the Entropy Data database. To enable encryption in your environment, set a 64 hex character APPLICATION_ENCRYPTION_KEYS in your environment (see Configuration).

Configure Filters

Configure filters to limit which assets are synchronized. Both include and exclude filters are supported. For Exasol, filters can be applied to Schemas and Tables. Table filters apply to views as well.

Filters support '*' as a wildcard character to match any number of characters. Exasol stores unquoted names in upper case, so write patterns in upper case, for example SALES* or DIM_*.

filters:
  schemaIncludePatterns:
    - "SALES"
    - "ANALYTICS_*"
  schemaExcludePatterns:
    - "STAGING"
  tableIncludePatterns:
    - "DIM_*"
    - "FACT_*"
  tableExcludePatterns:
    - "TEMP_*"

Configure Schedule

Set a schedule to automatically synchronize assets. You can choose from predefined schedules or define a custom schedule using the cron expression format.

Note: All schedules use the UTC timezone, so make sure to take this into account when configuring your schedule. Please do not synchronize the assets more than once or twice per day. We reserve the right to disable the integration if this happens. You will be able to trigger a synchronization manually if you need an immediate update.

Complete the Integration Configuration

Choose a unique name for the integration, review your configuration, and click Create Integration.

Synchronized Assets

Exasol objectAsset typeProperties
Schemaexasol_schemahost, port, schema
Tableexasol_tablehost, port, schema, table
Viewexasol_viewhost, port, schema, table

Tables and views are linked to their schema. Column comments become property descriptions, NOT NULL columns are marked as required, and primary key columns are marked as primary keys.

Data Products and Data Contracts

When you create a data product or a data contract from an Exasol asset, Entropy Data sets up an exasol server with the host, port and schema of the asset. An Exasol cluster runs a single database, so the schema is the namespace and there is no database field.

servers:
  - server: "production"
    type: "exasol"
    host: "exasol.example.com"
    port: 8563
    schema: "SALES"

Query Execution

Once an Exasol data product is available, users can execute read-only SQL queries against its output ports through:

  • MCP Interface: Use the execute_query tool to run SQL queries on Exasol output ports.
  • Entropy Intelligence: Chat-based query execution with automatic connection setup.

To execute queries, each user needs to configure a personal Exasol connection in their profile under Connections, with host, port, username, password and, for a self-signed certificate, its fingerprint. The connection is matched to the output port by host. This ensures queries run on behalf of the individual user with their own Exasol credentials and permissions.

Next Steps

The integration is now configured and will run according to the schedule. To check the integration status, navigate to Settings > Integrations. Here you'll find the current status and the last 10 integration runs.

You can adjust the integration configuration at any time. The configuration is saved in YAML format with syntax validation support in the editor.

You can also change and test credentials in the edit view.

Note: The previously stored credentials are not displayed in the edit view for security reasons. If you want to change them, add new credentials and save the integration.

Deselecting the Enabled checkbox disables the automatic schedule. Manual integration runs are still possible.