Ready to get started?

Learn more or sign up for a free trial:

CData Sync

Automated Continuous SingleStore Replication to MongoDB



Use CData Sync for automated, continuous, customizable SingleStore replication to MongoDB.

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live SingleStore data into your MongoDB instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure MongoDB as a Replication Destination

Using CData Sync, you can replicate SingleStore data to MongoDB. To add a replication destination, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select MongoDB as a destination.
  3. Enter the necessary connection properties. To connect to MongoDB, set the following:
    • Server: Set this to the name or address of the server where your MongoDB instance is running. You can specify the port here or in Port.
    • Database: Set this to the database you want to read from and write to.

    Connecting to CosmosDB with the MongoDB API

    To obtain the connection string needed to connect to a Cosmos DB account using the MongoDB API, log in to the Azure Portal, select Azure Cosmos DB, and select your account. In the Settings section, click Connection String and set the following values.

    • Server: Set this to the Host value, the FQDN of the server provisioned for your account. You can also specify the port here or in Port.
    • Port: Set this to the port.
    • Database: Set this to the database you want to read from and write to.
    • User: Set this to the database user.
    • Password: Set this to the user's password.

  4. Click Test Connection to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure the SingleStore Connection

You can configure a connection to SingleStore from the Connections tab. To add a connection to your SingleStore account, navigate to the Connections tab.

  1. Click Add Connection.
  2. Select a source (SingleStore).
  3. Configure the connection properties.

    The following connection properties are required in order to connect to data.

    • Server: The host name or IP of the server hosting the SingleStore database.
    • Port: The port of the server hosting the SingleStore database.
    • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

    Connect Using Standard Authentication

    To authenticate using standard authentication, set the following:

    • User: The user which will be used to authenticate with the SingleStore server.
    • Password: The password which will be used to authenticate with the SingleStore server.

    Connect Using Integrated Security

    As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

    Connect Using SSL Authentication

    You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

    • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
    • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSLClientCertType: The certificate type of the client store.
    • SSLServerCert: The certificate to be accepted from the server.

    Connect Using SSH Authentication

    Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

    • SSHClientCert: Set this to the name of the certificate store for the client certificate.
    • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
    • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
    • SSHClientCertType: The certificate type of the client store.
    • SSHPassword: The password that you use to authenticate with the SSH server.
    • SSHPort: The port used for SSH operations.
    • SSHServer: The SSH authentication server you are trying to authenticate against.
    • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
    • SSHUser: Set this to the username that you use to authenticate with the SSH server.
  4. Click Connect to ensure that the connection is configured properly.
  5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your SingleStore data to MongoDB.