Stay organized with collections Save and categorize content based on your preferences.
Before you choose to migrate your databases to Cloud SQL, make sure you consider known limitations for this migration scenario.
Note: You can also use Google Cloud Migration Center to discover possible limitations or gaps in feature support for your specific scenario. See Discover and import databases in the Migration Center documentation.Known limitations for using a MySQL database as a source include:
Migrating to MySQL 5.6 or MySQL 8.4 with a Percona XtraBackup physical backup file is not supported.
When you migrate across major MySQL versions (for example, from MySQL 8.0 to MySQL 8.4) you need to address possible incompatibilities to ensure a smooth migration without data consistency issues.
When you prepare for a cross-version migration, review the features supported by Cloud SQL for MySQL as well as the release notes for your target major version to determine what incompatibilities you need to address.
Don't perform any data definition language (DDL) changes, such as modifying table definitions, during the full data dump phase. DDL changes performed before the migration job moves to the CDC phase can cause your migration job to fail. For more information, see Diagnose issues: Table definition has changed error.
If the source is Amazon RDS MySQL, Amazon Aurora MySQL, or a source that doesn't grant SUPERUSER privileges, then additional steps are required for successful migration, including a brief write downtime on the source. For more information, see Amazon RDS-specific and Amazon Aurora-specific sections.
Database Migration Service can't migrate data from an Amazon Aurora read replica instance of a MySQL database cluster because binary log files can't be retrieved from the instance. For more information, see Amazon Aurora-specific section.
The MySQL system database isn't migrated as part of the server migration, which means information about user roles isn't included.
You can't select specific database objects (such as databases, tables, or schemas) when you migrate by using Database Migration Service. All tables from all databases and schemas are migrated, excluding the following system schemas: mysql, performance_schema, information_schema and sys. Before you begin the migration, make sure that your source database doesn't contain objects that reference tables in these schemas. Otherwise, your migration can fail with the ERROR 1109 (42S02): Unknown table in <schema name here> message. See Configure your source database and Diagnose issues.
If encrypted databases require customer-managed encryption keys to decrypt the information in the databases, and if Database Migration Service doesn't have access to the keys, then the databases can't be migrated.
Database Migration Service supports migrating data from encrypted Amazon Aurora or Amazon RDS databases because these databases handle decryption transparently in their services. For more information, see Encrypting Amazon Aurora resources and Encrypting Amazon RDS resources.
During migration, the destination Cloud SQL database is in read-only mode, to prevent modification of the database which might break the migration process or data integrity. After the destination is promoted, it becomes writable.
Presently, Database Migration Service isn't compatible with MariaDB.
You must set the binary log format to ROW. Configuring the binary log to any other format, such as STATEMENT or MIXED, might cause the replication to fail. For example, using the LOAD DATA IN FILE statement.
Learn more about this limitation for the STATEMENT or MIXED formats.
If you create a continuous migration job using your own dump file, then don't use the mysqldump utility from MySQL version 5.7.36. For more information, see bug #105761 in the MySQL documentation.
InnoDB is the only supported storage engine for Cloud SQL. Migrating with MyISAM might cause data inconsistency and requires data validation. For help with converting tables from MyISAM to InnoDB, see the MySQL documentation.
Private Service Connect interfaces connectivity method is only supported for migrating to existing destination instances. If you want to use private IP connectivity and migrate to a new destination instance, use VPC peering.
Data dump parallelism lets you migrate from MySQL databases using a high-performance dump mechanism, significantly improving the migration speed. When using data dump parallelism, consider the following:
Data dump parallelism is currently available only when migrating to MySQL versions 5.7 or 8.
At the beginning of the data dump, Database Migration Service briefly locks your source database making it temporarily unavailable for writes. The lock duration depends on the number of tables in the source database:
Number of tables Approximate lock time 100 1 second 10K 9 seconds 50K 49 secondsIf you encounter issues due to extra data in your existing destination instance, clear the databases in your destination instance and re-try the migration job. See Clear extra data from your existing destination instance.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-14 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["Database migrations to Cloud SQL from MySQL sources have limitations, including not supporting migrations to MySQL 5.6 or 8.4 with a Percona XtraBackup physical backup file."],["Cross-version MySQL migrations, such as from MySQL 8.0 to 8.4, require addressing potential incompatibilities to prevent data consistency issues, referencing the documentation for supported features and release notes for the target version."],["During the full data dump phase, no Data Definition Language (DDL) changes should be performed, as this can cause migration job failures."],["Database Migration Service cannot migrate specific database objects, and instead, migrates all tables from all databases and schemas, excluding certain system schemas."],["Migration to an existing Cloud SQL instance is only supported if the instance is empty or contains system configuration data, and only one migration job can be configured per destination instance."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4