Watch the webinar
Migrations are excruciating and are to be avoided whenever possible. Unfortunately, the advantages of modern database technology are forcing a lot of organizations running on traditional database solutions to consider migrations. In 2020 a lot of companies are migrating for the same reasons:
Manually sharding MySQL can be a nightmare and CockroachDB solves a lot of problems that manual sharding can create related to consistency, resiliency, locality, and scale. The result is that many companies have chosen to migrate from MySQL to CockroachDB and other cloud-native database products that automate sharding at the database layer.
Many of the complexities that make migrations painful can be addressed during the research stage, and will help an organization set itself up for a successful migration. Here are a few of the most common challenges that should be addressed ahead of time:
This webinar will detail the nuance of each step required for migrating from MySQL to CockroachDB. After you’ve watched the webinar you can consult this docs page which offers commands to be copied and pasted.
Dump the MySQL Database: There is an option to dump an entire database or to dump one table at a time.
Host the Files where the cluster can access them: CockroachDB strongly recommends using cloud storage such as Amazon S3 or Google Cloud to host the data files for import.
Import the MySQL dump file: There are three options here depending on whether or not you want to import the entire database or just one table at a time:
If you have questions following the webinar you can join the conversation in the CockroachDB Community Slack channel to discuss your migration with CockroachDB users and engineers.