Tableau #

  • Tableau data connector: The recommended connection method uses a Tableau data connector file paired with the Starburst JDBC driver

  • ODBC connection: Starburst also supports connecting to SEP clusters with the Starburst ODBC driver.

  • Legacy JDBC connection: For sites using a plain JDBC connection using the legacy “Other Databases (JDBC)” method, Starburst strongly recommends migrating to the Tableau data connector method, but Starburst also supports continued use of the legacy method.

Before you begin #

  1. Determine the connection information for your SEP cluster, including its URL and login credentials.

  2. Instructions to connect Tableau products to SEP clusters vary slightly, depending on the SEP version. See Determine cluster version.

Tableau data connector with JDBC driver #

You can connect recent releases of Tableau Desktop to recent SEP clusters with a combination of a Tableau data connector file and JDBC driver. This method requires Tableau Desktop 2021.1 or later, and SEP 354-e or later.

Note that a Tableau data connector is not the same as an SEP Connector. The Tableau data connector is a bridge between Tableau and the standard SEP JDBC driver that together enable read-only access between Tableau and one or more SEP clusters.

For Tableau Desktop 2021.1 and 2021.2, the Tableau data connector for Starburst does not appear in the integrated Extension Gallery within Tableau. Prepare your Tableau installation as described here before attempting to connect to a SEP cluster.

Follow these steps to configure the Tableau data connector for Starburst:

  1. Download the Tableau data connector file with .taco extension from the Starburst Enterprise page of Tableau’s web-based Extension Gallery, using the Download button on the upper right of the page. This requires logging into Tableau’s site with a free login name.

  2. Move the data connector file to:

    C:\Users\username\Documents\My Tableau Repository\Connectors
    /Users/username/Documents/My Tableau Repository/Connectors
  3. Download the latest Starburst JDBC driver.

  4. Place the JDBC driver file in the Tableau drivers directory:

    C:\Program Files\Tableau\Drivers

    Do not store more than one Starburst JDBC driver in this directory. Delete any older drivers when you update to a newer version. Connections to all SEP-connected data sources are made through the Starburst JDBC driver.

  5. Start Tableau Desktop. In the left column, under To a Server, click More.

  6. In the list of server types, select Starburst Enterprise by Starburst. This opens a connection dialog:

      Tableau Connector login dialog

  7. Fill in the connection dialog with the following parameters:

    Field Value
    Server Hostname or IP address of your SEP cluster.
    Port Port used by your cluster.
    Authentication Use the drop-down list to select Username for a cluster with no authentication or Username and Password for a cluster with TLS enabled and a password-based authentication method such as LDAP.
    Username Your SEP username.
    Password (If selected) the password for the specified Username.
    Require SSL Select this check box if your cluster has TLS enabled. When selected, the following field appears.
    SSL Verification Select an entry in the drop-down list to specify how rigorously the server’s certificate is to be validated.

    The values for SSL Verification have the following meanings:

    Confirm that the certificate's validity is chained all the way back to a root Certificate Authority (CA).
    Confirm that the certificate is valid as far back as the included intermediate CA.
    Confirm that the server's certificate matches the DNS name and private key of the server.
  8. When the connection is made, the Connections panel shows a list of the catalogs configured on your cluster.

      Tableau Connector list of catalogs

  9. Select a catalog and subsequent schema from that catalog, to see the available tables.

      Tableau list of tables

If your cluster and catalogs support it, you can use the Initial SQL panel to specify one or more SQL statements to run on connection to the cluster. See the Learn More link in Tableau for information on the limitations of this feature.

Customized JDBC connections #

If you need to set additional connection properties that are not included in Tableau’s connection dialog, customize the connection using a properties file.

For more information, see Customize JDBC Connections Using a Properties File in the Tableau Community and the list of available parameters for the JDBC driver.

Starburst advantage #

Remember that Starburst Enterprise is not a database, it’s a SQL query engine that can connect to multiple data sources at the same time. Each SEP cluster can query multiple catalogs in a wide range of different data sources.

Although Tableau is typically configured for one specific catalog and schema, it is possible to query more than one data source with a single Tableau connection.

To query multiple catalogs, select New Custom SQL in Tableau, and then reference the fully qualified name of any table in the cluster using the full catalog.schema.table syntax.

The follow example query accesses the three catalogs s3, mysql, and bigquery:

Tableau, let SEP do the JOINs

This approach is faster because all data access is managed by SEP, and is executed on the cluster. Tableau can also pull data from multiple catalogs, but Tableau pulls all data into the local machine and performs its joins and other operations as local analysis.

ODBC driver connection #

Contact Starburst Support to obtain access to the Starburst ODBC driver. This driver is supported for clusters running any supported SEP release. The Presto ODBC driver provided by Tableau is not supported.

Open Tableau and begin the ODBC configuration. On Tableau’s startup page, select Other Databases (ODBC), and configure as follows:

  • Driver: Starburst Presto ODBC Driver
  • Username: <username>
  • String Extras: Driver=Starburst Presto ODBC Driver;Catalog=<catalog>;Host=<host>;Port=<portDriver>;

The String Extras field supports any of the ODBC connection properties from the Starburst ODBC driver.

Select Sign In to establish the connection. If you are prompted for a password, the server has authentication enabled.

The Tableau ODBC documentation contains further information.

Legacy JDBC driver connection #

Tableau provides a generic connection method titled Other Databases (JDBC). Although Starburst strongly recommends using a Tableau data connector, this generic JDBC connection method is still available. Follow these steps:

  1. Download the Starburst JDBC driver according to your SEP version.

  2. Place the JDBC driver file in the Tableau drivers directory:

    C:\Program Files\Tableau\Drivers

    Do not store more than one JDBC driver in this directory. Delete any older drivers when you update to a newer version. Connections to all SEP-connected data sources are made through the Starburst JDBC driver.

  3. Start Tableau Desktop and select Connect to a server using the Other Databases (JDBC) connector in Tableau.

  4. Fill in the connection dialog as shown in the following table. For the URL field, if you downloaded the Trino JDBC driver file to connect to newer SEP versions, use a JDBC connection string in this format:


    If you downloaded the PrestoSQL JDBC driver file to connect to older SEP versions, use a JDBC connection string in this format:


    For either driver, the JDBC connection string must include the initial catalog to connect to. Once connected, you can select schemas and tables within that catalog, or select a different catalog.

    If your cluster has TLS enabled, append the property ?SSL=true to the connection string.

    Field Value
    URL Full JDBC connection string for your cluster. Must include a catalog name.
    Dialect Must be ‘SQL92’
    Username Your SEP username
    Password Your SEP password
    Properties File Specify or browse to the path of a JDBC properties file containing further specifications for this connection. See Customized JDBC Connections.

      Tableau Other Databases login dialog