Connect with Tableau Prep

You can connect Tableau Prep to SingleStore using the SingleStore JDBC driver or the SingleStore ODBC driver to perform ETL operations.

To connect using the SingleStore ODBC driver, select the SingleStore option from the connection list. To connect using the SingleStore JDBC driver, select the SingleStoreDB JDBC by SingleStore option from the connection list instead.

The following certification matrix shows the latest version(s) tested for SingleStore and Tableau Prep:

Certification Matrix

Versions

Tableau Prep

2023.1.3, 2023.2.0+

SingleStore ODBC Driver

1.1.7+

SingleStore JDBC Driver

1.1.4+

Note

SingleStore recommends using the latest version of Tableau Prep with the latest version of the SingleStore JDBC driver or the SingleStore ODBC driver.

Prerequisites

  • Install the SingleStore JDBC driver or the SingleStore ODBC driver.

  • Create the DSN for source and destination databases.

  • Install Tableau Prep.

Note: When using a source or target other than SingleStore or MySQL, you will need to install the respective JDBC/ODBC driver for that platform.

Write to a Database

Although Tableau Prep can read data from a wide array of databases and cloud storage platforms, writing to external databases is available only for a limited set of datasources.

SingleStore enables writing back to a database via Tableau Prep, which allows the users to:

  • Connect to other data sources supported by Tableau Prep or connect to a SingleStore database.

  • Prepare data, including cleansing, imputation, and complex transformation.

  • Write changes back to the SingleStore database from the other sources, a different SingleStore database, or a different table in the same database.

  • Build Tableau dashboards using the data in SingleStore.

Configure Tableau Prep to Connect to SingleStore and Run a Transform

To connect to SingleStore from Tableau Prep:

  1. On Tableau Prep, on the left navigation pane, select Connections > Connect > SingleStore (or SingleStoreDB JDBC by SingleStore).

  2. Enter the connection details in the SingleStore dialog and connect to the datasource:

    • Server: IP address or hostname of the SingleStore cluster

    • Port: Default is 3306

    • Database (Optional): The SingleStore database name

    • Username and Password: The SingleStore database username and password

  3. Select the database and tables, and configure the required transformations.

  4. From the Save output to list, select Database table.

  5. Under Settings, either select an existing connection or create a new connection to the target database.

  6. From the Write Options list select one of the following options: Create table, Append to table, or Replace data.

  7. Select Run flow to run the transform.

Last modified: December 1, 2023

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK