Sign inTry Free

Warning

SingleStore 9.0 gives you the opportunity to preview, evaluate, and provide feedback on new and upcoming features prior to their general availability. In the interim, SingleStore 8.9 is recommended for production workloads, which can later be upgraded to SingleStore 9.0.

Dashboard

On this page

The Dashboard provides a central screen to monitor the overall status of the Ingest instance.

  • Dashboard provides quick access to configure Ingest, including the following:

    • Source Database

    • Destination Database

    • Tables

    • Schedule Tasks

  • The Checklist gives the summary of the steps that are needed to complete to start an Ingest job.

  • The graph summary displays the number of records transferred.

    • When Hourly is selected, you can view transfer statistics for the past 24 hours.

    • When Daily is selected, the monthly statistics are shown.

    • The bar graph illustrates the process status:

      • Initial Extract is represented by blue.

      • Inserts are represented by green.

      • Updates are represented by yellow.

      • Deletes are represented by red.

    • Hovering over the bar graph shows the exact number of records transferred.

  • You can view the log for Source and Destination database at the bottom.

Source Database

You can configure the following databases as a source: Oracle, Microsoft SQL Server, MySQL, PostgreSQL, and Snowflake.

To configure the source database, navigate to Dashboard > Source, and then select the gear icon.

Destination Database

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. Schema for all tables

    6. Ignore database name in schema

    7. Schema 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

The Schema for all tables 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 below symbols, along with other characters, if desired:

    • %d: Source database name

    • %s: Source schema name

    • %t: Source table name

Examples

  1. A table called customer from source database tenant1_db is transferred to SingleStore.

    Schema for all tables set to: main_db.%d_%t

    Destination database name will be: main_db 

    Destination table will be: tenant1_db_customer

  2. A table called supplier from database server_db, schema org_1 is transferred to SingleStore.

    Schema for all tables set to: dest_db.%s_%t

    Destination database name will be: dest_db 

    Destination table will be: org_1_supplier

Last modified: January 29, 2025

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