Important

Helios features are now enabled during weekly update windows and are no longer directly tied to SingleStore engine releases. Refer to the release notes to view the latest features available in your Helios cluster.

Migrating to Clusters

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 cluster in the Cloud Portal

Refer to Compute Clusters for more information.

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

✔

✔

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

Note: While self-managed SingleStore Studio does not work with clusters, 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 cluster. Use the RESTORE DATABASE command to restore the database backups from the cloud object store into the cluster. 

Note: If you are moving from a SingleStore Self-Managed cluster to a SingleStore Helios cluster, 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 cluster 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 cluster. Refer to Firewall for more information.

✔

✔

12

Select the endpoint URL. The cluster 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?