Migrating to Workspaces
The table below outlines the tasks that need to be performed to migrate to Workspaces from an existing SingleStore Helios cluster, self-managed cluster, or a non-SingleStore platform.
Step |
Task |
Existing Cloud Cluster |
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. |
Yes |
Yes |
Yes |
2. |
Calculate the size needed to store all the existing objects and data. |
Yes |
Yes |
Yes |
3. |
Create test plans for the following Connectivity
Functionality
Performance
Rollback |
Yes |
Yes |
Yes |
4. |
Create the Workspace in the Cloud Portal Refer to Creating and Using Workspaces. Ensure there are enough credits to create the appropriate sized Workspace. |
Yes |
Yes |
Yes |
5. |
Generate SQL statements that can be executed to reproduce all the required objects. Refer to Migrating Data with mysqldump. |
No |
No |
Yes |
6. |
Create the objects in SingleStore Helios. Note: Studio does not work in Workspaces. |
No |
No |
Yes |
7. |
Backup all your databases. For non-SingleStore databases refer to Migrating Data from Another Database. |
Yes |
Yes |
Yes |
8. |
Restore the backed up data to the Workspace. Note: If you are moving from SingleStore Self-Managed to SingleStore Helios Workspaces, first copy the backup to the proper cloud service, then restore. For non-SingleStore databases refer to Migrating Data from Another Database. |
Yes |
Yes |
Yes |
9. |
Validate inventory and objects in SingleStore Helios. |
Yes |
Yes |
Yes |
10. |
Add users, groups, roles, permissions, resource governor pools, database variables, and global system variables settings by raising a Support ticket. |
Yes |
Yes |
Yes |
11. |
Set the firewall rules for the new workspace. |
Yes |
Yes |
Yes |
12. |
Select the endpoint URL. |
Yes |
Yes |
Yes |
13. |
Perform application level validation testing. |
Yes |
Yes |
Yes |
Last modified: July 4, 2023