To configure a proxy for a Talend Data Catalog server on Linux:

1. Stop the Talend Data Catalog application server
2. Locate the Talend Data Catalog Tomcat configuration:
   
   On Linux, the Talend Data Catalog server typically runs in a Tomcat‑style container under the installation directory (for example, /opt/talend/talend-data-catalog).
   
   The key paths are $TDC_HOME/bin/setenv.sh or equivalent startup script, often in /bin/ or /bin/linux_x86_64.
   
   
3. Configure the JVM proxy properties:
   
   
   1. Edit the $TDC_HOME/bin/setenv.sh of the Talend Data Catalog server on Linux.
   2. Add the JVM arguments for the proxy: -Dhttps.proxyHost= <IP or HostName> -Dhttps.proxyPort=3128
      
      Example:
      
      

      JAVA_OPTS="-D\"catalina.data=${CATALINA_DATA}\" -D\"connector.port=${M_CONNECTOR_PORT}\" -D\"shutdown.port=${M_SHUTDOWN_PORT}\" -D\"server.fqdn=${M_SERVER_FQDN}\" -Dlog4j2.disableJmx=true -Djava.awt.headless=true -Dhttp.proxyHost=<IP or HostName> -Dhttp.proxyPort=3128 -Dhttps.proxyHost= <IP or HostName> -Dhttps.proxyPort=3128"

4. Restart
5. To verify if the Talend Data Catalog application server uses the proxy, run the following command:
   
   

   $ps -ef | grep java

   
   This will output the following:
   
   [root@RHEL8-QCDI01 ~]# ps -ef | grep java
   root       23155       1  6 May11 ?        12:28:04 /home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../jre/bin/java -Dnop -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms256M -Xmx4096M -Dcatalina.data=/home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../data -Dconnector.port=11480 -Dshutdown.port=11481 -Dserver.fqdn=localhost -Dlog4j.configurationFile=/home/TDC-8-20250107/TalendDataCatalog/tomcat/bin/../../tomcat/conf/log4j2.xml -Dlog4j2.disableJmx=true -Djava.awt.headless=true -Dhttp.proxyHost=10.76.203.106 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=10.76.203.106 -Dhttps.proxyPort=3128 -Djdk.tls.ephemeralDHKeySize=2048 - [...]
   
   

Note the effect using a proxy will have if you have SAML/SSO enabled. See Configuring the SAML server for details. 

Environment

• Talend Data Catalog Server
• Squid Proxy Server

This article describes how to connect Talend Studio to Starburst (Galaxy or Enterprise) using the Trino JDBC driver. It covers driver download, JDBC connection configuration inside Talend Studio, and load script patterns for querying Starburst catalogs. It is intended for use alongside Qlik Sense Enterprise on Windows (client-managed) environments where Talend Studio is used as the ETL layer to stage or transform data before it is consumed by Qlik.

Content

• Prerequisites
• Download the Trino JDBC Driver
• Configure the JDBC Connection in Talend Studio
• Connection Settings: Galaxy vs. Enterprise
• Schema and Catalog Usage
• Trino SQL Compatibility Notes
• Talend Component Patterns
• Troubleshooting
• References

Prerequisites

Before configuring the connection, ensure the following requirements are met:

• Talend Studio (Data Integration or Big Data edition), version 7.x or later.
• Java Runtime Environment (JRE) 11 or later, as required by the Trino JDBC driver.
• Network connectivity from the Talend Studio workstation or server to the Starburst cluster endpoint.
• A Starburst user account (Galaxy service account or Enterprise user) with SELECT privileges on the target catalog and schema.
• Internet access to download the Trino JDBC driver from Maven Central, or an internal Maven proxy that mirrors it.

Download the Trino JDBC Driver

Talend Studio connects to Starburst using the Trino JDBC driver. Unlike the ODBC driver used for Qlik Sense direct connections, no platform installer is required. The driver is a single JAR file.

1. Download the Trino JDBC driver JAR from Maven Central:

   https://repo1.maven.org/maven2/io/trino/trino-jdbc/479/trino-jdbc-479.jar

2. Save the JAR to a stable local path, for example:

   C:\Drivers\Starburst\trino-jdbc-479.jar  

3. Do not rename the JAR file. Talend Studio uses the filename to identify the driver.

Check the Starburst documentation for the recommended JDBC driver version that matches your Starburst Galaxy or Enterprise deployment. The version referenced above (479) is the version used in the Data Nova Conference demo environment.

Configure the JDBC Connection in Talend Studio

Talend Studio uses a generic JDBC database connection type to connect to Starburst. The steps below apply to both Starburst Galaxy and Starburst Enterprise. The only difference is the JDBC URL and credentials.

Add a New Database Connection

• Open your Talend Studio project.
• In the Repository panel, expand Metadata and right-click Db Connections.
• Select Create connection.
• Enter a connection name (for example: Starburst Galaxy or Starburst Enterprise) and click Next.

Select the JDBC Connection Type

• In the DB Type dropdown, search for and select JDBC.
• Click Next to proceed to the driver and URL configuration.

Configure Driver and Connection Parameters

Complete the connection form with the following parameters:

Example JDBC URL for the Data Nova Conference demo environment (Starburst Galaxy):

jdbc:trino://stardock-qlik.starport.starburst.io:443/transactional_data

1. Click the [...] button next to the Driver JAR field and browse to the trino-jdbc-479.jar file saved in Download the Trino JDBC Driver.
2. In the Driver Class field, enter or select: io.trino.jdbc.TrinoDriver
3. Enter the User ID and Password for the Starburst service account.
4. Click Check to test the connection. A successful test displays the Starburst version.
5. Click Finish to save the connection.

If the connection test fails with an SSL error when connecting to Starburst Galaxy, ensure that Java's certificate store trusts the public CA that signed the Galaxy endpoint certificate. For Starburst Enterprise with a self-signed certificate, import the certificate into the JRE keystore using keytool.

Connection Settings: Galaxy vs. Enterprise

The table below summarises the JDBC parameters that differ between Starburst Galaxy and Starburst Enterprise: 

The Trino JDBC driver is the same JAR for both Galaxy and Enterprise. Only the JDBC URL, port, and authentication settings differ.

Schema and Catalog Usage

Starburst organises data in a three-level hierarchy: catalog > schema > table. The JDBC URL specifies the default catalog. The schema is set in the Talend connection configuration and can be overridden at the component level.

Specifying the Default Catalog in the JDBC URL

Include the catalog name as the path component of the JDBC URL:

jdbc:trino://stardock-qlik.starport.starburst.io:443/transactional_data

In this example, transactional_data is the catalog. All queries run through this connection will default to that catalog unless a three-part table name is used.

Using Three-Part Table Names in Talend Components

When querying tables across multiple catalogs within the same Talend job, use three-part table names in tDBInput or tDBRow SQL queries:

SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM transactional_data.retail.customers
WHERE created_date >= DATE '2024-01-01'

Always use three-part table names (catalog.schema.table) in SQL queries inside Talend components to avoid ambiguity, even when a default catalog is set in the JDBC URL.

Trino SQL Compatibility Notes

Starburst uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed when writing SQL inside Talend components (tDBInput, tDBRow, tDBOutput):

Talend Component Patterns

The following patterns cover common scenarios for reading from and writing to Starburst within a Talend Studio job.

Reading Data with tDBInput

• Use the Starburst JDBC connection configured in Configure the JDBC Connection in Talend Studio.
• In the tDBInput component, set the Query field to a valid Trino SQL SELECT statement using three-part table names.
• Map the output schema columns to match the SELECT column list.

Writing Data with tDBOutput

• Starburst supports INSERT INTO for Iceberg and Delta Lake tables. Hive connector tables may be read-only depending on the catalog configuration.
• Set the Action on the table to Insert and ensure the target table exists in Starburst before running the job.
• Use three-part table names in the Table field: catalog.schema.table.

Incremental Loads with Context Variables

Use Talend context variables to pass date parameters into SQL predicates for incremental data loads:

Define a context variable:

context.lastLoadDate = 2024-01-01

Reference it in the tDBInput query:

SELECT *
FROM transactional_data.retail.transactions
WHERE transaction_date >= DATE '" + context.lastLoadDate + "'

For production incremental loads, persist the last successful load date to a Talend context file or a control table in Starburst so that the value survives job restarts.

Troubleshooting

Connection test fails: ClassNotFoundException

• Verify the full path to the trino-jdbc-479.jar is correct in the Driver JAR field.
• Confirm the Driver Class is exactly io.trino.jdbc.TrinoDriver (case-sensitive).
• Ensure the JAR has not been renamed or moved since the connection was saved.

Connection test fails: SSL handshake error

• For Starburst Galaxy, confirm that the Talend Studio JRE trusts the public CA certificate chain for *.galaxy.starburst.io.
• For Starburst Enterprise with a self-signed certificate, import the certificate into the JRE keystore: keytool -import -alias starburst -keystore $JAVA_HOME/lib/security/cacerts -file starburst.crt
• Verify that the JDBC URL uses the correct port (443 for Galaxy, 8443 for Enterprise HTTPS).

Authentication failure: Access Denied

• Confirm the User ID and Password match the Starburst Galaxy service account credentials or the Starburst Enterprise user account.
• For Galaxy, verify that the service account has not been deactivated or had its password rotated.
• Test the same credentials in the Starburst Galaxy Query Editor or Enterprise query interface before diagnosing the Talend connection.

Query error: [Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive.
• Confirm the Starburst user account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst query interface before embedding it in the Talend component.

Slow job performance

• Push filtering predicates into the SQL WHERE clause in the tDBInput query rather than relying on Talend tFilterRow components downstream.
• Select only required columns rather than using SELECT *.
• Review the Starburst query history to identify slow-running queries and optimise at the catalog or connector level.

References

• Trino JDBC driver (Maven Central)
• Starburst Galaxy documentation
• Talend Studio documentation

Environment

• Talend Studio

This article describes how to connect Qlik Sense Enterprise on Windows (client-managed) to Starburst Galaxy using the Starburst ODBC driver. It covers driver installation, data connection configuration, and load script patterns for querying Starburst Galaxy catalogs via Trino SQL.

Content

• Prerequisites
• Install the Starburst ODBC Driver
• Configure an ODBC Data Source (DSN)
• Create a Data Connection in Qlik Sense
• Load Script Patterns
• Trino SQL Compatibility Notes
• Troubleshooting
• Related Content and References

Prerequisites

Before configuring the connection, ensure the following requirements are met on the Qlik Sense server or any node that will execute data load tasks:

• Qlik Sense Enterprise on Windows (client-managed), version February 2022 or later.
• Network connectivity from the Qlik Sense server to the Starburst Galaxy cluster endpoint (default port 443 over HTTPS/TLS).
• A Starburst Galaxy account with a running cluster and at least one catalog configured.
• A Starburst Galaxy service account username and password (or personal access token) with SELECT privileges on the target catalog and schema.
• Administrator access on the Windows server to install the ODBC driver and configure the DSN.

Install the Starburst ODBC Driver

Starburst provides a dedicated ODBC driver for Galaxy that is based on the Simba/Magnitude Trino ODBC driver. Use only the Galaxy-specific build to ensure compatibility with Galaxy authentication and TLS settings.

1. Download the Driver
   1. Log in to your Starburst Galaxy account at https://galaxy.starburst.io.
   2. Navigate to Settings > Clients & Tools > Drivers.
   3. Download the Windows 64-bit ODBC driver package (.msi or .zip).
   4. Copy the installer to the Qlik Sense server.
2. Install the Driver
   1. Run the installer as a local administrator.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select "System DSN" scope so that the Qlik Sense service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver even if the Qlik Sense process appears as 32-bit. Qlik Sense on Windows runs as a 64-bit process.

Configure an ODBC Data Source (DSN)

A System DSN makes the driver available to all Windows services, including the Qlik Sense Engine and Scheduler services.

1. Open ODBC Data Source Administrator (64-bit) from Windows Administrative Tools.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstGalaxy (used in the Qlik connection string)
   Host	<your-cluster>.galaxy.starburst.io
   Port	443
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP (username/password) or OAuth2 (token)
   SSL	Enabled (required for Galaxy)
   SSL Certificate	Use the system certificate store

   
   
   
5. Click Test Connection to verify connectivity. A successful test returns the Starburst Galaxy version.
6. Click OK to save.

If the test connection fails with a TLS error, ensure that the Starburst Galaxy root certificate is trusted by the Windows certificate store on the Qlik Sense Enterprise on Windows server.

Create a Data Connection in Qlik Sense

1. In the Qlik Sense Management Console (QMC), navigate to Data Connections.
2. Click Create new and select ODBC.
3. Select the StarburstGalaxy DSN created in Configure an ODBC Data Source (DSN).
4. Enter the service account credentials.
5. Set the connection name to: Data Nova Conference:Starburst Galaxy
   This name is required by the standard load script connection string used in Qlik apps that target this tenant.
6. Click Apply and test the connection.

The connection name Data Nova Conference:Starburst Galaxy is the canonical name used in all Qlik load scripts for this integration. Changing it requires updating all dependent scripts.

Load Script Patterns

The following patterns cover common scenarios for loading data from Starburst Galaxy into Qlik Sense Enterprise on Windows.

1. Establish the Connection
   
   Always use the following statement at the top of the load script tab that accesses Starburst Galaxy:

   LIB CONNECT TO 'Data Nova Conference:Starburst Galaxy'; 

2. Basic SQL SELECT

   Use three-part table names (catalog.schema.table) in all Trino SQL statements:

   Customers:
   SQL SELECT
      customer_id,
      customer_name,
      region,
      created_date
   FROM burstbank.retail.customers
   WHERE created_date >= DATE '2024-01-01';

3. Joining Tables

   Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume:

   Orders:
   SQL SELECT
      o.order_id,
      o.customer_id,
      o.order_date,
      o.total_amount,
      c.customer_name,
      c.region
   FROM burstbank.retail.orders o
   JOIN burstbank.retail.customers c ON o.customer_id = c.customer_id;

4. Incremental Load

   Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

   LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

   Transactions:
   SQL SELECT *
   FROM burstbank.retail.transactions
   WHERE transaction_date >= DATE '$(vLastLoadDate)';

Trino SQL Compatibility Notes

Starburst Galaxy uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed:

Troubleshooting

Connection fails in QMC

• Verify the DSN name matches exactly (case-sensitive) in the data connection configuration.
• Confirm the Qlik Sense service account has Read permission on the Windows registry key for the System DSN.
• Check that TCP port 443 is open outbound from the Qlik Sense server to the Galaxy cluster host.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive in some catalogs.
• Confirm the Galaxy service account has SELECT privileges on the target table.
• Test the same SQL in the Starburst Galaxy Query Editor before embedding it in the Qlik load script.

Slow load performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses.
• Select only required columns rather than using SELECT *.
• Consider using Starburst Galaxy materialized views for frequently queried aggregations.

Related Content and References

• Starburst Galaxy documentation
• Qlik ODBC connector documentation

Environment

• Qlik Sense Enterprise on Windows

This article describes how to connect Qlik Sense Enterprise on Windows (client-managed) to Starburst Enterprise (self-managed, on-premises or private cloud) using the Starburst ODBC driver. It covers driver installation, data connection configuration, and load script patterns for querying Starburst Enterprise catalogs via Trino SQL.

Content

• Prerequisites
• Install the Starburst ODBC Driver
• Configure an ODBC Data Source (DSN)
• Create a Data Connection in Qlik Sense
• Load Script Patterns
• Trino SQL Compatibility Notes
• Differences vs. Starburst Galaxy
• Troubleshooting
• Related Content and References

Prerequisites

Before configuring the connection, ensure the following requirements are met on the Qlik Sense server or any node that will execute data load tasks:

• Qlik Sense Enterprise on Windows (client-managed), version February 2022 or later.
• Network connectivity from the Qlik Sense server to the Starburst Enterprise coordinator node (default port 8443 for HTTPS/TLS, or 8080 for HTTP).
• A Starburst Enterprise deployment with at least one catalog configured and the coordinator accessible from the Qlik network segment.
• A Starburst Enterprise user account with SELECT privileges on the target catalog and schema.
• Administrator access on the Windows server to install the ODBC driver and configure the DSN.
• The Starburst Enterprise TLS certificate (or the CA certificate chain) if using HTTPS, to be trusted by the Windows server.

Install the Starburst ODBC Driver

Starburst provides a dedicated ODBC driver for Starburst Enterprise based on the Simba/Magnitude Trino ODBC driver. Download the Enterprise-specific build from your Starburst Enterprise distribution. Do not use the Galaxy driver.

1. Download the Driver
   1. Log in to the Starburst Enterprise software portal or obtain the driver package from your Starburst account representative.
   2. Download the Windows 64-bit ODBC driver package (.msi) that matches your Starburst Enterprise version.
   3. Copy the installer to the Qlik Sense server.
2. Install the Driver
   1. Run the installer as a local administrator.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select "System DSN" scope so that the Qlik Sense service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver. Qlik Sense on Windows runs as a 64-bit process regardless of the label shown in Windows Task Manager.

Configure an ODBC Data Source (DSN)

A System DSN makes the driver available to all Windows services, including the Qlik Sense Engine and Scheduler services.

1. Open ODBC Data Source Administrator (64-bit) from Windows Administrative Tools.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstEnterprise (used in the Qlik connection string)
   Host	<coordinator-hostname-or-ip>
   Port	8443 (HTTPS) or 8080 (HTTP — not recommended for production)
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP, Kerberos, or Password (depends on Starburst Enterprise configuration)
   SSL	Enabled for HTTPS deployments; disabled for HTTP-only test environments
   SSL Certificate	Path to the PEM or PFX certificate file, or use the system certificate store if the CA is trusted

    

5. Click Test Connection to verify connectivity. A successful test returns the Starburst Enterprise version.
6. Click OK to save.

If Kerberos authentication is required, ensure the Qlik Sense service account has a valid Kerberos ticket and that the Kerberos configuration file (krb5.ini) is present at C:\Windows\krb5.ini on the Qlik Sense server.

Create a Data Connection in Qlik Sense

1. In the Qlik Sense Management Console (QMC), navigate to Data Connections.
2. Click Create new and select ODBC.
3. Select the StarburstEnterprise DSN created in Configure an ODBC Data Source (DSN)
4. Enter the service account credentials appropriate to your authentication method (LDAP username/password, or leave blank for Kerberos SSO).
5. Set the connection name to reflect your deployment (for example: Starburst Enterprise:Production).
   Update the LIB CONNECT TO statement in your load scripts to match the connection name you choose.
6. Click Apply and test the connection.

Unlike Starburst Galaxy, the connection name for Starburst Enterprise deployments can be customised to match your environment. Ensure the name is consistent across all load scripts that use this connection.

Load Script Patterns

The following patterns cover common scenarios for loading data from Starburst Enterprise into Qlik Sense. The patterns are identical to those used with Starburst Galaxy; the only difference is the connection name in the LIB CONNECT TO statement.

1. Establish the Connection
   
   Replace the connection name with the one configured in Create a Data Connection in Qlik Sense:

   LIB CONNECT TO 'Starburst Enterprise:Production'; 

2. Basic SQL SELECT

   Use three-part table names (catalog.schema.table) in all Trino SQL statements:

   Customers:
   SQL SELECT
       customer_id,
       customer_name,
       region,
       created_date
   FROM hive.sales.customers
   WHERE created_date >= DATE '2024-01-01';

3. Joining Tables

   Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume:

   Orders:
   SQL SELECT
       o.order_id,
       o.customer_id,
       o.order_date,
       o.total_amount,
       c.customer_name,
       c.region
   FROM hive.sales.orders o
   JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

4. Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

   LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

   Transactions:
   SQL SELECT *
   FROM hive.sales.transactions
   WHERE transaction_date >= DATE '$(vLastLoadDate)';

Trino SQL Compatibility Notes

Starburst Enterprise uses the Trino query engine. The same Trino SQL conventions apply as for Starburst Galaxy:

Differences vs. Starburst Galaxy

The table below summarises the key differences between the two deployment models relevant to a Qlik Sense integration:

Troubleshooting

Connection fails in QMC

• Verify the DSN name matches exactly (case-sensitive) in the data connection configuration.
• Confirm the Qlik Sense service account has Read permission on the Windows registry key for the System DSN.
• Check that the configured TCP port (8443 or 8080) is open outbound from the Qlik Sense server to the Starburst Enterprise coordinator.
• If using HTTPS, verify that the Starburst Enterprise TLS certificate or its CA is trusted by the Windows server certificate store.

Kerberos authentication failures

• Confirm that the krb5.ini file exists at C:\Windows\krb5.ini and contains the correct KDC settings for your domain.
• Verify that the Qlik Sense Windows service is running as a domain account (not Local System) with a valid Kerberos principal.
• Test Kerberos connectivity separately using the kinit utility before diagnosing ODBC issues.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct: catalog, schema, and table names are case-sensitive in some catalogs.
• Confirm the Starburst user account has SELECT privileges on the target table.
• Test the same SQL in the Starburst Enterprise query interface before embedding it in the Qlik load script.

Slow load performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses.
• Select only required columns rather than using SELECT *.
• Review the Starburst Enterprise query history to identify slow-running queries and optimise at the catalog/connector level.

Related Content and References

• Starburst Galaxy documentation
• Qlik ODBC connector documentation

Environment

• Qlik Sense Enterprise on Windows

This article describes how to connect Qlik Cloud Analytics to Starburst Enterprise (self-managed, on-premises, or private cloud) using a Qlik Data Gateway - Direct Access and the Starburst ODBC driver. It covers gateway installation and registration, ODBC driver and DSN configuration on the gateway host, TLS certificate handling for self-managed deployments, and data connection setup in Qlik Cloud. It is intended for Qlik Cloud tenants that need to query Starburst Enterprise catalogs directly from Qlik Cloud apps and scripts.

Content

• Architecture Overview
• Prerequisites
• Qlik Data Gateway - Direct Access Requirement
• Install the Starburst ODBC Driver on the Gateway Host
• Configure TLS Certificate Trust on the Gateway Host
• Configure an ODBC DSN on the Gateway Host
• Install and Register the Qlik Data Gateway - Direct Access
• Create a Data Connection in Qlik Cloud
• Load Script Patterns
• Trino SQL Compatibility Notes
• Comparison: Starburst Enterprise vs. Starburst Galaxy
• Troubleshooting
• Related Content and References

Architecture Overview

Qlik Cloud Analytics is a fully managed SaaS platform. Because Starburst Enterprise runs within a customer-managed network, a Qlik Data Gateway - Direct Access must be deployed within the same network as, or with routable access to, the Starburst Enterprise coordinator node. The gateway acts as a secure proxy, relaying data load requests from Qlik Cloud to Starburst Enterprise over the ODBC connection configured on the gateway host.

The connection flow will look as follows:

Qlik Cloud tenant → Qlik Data Gateway (Direct Access) → Starburst ODBC DSN → Starburst Enterprise coordinator

The gateway host is a Windows or Linux server that you manage. It must have outbound HTTPS access to both the Qlik Cloud tenant (port 443) and the Starburst Enterprise coordinator (port 8443 for HTTPS, or 8080 for HTTP). The gateway is typically deployed inside the same private network as the Starburst Enterprise cluster.

Prerequisites

Before beginning, ensure the following requirements are met:

• A Qlik Cloud tenant with a Qlik Cloud Analytics subscription.
• Tenant Admin or Space Admin rights in Qlik Cloud to create data connections.
• A dedicated Windows or Linux server to host the Qlik Data Gateway - Direct Access (minimum: 4 vCPU, 8 GB RAM, Windows Server 2016+ or RHEL/Ubuntu 20.04+), deployed inside or with routable access to the Starburst Enterprise network.
• Network connectivity from the gateway host to the Starburst Enterprise coordinator node (port 8443 for HTTPS, or 8080 for HTTP).
• Outbound HTTPS access (port 443) from the gateway host to your Qlik Cloud tenant URL (e.g. https://<tenant>.us.qlikcloud.com).
• The Starburst Enterprise TLS certificate or CA certificate chain (if using HTTPS with a self-signed or private CA certificate), to be imported into the Windows certificate store on the gateway host.
• A Starburst Enterprise user account with SELECT privileges on the target catalog and schema.
• Administrator access on the gateway host to install software, configure ODBC System DSNs, and manage the Windows certificate store.

Qlik Data Gateway - Direct Access Requirement

A Qlik Data Gateway - Direct Access is required to connect Qlik Cloud Analytics to Starburst Enterprise. Unlike Qlik Sense on Windows (client-managed), Qlik Cloud does not execute data load scripts directly. All connections to on-premises or privately hosted data sources are routed through the gateway.

A Qlik Data Gateway - Direct Access must be installed and registered to your Qlik Cloud tenant before a Starburst ODBC data connection can be created or used. Attempting to create the connection without a registered gateway will result in an error.

Because Starburst Enterprise runs inside a customer-managed network, the gateway host is typically deployed within that same network. This ensures the gateway can reach the Starburst Enterprise coordinator without requiring firewall rules that expose the coordinator to the public internet.

The gateway must be installed on a host that:

• Has network access to the Starburst Enterprise coordinator on the configured port (8443 for HTTPS or 8080 for HTTP).
• Has the Starburst Enterprise ODBC driver been installed and a System DSN configured (see Install the Starburst ODBC Driver on the Gateway Host, and Configure an ODBC DSN on the Gateway Host).
• Has outbound HTTPS access to the Qlik Cloud tenant on port 443.
• Has the Starburst Enterprise TLS certificate or CA chain been trusted in its certificate store (see Configure TLS Certificate Trust on the Gateway Host).
• Runs continuously. The gateway must be active whenever a Qlik Cloud app or script loads data from Starburst.

blockquote For high availability, install the gateway on two or more hosts within the Starburst Enterprise network and register all of them to the same Qlik Cloud tenant. Qlik Cloud will distribute data load requests across available gateway instances.

Install the Starburst ODBC Driver on the Gateway Host

The Starburst ODBC driver must be installed on the gateway host, not on the Qlik Cloud infrastructure. Qlik Cloud reads data through the gateway, so the driver must be present and configured where the gateway is running.

Download the Driver

Use the Starburst Enterprise-specific ODBC driver build, not the Starburst Galaxy driver.

1. Log in to the Starburst Enterprise software portal or obtain the driver package from your Starburst account representative.
2. Download the Windows 64-bit ODBC driver package (.msi) that matches your Starburst Enterprise version.
3. Copy the installer to the gateway host.

Install the Driver

1. Run the installer as a local administrator on the gateway host.
2. Accept the licence agreement and choose the default installation directory.
3. When prompted, select System DSN scope so that the Qlik Data Gateway service account can access the driver.
4. Complete the installation. No restart is required.

Install the 64-bit driver on the gateway host. The Qlik Data Gateway - Direct Access runs as a 64-bit process and requires the 64-bit ODBC driver. Use ODBC Data Source Administrator (64-bit) for all DSN configuration.

Configure TLS Certificate Trust on the Gateway Host

Starburst Enterprise deployments commonly use HTTPS with a certificate signed by a private or internal CA. Unlike Starburst Galaxy, whose certificate is signed by a publicly trusted CA, the Starburst Enterprise certificate chain may not be automatically trusted by Windows. The certificate must be imported into the Windows certificate store on the gateway host before the ODBC DSN can establish a TLS connection.

Obtain the Certificate

1. Obtain the Starburst Enterprise TLS certificate or the root CA certificate that signed it from your Starburst Enterprise administrator.
2. The certificate file is typically in PEM (.pem, .crt) or DER (.cer) format.
3. Copy the certificate file to the gateway host.

Import the Certificate into the Windows Certificate Store

1. Open the Microsoft Management Console (MMC) on the gateway host: press Win + R, type mmc, and press Enter.
2. In MMC, select File > Add/Remove Snap-in.
3. Add the Certificates snap-in and select Computer account when prompted.
4. Navigate to Trusted Root Certification Authorities > Certificates.
5. Right-click and select All Tasks > Import.
6. Follow the Certificate Import Wizard to import the Starburst Enterprise CA certificate.
7. Confirm the certificate appears in the Trusted Root Certification Authorities store.

If the Starburst Enterprise deployment uses a certificate signed by an intermediate CA, import the full chain: the root CA certificate and any intermediate CA certificates. Importing only the leaf (server) certificate is not sufficient for TLS validation.

Verify Certificate Trust

After importing the certificate, verify that the gateway host trusts the Starburst Enterprise endpoint by opening a browser on the gateway host and navigating to the coordinator URL (such as https://<coordinator-host>:8443). If the page loads without a certificate warning, the certificate chain is trusted correctly.

This step is only required for HTTPS deployments with private or self-signed certificates. It is not applicable for Starburst Enterprise using a certificate signed by a publicly trusted CA (such as Let's Encrypt, DigiCert).

Configure an ODBC DSN on the Gateway Host

A System DSN must be created on the gateway host. This is the DSN that Qlik Cloud will reference when the data connection is used in a load script or app.

1. Open ODBC Data Source Administrator (64-bit) on the gateway host.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the driver list and click Finish.

4. Configure the DSN with the following settings:

   Setting	Value
   DSN Name	StarburstEnterprise (must match the name used when creating the Qlik Cloud data connection)
   Host	<coordinator-hostname-or-ip>
   Port	8443 (HTTPS) or 8080 (HTTP — not recommended for production)
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP, Kerberos, or password (depends on Starburst Enterprise configuration)
   SSL	Enabled for HTTPS deployments; disabled for HTTP-only test environments
   SSL Certificate	Use the system certificate store (after completing Configure TLS Certificate Trust on the Gateway Host)

    

5. Click Test Connection to verify connectivity from the gateway host to the Starburst Enterprise coordinator. A successful test returns the Starburst Enterprise version.
6. Click OK to save the DSN.

Test the DSN connection while logged in as the same Windows service account that will run the Qlik Data Gateway service. DSN access permissions are per-user for User DSNs and per-machine for System DSNs. Always use System DSN for service accounts.

If Kerberos authentication is required, ensure the Qlik Data Gateway service account has a valid Kerberos principal and that the Kerberos configuration file (krb5.ini) is present at C:\Windows\krb5.ini on the gateway host before configuring the DSN.

Install and Register the Qlik Data Gateway - Direct Access

The Qlik Data Gateway - Direct Access installer is downloaded from the Qlik Cloud Administration Center and registers the gateway to your tenant during installation. The gateway itself is product-agnostic, meaning the installation steps are identical for Starburst Galaxy and Starburst Enterprise connections. 

Download the Installer

1. In Qlik Cloud, open the Qlik Cloud Administration activity center
2. Navigate to Data Gateways.
3. Click Add and select Direct Access Gateway.
4. Follow the on-screen instructions to download the installer for the gateway host operating system.

Install the Gateway

1. Copy the installer to the gateway host.
2. Run the installer as a local administrator.
3. When prompted, enter the Qlik Cloud tenant URL and an API key.
   
   See Generating and managing API keys for instructions on how to generate an API key.
   
   
4. Complete the installation. The gateway service will start automatically and register with the Qlik Cloud tenant.

Verify the Gateway is Registered

1. Return to the Qlik Cloud Administration activity center > Data Gateways.
2. Confirm the gateway appears in the list with a Connected status.
3. If the gateway shows a Disconnected status, check outbound HTTPS connectivity from the gateway host to the tenant URL on port 443.

The gateway service runs under a Windows service account (or as a systemd service on Linux). Ensure this account has Read access to the System DSN registry keys and is granted Log on as a service rights on Windows. For Kerberos authentication, the service account must also have a valid Kerberos ticket.

Create a Data Connection in Qlik Cloud

Once the gateway is registered and the ODBC DSN is configured on the gateway host, create the ODBC data connection in Qlik Cloud.

1. In Qlik Cloud, go to Create
2. Choose Data connection from the available actions and choose your Space
3. In the connector list, search for and select ODBC.
4. In the connection configuration panel, set the following:
   
   

   Field	Value
   Data gateway	Select the Direct Access Gateway registered in Install and Register the Qlik Data Gateway - Direct Access
   DSN	StarburstEnterprise (the System DSN configured on the gateway host in Configure an ODBC DSN on the Gateway Host)
   Username	Starburst Enterprise user account username (leave blank for Kerberos SSO)
   Password	Starburst Enterprise user account password (leave blank for Kerberos SSO)
   Connection name	Administrator-defined (e.g. Starburst Enterprise:Production)

5. Click Create.
6. Test the connection. The test runs through the gateway, confirming end-to-end connectivity from Qlik Cloud through the gateway to Starburst Enterprise. 

Unlike Starburst Galaxy, the connection name for Starburst Enterprise is administrator-defined and can reflect the deployment environment (e.g. Starburst Enterprise:Production, Starburst Enterprise:Staging). Ensure the name is used consistently in all load scripts that reference this connection.

Load Script Patterns

Load scripts in Qlik Cloud apps use the same patterns as Qlik Sense on Windows. The LIB CONNECT TO connection name must match the data connection created in Create a Data Connection in Qlik Cloud.

Establish the Connection

Replace the connection name with the one configured in Create a Data Connection in Qlik Cloud:

LIB CONNECT TO 'Starburst Enterprise:Production'; 

Basic SQL SELECT

Use three-part table names (catalog.schema.table) in all Trino SQL statements:

Customers:
SQL SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM hive.sales.customers
WHERE created_date >= DATE '2024-01-01';

Joining Tables

Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume through the gateway:

Orders:
SQL SELECT
    o.order_id,
    o.customer_id,
    o.order_date,
    o.total_amount,
    c.customer_name,
    c.region
FROM hive.sales.orders o
JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

Incremental Load

Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

Transactions:
SQL SELECT *
FROM hive.sales.transactions
WHERE transaction_date >= DATE '$(vLastLoadDate)';

Avoiding Synthetic Keys

Rename non-key fields that share names across tables by prefixing the table name. Island tables should be commented out:

Orders:
SQL SELECT
    order_id,
    customer_id, // Key — keep as-is
    order_date AS Order_order_date, // Renamed to avoid synthetic key
    total_amount AS Order_total_amount
FROM hive.sales.orders;

In Qlik Cloud, scheduled reloads run through the gateway. Ensure the gateway service is running and the gateway host has network access to the Starburst Enterprise coordinator at the time scheduled reloads are triggered.

Trino SQL Compatibility Notes

Starburst Enterprise uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed in all Qlik load script SQL statements:

Comparison: Starburst Enterprise vs. Starburst Galaxy

The table below summarises the key differences in the Qlik Cloud connection setup between Starburst Enterprise and Starburst Galaxy:

Troubleshooting

Gateway shows Disconnected in Qlik Cloud

• Verify outbound HTTPS connectivity from the gateway host to the Qlik Cloud tenant URL on port 443.
• Check that the gateway service is running: in Windows Services, look for Qlik Data Gateway - Direct Access.
• Review the gateway log files at %ProgramData%\Qlik\DataGateway\logs for connection errors.
• Confirm the API key used during registration has not been revoked in Qlik Cloud.

Data connection test fails: DSN not found

• Confirm the DSN name in the Qlik Cloud data connection matches exactly (case-sensitive) the System DSN name on the gateway host.
• Open ODBC Data Source Administrator (64-bit) on the gateway host and verify the DSN exists under the System DSN tab.
• Ensure the Qlik Data Gateway service account has access to the System DSN. Restart the gateway service after creating or modifying the DSN.

Data connection test fails: SSL/TLS error

• Confirm that the CA certificate chain for the Starburst Enterprise deployment has been imported into the Trusted Root Certification Authorities store on the gateway host.
• The test connection runs on the gateway host, not in Qlik Cloud. All certificate issues must be resolved on the gateway host.
• Verify that the SSL Certificate setting in the DSN is set to use the system certificate store, not a specific file path that may no longer be valid.

Kerberos authentication failures

• Confirm that the krb5.ini file exists at C:\Windows\krb5.ini and contains the correct KDC and realm settings for your domain.
• Verify that the Qlik Data Gateway Windows service is running as a domain account (not Local System) with a valid Kerberos principal.
• Test Kerberos connectivity separately using the kinit utility before diagnosing ODBC issues.
• After any changes to krb5.ini or the service account configuration, restart the Qlik Data Gateway service.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct. Catalog, schema, and table names are case-sensitive.
• Confirm the Starburst Enterprise user account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst Enterprise query interface before embedding it in the Qlik load script.

Scheduled reload fails, but manual reload succeeds

• Scheduled reloads run through the gateway under the service account context. Ensure the gateway service account has the same DSN access and Kerberos credentials as the interactive user.
• Verify the gateway is in a Connected state at the time the reload is scheduled.
• Check the Qlik Cloud reload log for gateway timeout errors and increase the gateway connection timeout if necessary.

Slow reload performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses. All data passes through the gateway, so minimising row count reduces transfer time.
• Select only required columns rather than using SELECT *.
• Consider co-locating the gateway host in the same network segment as the Starburst Enterprise coordinator to minimise latency.
• Review the Starburst Enterprise query history to identify slow-running queries and optimise at the catalog or connector level.

Related Content and References

• Qlik Data Gateway - Direct Access documentation 
• Starburst Enterprise documentation 
• Qlik Cloud Data Sources

Environment

• Qlik Cloud

This article describes how to connect Qlik Cloud Analytics to Starburst Galaxy using a Qlik Data Gateway - Direct Access and the Starburst ODBC driver. It covers gateway installation and registration, ODBC driver and DSN configuration on the gateway host, and data connection setup in Qlik Cloud. It is intended for Qlik Cloud tenants that need to query Starburst Galaxy catalogs directly from Qlik Cloud apps and scripts.

Content

• Architecture Overview
• Prerequisites
• Qlik Data Gateway - Direct Access Requirement
• Install the Starburst ODBC Driver on the Gateway Host
• Configure an ODBC DSN on the Gateway Host
• Install and Register the Qlik Data Gateway - Direct Access
• Create a Data Connection in Qlik Cloud
• Load Script Patterns
• Trino SQL Compatibility Notes
• Comparison: Qlik Cloud vs. Qlik Sense on Windows
• Troubleshooting
• Related Content and References

Architecture Overview

Qlik Cloud Analytics is a fully managed SaaS platform. Because Starburst Galaxy is not directly accessible from the Qlik Cloud infrastructure without network configuration, a Qlik Data Gateway - Direct Access must be deployed within the same network as, or with routable access to, the Starburst Galaxy cluster endpoint. The gateway acts as a secure proxy, relaying data load requests from Qlik Cloud to Starburst Galaxy over the ODBC connection configured on the gateway host.

The connection flow will look as follows:

Qlik Cloud tenant → Qlik Data Gateway (Direct Access) → Starburst ODBC DSN → Starburst Galaxy cluster

The gateway host is a Windows or Linux server that you manage. It must have outbound HTTPS access to both the Qlik Cloud tenant (port 443) and the Starburst Galaxy cluster endpoint (port 443).

Prerequisites

Before beginning, ensure the following requirements are met:

• A Qlik Cloud tenant with a Qlik Cloud Analytics subscription.
• Tenant Admin or Space Admin rights in Qlik Cloud to create data connections.
• A dedicated Windows or Linux server to host the Qlik Data Gateway - Direct Access (minimum: 4 vCPU, 8 GB RAM, Windows Server 2016+ or RHEL/Ubuntu 20.04+).

  A Qlik Data Gateway - Direct Access must be installed and registered to your Qlik Cloud tenant before a Starburst ODBC data connection can be created or used. Attempting to create the connection without a registered gateway will result in an error.

• Network connectivity from the gateway host to the Starburst Galaxy cluster endpoint (port 443, HTTPS/TLS).
• Outbound HTTPS access (port 443) from the gateway host to your Qlik Cloud tenant URL (such as https://<tenant>.us.qlikcloud.com).
• A Starburst Galaxy service account with SELECT privileges on the target catalog and schema.
• Administrator access on the gateway host to install software and configure ODBC System DSNs.

Qlik Data Gateway - Direct Access Requirement

A Qlik Data Gateway - Direct Access is required to connect Qlik Cloud Analytics to Starburst Galaxy. All connections to on-premises or privately hosted data sources are routed through the gateway.

The gateway must be installed on a host that:

• Has network access to the Starburst Galaxy cluster on port 443.
• Has the Starburst ODBC driver installed and a System DSN configured (see Install the Starburst ODBC Driver on the Gateway Host, and Configure an ODBC DSN on the Gateway Host).
• Has outbound HTTPS access to the Qlik Cloud tenant on port 443.
• Runs continuously. The gateway must be active whenever a Qlik Cloud app or script loads data from Starburst.

For high availability, install the gateway on two or more hosts and register all of them to the same Qlik Cloud tenant. Qlik Cloud will distribute data load requests across available gateway instances.

Install the Starburst ODBC Driver on the Gateway Host

The Starburst ODBC driver must be installed on the gateway host. Qlik Cloud reads data through the gateway, so the driver must be present and configured where the gateway is running.

1. Download the Driver
   1. Log in to your Starburst Galaxy account at https://galaxy.starburst.io.
   2. Navigate to Settings > Clients & Tools > Drivers.
   3. Download the Windows 64-bit ODBC driver package (.msi or .zip) appropriate for the gateway host operating system.
   4. Copy the installer to the gateway host.
2. Install the Driver
   1. Run the installer as a local administrator on the gateway host.
   2. Accept the licence agreement and choose the default installation directory.
   3. When prompted, select System DSN scope so that the Qlik Data Gateway service account can access the driver.
   4. Complete the installation. No restart is required.

Install the 64-bit driver on the gateway host. The Qlik Data Gateway - Direct Access runs as a 64-bit process and requires the 64-bit ODBC driver. Use ODBC Data Source Administrator (64-bit) for all DSN configuration.

Configure an ODBC DSN on the Gateway Host

A System DSN must be created on the gateway host. This is the DSN that Qlik Cloud will reference when the data connection is used in a load script or app.

1. Open ODBC Data Source Administrator (64-bit) on the gateway host.
2. Click the System DSN tab, then click Add.
3. Select the Starburst ODBC Driver from the driver list and click Finish.
4. Configure the DSN with the following settings:
   
   

   Setting	Value
   DSN Name	StarburstGalaxy (must match the name used when creating the Qlik Cloud data connection)
   Host	<your-cluster>.galaxy.starburst.io
   Port	443
   Catalog	Leave blank (set per query or in the Qlik load script)
   Authentication	LDAP (username/password) or OAuth2 (token)
   SSL	Enabled (required for Galaxy)
   SSL Certificate	Use system certificate store

5. Click Test Connection to verify connectivity from the gateway host to Starburst Galaxy. A successful test returns the Starburst Galaxy version. 
6. Click OK to save the DSN.

Test the DSN connection while logged in as the same Windows service account that will run the Qlik Data Gateway service. DSN access permissions are per-user for User DSNs and per-machine for System DSNs. Always use System DSN for service accounts.

Install and Register the Qlik Data Gateway - Direct Access

The Qlik Data Gateway - Direct Access installer is downloaded from the Qlik Cloud Administration activity center and registers the gateway to your tenant during installation.

1. Download the Installer
   1. In Qlik Cloud, open the Qlik Cloud Administration activity center.
   2. Navigate to Data Gateways.
   3. Click Add and select Direct Access Gateway.
   4. Follow the on-screen instructions to download the installer for the gateway host operating system.
2. Install the Gateway
   1. Copy the installer to the gateway host.
   2. Run the installer as a local administrator.
   3. When prompted, enter the Qlik Cloud tenant URL and your API key.
      
      See Generating and managing API keys for instructions on how to generate an API key.
      
      
   4. Complete the installation. The gateway service will start automatically and register with the Qlik Cloud tenant.
3. Verify the Gateway is registered
   1. Return to the Qlik Cloud Administration activity center > Data Gateways.
   2. Confirm the gateway appears in the list with a Connected status.
      If the gateway shows a Disconnected status, check outbound HTTPS connectivity from the gateway host to the tenant URL on port 443.

The gateway service runs under a Windows service account (or as a systemd service on Linux). Ensure this account has Read access to the System DSN registry keys and is granted Log on as a service rights on Windows.

Create a Data Connection in Qlik Cloud

Once the gateway is registered and the ODBC DSN is configured on the gateway host, create the ODBC data connection in Qlik Cloud.

1. In Qlik Cloud, go to Create
2. Choose Data connection from the available actions and choose your Space
3. In the connector list, search for and select ODBC.
4. In the connection configuration panel, set the following:
   
   

   Field	Value
   Data gateway	Select the Direct Access Gateway registered in Install and Register the Qlik Data Gateway - Direct Access
   DSN	StarburstGalaxy (the System DSN configured on the gateway host in Configure an ODBC DSN on the Gateway Host)
   Username	Starburst Galaxy service account username
   Password	Starburst Galaxy service account password or personal access token
   Connection name	Data Nova Conference:Starburst Galaxy

5. Click Create.
6. Use the Test button to verify the connection. The test runs through the gateway, confirming end-to-end connectivity.

The connection name Data Nova Conference:Starburst Galaxy is the canonical name used in all Qlik load scripts for this integration. Changing it requires updating all dependent scripts. This name is consistent across Qlik Sense Enterprise on Windows and Qlik Cloud (this article).

Load Script Patterns

Load scripts in Qlik Cloud apps use the same patterns as Qlik Sense on Windows. The LIB CONNECT TO connection name must match the data connection created in Create a Data Connection in Qlik Cloud.

Establish the Connection

Always use the following statement at the top of the load script tab that accesses Starburst Galaxy:

LIB CONNECT TO 'Data Nova Conference:Starburst Galaxy'; 

Basic SQL SELECT

Use three-part table names (catalog.schema.table) in all Trino SQL statements:

Customers:
SQL SELECT
    customer_id,
    customer_name,
    region,
    created_date
FROM hive.sales.customers
WHERE created_date >= DATE '2024-01-01';

Joining Tables

Perform joins in SQL rather than in the Qlik data model to reduce data transfer volume through the gateway:

Orders:
SQL SELECT
    o.order_id,
    o.customer_id,
    o.order_date,
    o.total_amount,
    c.customer_name,
    c.region
FROM hive.sales.orders o
JOIN hive.sales.customers c ON o.customer_id = c.customer_id;

Incremental Load

Use Qlik variables to pass date parameters into the SQL predicate for incremental data loads:

LET vLastLoadDate = Date(Today()-1, 'YYYY-MM-DD');

Transactions:
SQL SELECT *
FROM hive.sales.transactions
WHERE transaction_date >= DATE '$(vLastLoadDate)';

Avoiding Synthetic Keys

Rename non-key fields that share names across tables by prefixing the table name. Island tables should be commented out:

Orders:
SQL SELECT
    order_id,
    customer_id, // Key — keep as-is
    order_date AS Order_order_date, // Renamed to avoid synthetic key
    total_amount AS Order_total_amount
FROM hive.sales.orders;

In Qlik Cloud, scheduled reloads run through the gateway. Ensure the gateway service is running and the gateway host has network access to Starburst Galaxy at the time scheduled reloads are triggered.

Trino SQL Compatibility Notes

Starburst Galaxy uses the Trino query engine. The following SQL conventions differ from standard ANSI SQL and must be observed in all Qlik load script SQL statements:

Comparison: Qlik Cloud vs. Qlik Sense on Windows

The table below summarises the key differences in the Starburst connection setup between Qlik Cloud Analytics and Qlik Sense Enterprise on Windows (client-managed):

Troubleshooting

Gateway shows Disconnected in Qlik Cloud

• Verify outbound HTTPS connectivity from the gateway host to the Qlik Cloud tenant URL on port 443.
• Check that the gateway service is running: in Windows Services, look for Qlik Data Gateway - Direct Access.
• Review the gateway log files at %ProgramData%\Qlik\DataGateway\logs for connection errors.
• Confirm the API key used during registration has not been revoked in Qlik Cloud.

Data connection test fails: DSN not found

• Confirm the DSN name in the Qlik Cloud data connection matches exactly (case-sensitive) the System DSN name on the gateway host.
• Open ODBC Data Source Administrator (64-bit) on the gateway host and verify the DSN exists under the System DSN tab.
• Ensure the Qlik Data Gateway service account has access to the System DSN. Restart the gateway service after creating or modifying the DSN.

Data connection test fails: SSL/TLS error

• Confirm that the Windows certificate store on the gateway host trusts the CA certificate chain for *.galaxy.starburst.io.
• The test connection runs on the gateway host, not in Qlik Cloud. All certificate issues must be resolved on the gateway host.

Load script error: [Starburst][Trino] Error executing query

• Verify the three-part table name is correct. Catalog, schema, and table names are case-sensitive.
• Confirm the Starburst Galaxy service account has SELECT privileges on the target table.
• Test the SQL directly in the Starburst Galaxy Query Editor before embedding it in the Qlik load script.

Scheduled reload fails, but manual reload succeeds

• Scheduled reloads run through the gateway under the service account context. Ensure the gateway service account has the same DSN access as the interactive user.
• Verify the gateway is in a Connected state at the time the reload is scheduled.
• Check the Qlik Cloud reload log for gateway timeout errors and increase the gateway connection timeout if necessary.

Slow reload performance

• Push filtering predicates into the SQL WHERE clause rather than relying on Qlik WHERE clauses. All data passes through the gateway, so minimising row count reduces transfer time.
• Select only required columns rather than using SELECT *.
• Consider co-locating the gateway host in the same network region as the Starburst Galaxy cluster to minimise latency.

Related Content and References

• Qlik Data Gateway - Direct Access documentation 
• Starburst Galaxy documentation 
• Qlik Cloud Data Sources

Environment

• Qlik Cloud

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

During Change Data Capture (CDC) replication, the target Oracle database experienced a transient CPU spike.

Database performance monitoring identified that the high CPU consumption was driven by the following automated bulk query generated by Qlik Replicate:

UPDATE /*+ PARALLEL(tempview) */ ( SELECT /*+ PARALLEL("CDC"."CATB_ENTRIES_DECOUPLING") PARALLEL("QLIK_TARGET"."attrep_changes69C66930_0000001") */ ...

The underlying cause of the resource spike was the execution of this query using aggressive Oracle PARALLEL hints, which exhausted available target DB CPU/memory resources.

Resolution

To prevent future resource contention and CPU/memory alerts in the target database, parallelism hints must be disabled or tuned within Qlik Replicate. This involves modifying two internal parameters across the Full Load and CDC stages: bulkUseParallel and directPathParallelLoad.

bulkUseParallel is for CDC / Change Processing and is enabled by default (true). It instructs Qlik Replicate to inject the Oracle PARALLEL hint into bulk DML statements for better target performance.

Setting it to false stops queries such as UPDATE /*+ PARALLEL(tempview) */ ... from executing in parallel, preventing CPU spikes.

This may cause a slight performance degradation during high-volume CDC processing.

directPathParallelLoad is for Full Load and enabled by default (true). It enables Direct Path loading using parallel processing only during the initial Full Load phase. It has no impact on the daily CDC.

Setting it to false proactively protects the DB during table reloads.

Will likely increase the time required to complete Full Load operations.

How to set the Internal Parameters in Qlik Replicate:

1. Navigate to Manage Endpoint Connection → Targets and select your Endpoint
2. Open the Advanced tab and select Internal Parameters
3. Add bulkUseParallel and directPathParallelLoad
4. Untick the Value checkbox to disable them
   
   
   
   
5. Click OK

Environment

• Qlik Replicate

After recreating the Amazon EMR cluster and updating the Storage Zone configuration in Qlik Compose with the new EMR master IP, the connection validation failed with the following error:

Storage Zone connection failed  
COMPOSE-E-ENGCONFAI  
Java connection failed  
SYS-E-GNRLERR, Required driver class not found:  
com.simba.hive.jdbc41.HS2Driver

This issue caused the Storage Zone connection to fail, impacting data pipeline operations.

Resolution

1. Verify that the required Hive JDBC driver (HiveJDBC41.jar) is present in the following directory on the Qlik Compose Agent server:
   
   <Compose Install directory>/java/jdbc/
   
   
2. Restart the Qlik Compose Agent service to ensure the driver is loaded:
   
   

   sudo service compose-agent stop
   sudo service compose-agent start

3. Validate the service is running:
   
   

   sudo service compose-agent status

4. Retest the Storage Zone connection in Qlik Compose UI, which succeeded after the restart.

Cause

The Hive JDBC driver (HiveJDBC41.jar) required for connecting to EMR HiveServer2 was either:

• Missing from the Compose Agent jdbc directory, or
• Added but not loaded because the Compose Agent service was not restarted

Qlik Compose does not dynamically load new JDBC drivers. The driver becomes available only after restarting the Compose Agent service.

See Prerequisites | Qlik Compose.

Environment

• Qlik Compose

Purpose

The purpose of this post is to help you install the database drivers necessary to allow your Qlik Data Gateway to communicate with your company's servers once you have completed the Qlik Data Gateway installation itself. 

Background

If you are anything like me, perhaps you panicked a bit at the thought of installing the Qlik Data Gateway in a Linux environment. I have a lot of experience with .EXE installations in Windows environments. You know "Next – Next – Next – Finish." But an .RPM file?  I had never even see that extension type before. If you were a Linux connoisseur beforehand, you probably guessed that my image for this post is an homage to the Fedora flavor of Linux. Otherwise you just thought it was an advertisement for the new "Raiders of the Lost Data" movie.

In any event, by now you have created your first Data Gateway, applied the registration key, completed the setup instructions and thankfully the command to check your Data Gateway service shows that it is running.

When you go back to the Data Gateway section of the Management Console and do a refresh your eyes fill you with happiness because your brand spanking new Data Movement Gateway shows "Connected.”

 A lesser person would go celebrate right now. But you've decided to try and connect to a source before doing your happy dance. So, you create a new Data Integration project to the destination of your choice. While you will ultimately have many different data sources, let's imagine that you decide to start with a "SQL Server (Log Based)" connection, as your first source test.

You input the server connection details, but your SQL Server doesn't use a standard port for security. Finally, you find information online that you should input your server IP followed by a "comma and the port #". As an example, if your servers IP is 39.30.3.1 and your security port is 12345 you would input "39.30.3.1,12345'. Next you input the user and password credentials. Your last step is to choose the database. Easy peezy, lemon squeezey. Right?

You press the "Load databases" button but suddenly a dialog comes up telling you that the Data Gateway can't connect because it can't find a SQL Server driver.

Driver Installation

Your heart starts beating quickly but naturally as a pro, you remain calm on the outside. Eventually you realize that whether on Windows or Linux, applications have always required drivers to communicate with servers. This is nothing new, we just got excited when we saw that connected message and thought we were done. Upon going back to the setup guide

[https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm]

you realize that there is in fact a link labeled "Setting up Data Gateway – Data Movement source connections."

So, you go ahead and click the link and it takes you to:

https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/DataIntegration/Landing/connecting-data-2.htm 

Wow, so many sources, and so many additional links to click to ensure the required drivers are in place for the sources your company will need. All the documentation is there, but I know firsthand that it can get a bit overwhelming, especially if Linux isn't your native language, which is the reason for this post.

Obviously every one of you reading this works in an environment that may require different data source connections than the others. Thus, there is no way for me to predict and help with your exact configuration. However, odds are strong that most of you likely require at least: SQL Server, Databricks, Snowflake, Postgres or MySQL, various combinations of them, or perhaps all of them.

As tedious, or imposing as it may be, I highly recommend you walk through the documentation for each data source you will need. But thanks to my buddy John Neal, I have attached a Linux shell script that can be executed to configure all 5 of those data sources for you. Given the many flairs and versions and configurations of Linux I can't ensure that it will work for everyone, but at least it is a start for those that may want to press an easy button, and those that like me may be somewhat or brand new to Linux.

If you choose to take advantage of it, understand that it is only being offered a shelp, and is not meant to replace the documentation. To utilize it you will need to do the following (Please note in my examples I have changed to the root user. If you are logged in as a normal user account, you may need to use SUDO "super user do"):

1. Copy the attached "repldrivers-el7.sh.txt" file your Linux home directory where you placed the gateway .RPM file.
2. Change the file name to simply be "repldrivers-el7.sh" so that it's clear that it is a shell script in case you or others see it in the future.
3. Issue the following command from your prompt: "chmod 775 repldrivers-el7.sh" so that the file has the appropriate security allowing it to be executed.
4. Issue the following command from your prompt: "./ repldrivers-el7.sh"  
5. Issue the following command from your prompt: "cd /etc"
6. Issue the following command from your prompt: "/etc/odbcinst.ini"    

If all went well with the installation your output should look like similar to the following image that was part of my file:

It's almost time to do our happy dance, but let's hold off until we test. In my starting example I asked you to assume we wanted to test against a "SQL Server (Log Based) connection." When we left off it was because we got an error message we had no driver while trying to load the list of databases. I will try that again.

 Oh no, the heart rate is going up again. 

We have successfully installed the Qlik Data Gateway. We have successfully installed the required drivers. Yet, we are getting this new error message. Let's focus on our breathing and try and digest the situation. What could cause our attempt to connect to our data source to timeout? I got it.

It's likely network security. We know what we want to talk to. We know the location. We know the credentials. But our networks aren't always wide open to do the talking. Resolving your connectivity/firewall issues may or not be with your abilities and if you are like me, you may need to seek the help of your IT/Networking team.

When I reached out to my friendly IT guru, here within Qlik, he was able to help me get everything in place so that my Linux server could speak with my database servers, including all of the needed ports.

Once they were completed I was able to test and sure enough my data connection succeeded.

Whether or not you do a happy dance, as I did, I hope that this post has helped you get to that sweet smell of success. After all, someone has to be known as the amazing person who got your Qlik Data Gateway going so that others in the Data Engineering team could create all of those lights out Qlik Cloud Data Integration projects that would be feeding data in near real time to all of those wonderul analytics use cases. Hopefully with the help of the documentation and this post, that person is you my friends. 

Challenge 

One of the things I've long admired about the Qlik Community is their willingness to help each other through this Community site. If you are a Linux guru and are so inclined I would love to see you share other versions of the shell script that I have started. Maybe your organization is using another flair/version of Linux and you needed to make a few tweaks to my file. Maybe your organization needed Oracle added and you can tweak my file. Whatever the reason, I sure hope you will give back to the community by sharing all of those tweaks here. Who knows, your help might help them be able to do their happy dance. And we all know the world is a better place when more people do their happy dance. 

Related Content 

Qlik Data Gateway - Data Movement prerequisites and Limitations - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-prerequisites.htm

Setting up the Data Movement gateway - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Gateways/dm-gateway-setting-up.htm

PS - I created both of the images here using a generative AI solution called MidJourney. I hope they've added to the fun of this post. 

Qlik Talend Studio job fails connecting to the Data Stewardship Application in Qlik Talend Cloud with the error below:

tDataStewardshipTaskInput_1 Unable to connect to Talend Data Stewardship.
java.io.IOException: Unable to connect to Talend Data Stewardship.

Caused by: java.net.UnknownHostException: No such host is known (tds.eu.cloud.talend.com)

Resolution

Cause

This error indicates that the Qlik Talend Studio job was unable to resolve the hostname to an IP address at that instant, in this case, Qlik Talend Cloud Data Stewardship.

Environment

• Qlik Talend Studio
• Qlik Talend Cloud

The Data Load Editor in Qlik Sense Enterprise on Windows 2025 experiences noticeable performance issues.

Resolution

Fix Version

Qlik Sense May 2025 SR 6 and higher releases.

Workaround

A workaround is available. It is viable as long as the Qlik SAP Connector is not in use.

1. In a Windows file browser, navigate to C:\Program Files\Common Files\Qlik\Custom Data\
2. Move the QvSapConnectorPackage directory to a different location

No service restart is required.

Internal Investigation ID(s) 

SUPPORT-6006

Environment

• Qlik Sense Enterprise on Windows

Beginning from Qlik Replicate version 2024.05, a new checkbox was added to Log Stream Staging tasks: Retrieve all source columns on UPDATE

The option is available in Task Settings (A) > Change Processing > Change Processing Tuning (B)

It is enabled (C) by default.  

When Retrieve all source columns on UPDATE is enabled, it will cause any table added to the task to issue an ALTER on the table to enable supplemental logging on all columns if the source database is Oracle.

Resolution

For high-transaction tables, enable Supplemental Logging on all columns during off-peak hours manually before adding them to the Qlik Replicate task.

Cause

In previous Qlik Replicate versions, supplemental logging was not required on all columns and was enabled only on Primary Key Columns. But with that new checkbox, it is required to be added to all columns.

When any new table is added to the Log Stream Staging task, Qlik Replicate issues an ALTER TABLE command to enable Supplemental Logging on all columns. This command can fail on high-transaction or busy tables in the source Oracle DB.

Environment

• Qlik Replicate

Method 1: From the Data Sources

1. Open the Qlik Analytics Service
2. Select  Catalog 
3. Pick your Space 
4. Click Space Details then
5. Select Data Files from the context menu
   
   
   
   
   
6. Locate the data you wish to delete
7. Click the ellipses to open the next menu
8. Click Delete
   
   
   
   
   
9. Alternatively, add /data at the end of the URL.

Method 2: From the Data Load Editor

1. Open the App with a connection to the data files you wish to edit
2. Go to Data Load Editor
3. On the Right Side of the Data Load Editor under add data section select your data space.
4. Click on the table icon under datafiles.
   
   
    
5. select the Delete option on the right side of each file that you want to delete.
   
   

Environment

• Qlik Sense Business 
• Qlik Cloud 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

When using Key Pair authentication and creating a new Snowflake connection, you might encounter the following error:

Illegal Argument

Resolution

The provided private key file (.p8) is not in the correct format, or the key file password is invalid. 

To get the actual error, install SnowSQL utility in the Linux machine where the Qlik Data Movement gateway is installed and try to connect to the same account:

snowsql -a <account> -u <username> --private-key-path <path to file/rsa_key.p8>

This will provide the exact error on why the connectivity is failing and assist in identifying which root cause applies.

Cause

Environment

• Qlik Talend Cloud

Starting from Qlik Replicate versions 2024.5 and 2024.11, Microsoft SQL Server 2012 and 2014 are no longer supported. Supported SQL Server versions include 2016, 2017, 2019, and 2022. For up-to-date information, see Support Source Endpoints for your respective version.

Attempting to connect to unsupported versions, both on-premise and cloud, can result in various errors.

Examples of reported Errors:

• Qlik Replicate 2024.5 accessing Microsoft Azure SQL Server 2014
  
  [SOURCE_CAPTURE  ]W:  Table 'dbo'.'tableName' has encrypted column(s), but the 'Capture data from Always Encrypted database' option is disabled. The table will be suspended  (sqlserver_endpoint_capture.c:157)
  
  
• Qlik Replicate 2024.11 accessing Microsoft SQL Server 2014
  
  [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: 42S02 NativeError: 208 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Invalid object name 'sys.column_encryption_keys'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4067)

Cause

The system view sys.column_encryption_keys is only available starting from SQL Server 2016. Attempting to query this view on earlier versions results in errors.

Reference: sys.column_encryption_keys (Microsoft Docs)

Resolution

Upgrade your SQL Server instances to a supported version (2016 or later) to ensure compatibility with Qlik Replicate 2024.5 and above.

Internal Investigation ID(s)

00375940, 00376089

Environment

• Qlik Replicate versions 2024.5, 2024.11, and higher
• Microsoft SQL Server 2014, 2012, and lower (unsupported)

Qlik Sense Connectors are missing from the Data source except few REST connectors.

Resolution

Solution 1

Repair Qlik Sense with the Qlik Sense Setup file (identical version).

Solution 2

1. Obtain a copy of the folder "C:\Program Files\Common Files\Qlik\Custom Data\" from a different, but working Qlik Sense Enterprise on a Windows environment (identical version). A test installation can be set up to obtain it.
2. Replace the files/folders with the copied version. This action needs to be carried out on all nodes if it is a multi-node environment.

Solution 3

Encryption keys:

• Verify if the Encryption keys are present in the User's directory.
• Check if you have multiple encryption keys stored in the User's directory.
• Delete and recreate the Encryption keys using Setting an encryption key

Encryption keys will be stored in either "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\" Or "C:\Users\{sense service user}\AppData\Roaming\Qlik\Keys\"

Cause

• The Connector folders or executables are corrupted or deleted.
• Connector folders or executables are being scanned and removed from their path. Therefore, it is mandatory to exclude Qlik folders if any scanning software is present on Qlik Sense Windows machines. For more information about exclusions, please refer to the document titled Qlik Sense Folder And Files To Exclude From Anti-Virus Scanning
• Encryption Keys are either deleted or corrupted.

Related Content

Qlik Sense ODBC Connectors are no longer available after an Upgrade - Error Message Unknown Connection Type. QvOdbcConnectorPackage.exe

An error occurred / Failed to load connection error message in Qlik Sense - Server Has No Internet

Environment

• Qlik Sense Enterprise on Windows 

After upgrading Qlik Talend Studio to patch R2025-08 or later, jobs using the tS3Connection or tS3List components fail with the error:

Exception in component tS3List_1
java.lang.IllegalStateException: Connection pool shut down

Resolution

An additional change with the new SDK version is how the AWS "region" is handled. In Qlik Talend Studio R2025-07 and earlier, the Region and Endpoint field is shown as a dropdown below.

Using the DEFAULT value works for most cases:

With the new SDK 2.x, the region field is less flexible. The region must explicitly be defined to work correctly. To resolve connectivity issues after upgrading, it is best to explicitly define the AWS region used under the new Region text field:

Additional Information

• For all AWS regions, see: AWS service endpoints 
• We recommend also reviewing all details for tS3Connection in our help documentation as per tS3Connection | help.qlik.com

Cause

With the release of R2025-08, Qlik Talend Studio migrated AWS component dependencies from Amazon Web Services SDK version 1.x to SDK version 2.x. This move was prompted by SDK 1.x having reached end of life as of December 31, 2025.

The Amazon DynamoDB, Amazon SQS, and Amazon S3 components were all updated. For the full release notes, see R2025-08 Talend Studio 8.0 - New Features.

Environment

• Qlik Talend Studio

When using IBM DB2 for iSeries as a source in Qlik Replicate, the task may report a warning if journal receiver numbers are not continuous.

A typical warning message looks like:

[SOURCE_CAPTURE  ]W:  Journal entry sequence '2026' was read from journal receiver 'APSUPDB.QSQJRN0118'. The previous entry was read from receiver 'APSUPDB.QSQJRN0116'. Check if a receiver has been detached.  (db2i_endpoint_capture.c:1836)

Resolution

Qlik Replicate reports this condition as a warning only. There is no impact on task execution or data integrity:

• The task continues to run normally
• No journal entries are lost
• No data inconsistency is introduced

This warning can be safely ignored unless accompanied by other errors or abnormal task behavior.

Cause

On the IBM DB2 for iSeries side, 'Check if a receiver has been detached' can occur if, for example, the process is holding or locking the journal. This temporarily prevents the system from creating or attaching the next journal receiver. In such cases, a receiver number may be allocated but never successfully created, resulting in a gap in the receiver numbering.

This behavior is normal on IBM i and does not indicate a defect. The system assigns journal receiver numbers, but sequential continuity is not guaranteed. IBM i only guarantees that receiver numbers increase monotonically, not that every number will exist.

Internal Investigation ID(s)

00420963, 00423959

Environment

• Qlik Replicate
• IBM DB2 for iSeries all versions