Sign inTry Free

Configure Destination Database

On this page

You can configure SingleStore databases as a destination. To configure the destination database, navigate to Dashboard > Destination, and then select the gear icon.

  1. In the Destination Database dialog, select SingleStore from the Destination Database list.

  2. In the SingleStore tab, enter the following configuration details:

    1. Host Name: Enter the IP address or hostname of the database server.

    2. Port: Enter the port number on which the database server is listening (default port for SingleStore is 3306).

    3. Database Name: Enter the name of your database.

    4. User ID: Enter a valid SingleStore user ID to be used with Ingest.

    5. Password: Enter the password and confirm it by re-entering it in the Confirm Password field.

      Note: Passwords are encrypted within Ingest.

    6. JDBC Options (Optional): JDBC options are optional and can be used to extend the JDBC URL for accessing the database.

  3. Select the Advanced Options tab. Enter the following configuration details:

    1. Max Updates (Default maximum update is 4)

    2. Load Threads

    3. Add Database Prefix

    4. Truncate table instead of drop

    5. Database name and optional table name pattern

    6. Ignore database name in schema

    7. Database for staging tables

    8. Retain staging tables

    Refer to Appendix for more information.

  4. Select Apply to confirm and save the details.

  5. Select Test to verify the connectivity.

Multi-Tenant Support (For MySQL, PostgreSQL, SQL Server, and Oracle sources)

The Database name and optional table name pattern field in the Advanced Options controls how source tables are written to the destination, along with support for multi-tenancy.

  • Enter a single database name (e.g. main_db) to direct all source tables to that database.

  • For multi-tenancy, enter a database name followed by the destination table name in the following format:

    <dbname>.<destination_table_name>

    where destination_table_name can include the following symbols along with underscores (no other special characters supported) :

    • %d: Source database name

    • %s: Source schema name

    • %t: Source table name

    Note

    %d is not supported for MySQL and Oracle sources. Use %s to refer to the database name for these sources.

Examples (PostgreSQL, SQL Server)

  1. Source database: tenant1_db

    Source table: customers

    Database name and optional table name pattern set to: main_db.%d_%t

    • Destination database name: main_db 

    • Destination table: tenant1_db_customers

  2. Source database: server_db

    Source schema: org1

    Source table: supplier

    Database name and optional table name pattern set to: dest_db.%s_%t

    • Destination database name will be: dest_db 

    • Destination table will be: org1_supplier

Examples (MySQL, Oracle)

  1. Source database: org1_db

    Source table: customers

    Database name and optional table name pattern set to: dest_db.%s_%t

    • Destination database: dest_db

    • Destination table: org1_db_customers

  2. Source database: vdb

    Source table: customer

    Database name and optional table name pattern set to: main_%s.primary_%t

    • Destination database: main_vdb

    • Destination table: primary_customer

Last modified: February 3, 2026

Was this article helpful?

On this page

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

Try Out This Notebook to See What’s Possible in SingleStore

Get access to other groundbreaking datasets and engage with our community for expert advice.

Sign UpLog In