DBeaver #

Requirements #

Users of Starburst Galaxy and Starburst Enterprise 354-e or newer, must use DBeaver 21.0 or newer.

Connection #

Use the following steps to prepare DBeaver to access your cluster:

  1. Get the necessary connection information for your cluster.

  2. Start DBeaver.

  3. Right-click in the Database Navigator panel and select Create > connection.

  4. In the Connect to a database dialog, select All in the left column.

  5. Enter trino in the search field. Select the Trino logo and click Next.

    (If you are connecting to a SEP cluster with release 350-e or older, instead enter prestos. Select the PrestoSQL icon, then Next.)

      DBeaver select driver dialog

  6. In the Main tab of the Connect to a database dialog:

    a. The initial configuration is set for a server running at localhost:8080 with no security settings.

      DBeaver connect to database dialog

    b. The JDBC URL field is constructed automatically. Do not write in this field.

    c. In the Host field, enter the FQDN or IP address of your cluster’s coordinator (or its load balancer or proxy). Do not include the protocol at the start of the string or a database name on the end.

    d. In the Port field, enter the port on which your cluster is listening for connections. Use 443 for Starburst Galaxy. For SEP clusters, you must fill in a port number, which your network administrator can provide, or enter one of the default ports.

    e. For your initial connection test, do not use the Database/Schema field. You can come back later to narrow this connection entry to open a particular database among those managed by your cluster.

    f. In the Username field, for a cluster without security, enter any name. For a TLS-enabled cluster, enter a valid username for the authentication type in use on your cluster, such as LDAP. Starburst Galaxy provides the correct value in the User field in the connection info dialog.

    g. In the Password field, leave blank for a cluster without security. For a TLS-enabled cluster, enter the valid password for the username entered.

  7. For a TLS-enabled cluster, continue into the Driver properties tab.

    a. In the User Properties grid, right-click and select Add new property.

    b. Add a property named SSL with value true.

      DBeaver driver properties

  8. Click the Test Connection button in the bottom left of the dialog.

    If the JDBC driver is not already installed, this opens the Download driver files dialog showing the latest available JDBC driver. Select that line and click Download.

  9. The connection test continues. Look for a success dialog like the following:

      DBeaver connection test

    If you instead receive an error dialog, go back through your settings or try different port numbers. Make sure you are using the exact connection information provided by your network administrator.

  10. After a successful test, click Finish. This places an entry for this connection in the Database Navigator panel. Open this entry to connect to the cluster and see a list of its catalogs.


Starburst Galaxy uses globally trusted certificates, so the host and port provided by the connection dialog are sufficient.

Any SEP cluster that requires authentication is also required to use TLS/HTTPS. If you’re using globally trusted certificate best practices, use the cluster’s HTTPS URL in the connection string as shown in the steps above.

If you’re not using a globally trusted certificate, you may have to configure the trust store on your client machine. Consult your site’s network administrators for guidance.

To use TLS, specify the JDBC parameter setting SSL=true as shown in the steps above. As an alternative, you can make the same setting appended to the JDBC connection string in the form ?SSL=true.

Querying #

Click on the defined connection in the Database Navigator to connect. The initial connection downloads all metadata about catalogs, schema, tables, columns and more. You can browse the information as it loads.

DBeaver database navigator

Open SQL Editor > Open SQL script (or press F3) to write and execute your queries and inspect the returned results.

DBeaver SQL editor

Configure for OAuth 2.0 #

The default DBeaver configuration works well for password-based authentication types, such as LDAP. But when using an OAuth 2.0 compliant authentication type such as Okta or Ping Identity, every new connection to an SEP cluster might result in another browser pop-up confirming that you are authenticated or even requesting re-authentication.

To avoid these pop-ups, configure DBeaver with the following additional settings in DBeaver Preferences.

In Preferences > Editors > SQL Editor, in the Connections section, set Open separate connection for each editor to NEVER. Clear both checkboxes.

DBeaver OAuth 2.0 Setting

In Preferences > Connections > Metadata, set Open separate connection for metadata read to NEVER.

DBeaver OAuth 2.0 Setting