Sign inTry Free

Load Data

On this page

SingleStore provides several options for loading data from various sources such as files, cloud repositories, external databases, and third-party ETL or CDC tools.

Data Loading Methods Available in SingleStore

  • SingleStore Flow: A GUI-based tool designed for database migration and change data capture (CDC) replication. It supports a wide range of enterprise databases.

  • SingleStore Pipelines: A built-in, real-time ingestion mechanism ideal for streaming and ETL scenarios, allowing continuous loading and transformation of data from file storages and streaming platforms.

  • LOAD DATA SQL Command: A SQL-based method for directly loading data from local or remote files into SingleStore tables.

All of these methods are accessible through the Helios Portal Load Data UI for easy setup and management.

Supported File Formats

SingleStore supports loading data from the following file formats:

Data Sources And the Corresponding Loading Methods in SingleStore

Note: Click a check mark (✓) to view the associated guide.

Data Sources

SingleStore Flow

Pipelines

LOAD DATA Command

Notes/Special Features

FIle Systems

Amazon Web Services (AWS) S3

✓

✓

Azure Blob Storage

✓

✓

Google Cloud Storage (GCS)

✓

✓

Hadoop Distributed File System (HDFS)

✓

Apache Iceberg

✓

Filesystem paths (local or network drives)

✓

✓

Stage

✓

✓

SingleStore managed storage

Streaming Systems

Kafka

✓

Database Sources

Oracle & Oracle RAC

✓

Microsoft SQL Server

✓

MySQL

✓

✓

When using pipelines; there is a cap of 16 pipelines for the MySQL source.

Also supports mysqlimport utility.

PostgreSQL

✓

Snowflake

✓

Data migration only.

Any JDBC-compliant database

✓

Limited to non-production preview, available for testing.

MongoDB®

✓

✓

When using pipelines; there is a cap of 16 pipelines for MongoDB® source.

Third-party Integration Tools

Apache Beam/Flink, AWS Glue, Azure Data Factory, dbt, Fivetran, Informatica, Qlik, StreamSets and similar platforms.

Supports JDBC, ODBC, REST APIs.

Third-party and Custom Connectors

In this section

Last modified: December 4, 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

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