Migrating to Workspaces
The table below outlines the tasks that need to be performed to migrate to Workspaces from an existing SingleStoreDB Cloud 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. in your current production environment that have to be migrated. | Yes | Yes | Yes |
2. | Calculate the size needed to store all the existing objects and data. Refer to SingleStoreDB Cloud Sizing Guidelines. | Yes | Yes | Yes |
3. | Create test plans for the following Connectivity
Functionality
Performance
Rollback | Yes | Yes | Yes |
4. | Create the Workspace in the 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. Use a third party tool such as Refer to Migrating Data with mysqldump. | No | No | Yes |
6. | Create the objects in SingleStoreDB Cloud. Use the Note: Studio does not work in Workspaces. You can use the Portal or third- party tools. | No | No | Yes |
7. | Backup all your databases. Use the BACKUP DATABASE command to backup the data in production (or take backup from daily backups). For non-SingleStore databases refer to Migrating Data from Another Database. | Yes | Yes | Yes |
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 SingleStoreDB Self-Managed to SingleStoreDB Cloud 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 SingleStoreDB Cloud. Double check to ensure that everything exists in the workspace environment. This should include everything gathered in Step 1. | 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. Refer to IP Address Allowlisting. | Yes | Yes | Yes |
12. | Select the endpoint URL. The workspace will have a different endpoint URL from the old cluster. Only DML endpoints are currently offered. The DDL can be provided if some operations require it. Refer to SingleStoreDB Cloud Endpoints. | Yes | Yes | Yes |
13. | Perform application level validation testing. Connect your application and run some benchmark queries. | Yes | Yes | Yes |