Sign inTry Free

Migrating to Workspaces

On this page

Overview

This page describes the general process for migrating to SingleStore Helios.

Migration is typically performed by following the documented steps to:

  • Prepare the target Helios deployment

  • Back up or export existing databases and objects

  • Restore or import the databases and objects into Helios

  • Validate the migrated environment

The exact steps may vary depending on your source environment and migration goals.

Migrate to Helios

The following table outlines the tasks that must be performed to migrate from a self-managed cluster or a non-SingleStore platform to Helios.

Step

Task

Self-Managed Cluster

Non-SingleStore Platform

1

Create an inventory of all objects, databases, tables, records, functions, stored procedures, views, aggregations, pipelines, database variables, etc. in your current production environment that need to be migrated.

✔

✔

2

Calculate the size required to store all the existing objects and data. Refer to the SingleStore Helios Sizing Guidelines for more information.

✔

✔

3

Create test plans for the following:

Connectivity

  • Upstream / downstream dataflows

  • Application

  • End-user

Functionality

  • Data accuracy

  • Custom objects

  • Jobs

  • Permissions

Performance

  • Ingest

  • Query

  • Skew

Rollback

✔

✔

4

Create the workspace in the Cloud Portal

Refer to Compute Workspaces for more information.

Ensure there are enough credits to create an appropriately sized workspace.

✔

✔

5

Generate SQL statements that can be executed to reproduce all the required objects. Use a third-party tool such as mysqldump.

Refer to Transition from MySQL to SingleStore Helios for more information.

✔

6

Create the objects in SingleStore Helios. Use the .sql dump file created in Step 5.

Copy and paste the contents of this file into the SingleStore Helios SQL Editor and run the SQL statements to recreate all objects in the workspace.

Note: While self-managed SingleStore Studio does not work with workspaces, you can use the Cloud Portal or third-party tools.

✔

7

Back up all of your databases. Use the  BACKUP DATABASE command to back up the data in production or take a backup from daily backups.

For non-SingleStore databases, refer to Migrating Data from Another Database for more information.

✔

✔

8

Restore the backed-up data to the workspace. Use the RESTORE DATABASE command to restore the database backups from the cloud object store into the workspace. 

Note: If you are moving from a SingleStore Self-Managed cluster to a SingleStore Helios workspace, first copy the backup to the proper cloud service and then restore.

For non-SingleStore databases, refer to Migrating Data from Another Database for more information.

✔

✔

9

Validate inventory and objects in SingleStore Helios. Confirm that everything exists in the workspace environment. This should include everything gathered in Step 1.

✔

✔

10

Add users, groups, roles, permissions, resource governor pools, database variables, and global system variables settings by raising a Support ticket.

✔

✔

11

Set the firewall rules for the new workspace. Refer to Firewall for more information.

✔

✔

12

Select the endpoint URL. The workspace will have a different endpoint URL than the prior cluster.

Only DML endpoints are currently offered. The DDL can be provided if some operations require it. Refer to SingleStore Helios Endpoints for more information.

✔

✔

13

Perform application-level validation testing. Connect your application and run benchmark queries.

✔

✔

Last modified:

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