Database Migration Service 是一项可帮助您更轻松地将数据迁移到 Google Cloud的服务。Database Migration Service 可帮助您将 MySQL 工作负载直接原样迁移到 Cloud SQL。
支持哪些来源？
Amazon RDS 5.6、5.7、8.0
自行管理的 MySQL（在本地或由您完全控制的任何云端虚拟机上）5.5、5.6、5.7、8.0
Cloud SQL for MySQL 5.6、5.7、8.0、8.4
Amazon Aurora 5.6、5.7、8.0
Microsoft Azure Database for MySQL 5.7、8.0
对于 MySQL 8.0 源，Database Migration Service 还支持以下次要版本：8.0.18、8.0.26、8.0.27、8.0.28、8.0.30、8.0.31、8.0.32、8.0.33、8.0.34、8.0.35、8.0.36、8.0.37、8.0.39、8.0.40、8.0.41、8.0.42。
支持哪些目标位置？
Cloud SQL for MySQL 5.6 和 5.7
Cloud SQL for MySQL 8.0，包括以下次要版本：8.0.18、8.0.26、8.0.27、8.0.28、8.0.30、8.0.31、8.0.32、8.0.33、8.0.34、8.0.35、8.0.36、8.0.37、8.0.39、8.0.40、8.0.41、8.0.42。
Cloud SQL for MySQL 8.4，但存在一些限制。例如，MySQL 8.4 目标位置不支持使用物理备份文件的迁移。如需了解详情，请参阅已知限制。
是否支持跨版本？
Database Migration Service 支持跨任何主要版本进行 MySQL 到 Cloud SQL 迁移，前提是目标数据库的版本与源数据库相同或高于源数据库一个版本。例如，将 MySQL 5.6 源数据库迁移到 Cloud SQL for MySQL 5.6 或 5.7 目标位置。
哪些数据、架构和元数据组件会被迁移？
Database Migration Service 会将架构、数据和元数据从源迁移到目标。在数据库迁移过程中，系统会迁移以下所有数据、架构和元数据组件：
数据迁移
所有数据库/架构中的所有表。
架构迁移
命名
主键
数据类型
序数位置
默认值
是否可为 NULL
自动递增属性
二级索引
元数据迁移
存储过程
函数
触发器
查看次数
外键约束条件
持续迁移期间复制哪些更改？
在持续迁移期间，DML 和 DDL 更改（即对上述所有数据、架构和元数据的更改）会更新。
哪些内容不会迁移？
迁移 MySQL 数据库时，系统不会迁移包含用户和权限相关信息的 MySQL 系统数据库。这意味着，必须直接在目标 Cloud SQL 实例中管理用户账号/登录信息。
如需向 Cloud SQL 目标实例添加用户，请前往该实例，然后从用户标签页添加用户，或通过 MySQL 客户端添加用户。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-05。"],[[["\u003cp\u003eDatabase Migration Service simplifies the process of migrating MySQL workloads to Google Cloud's Cloud SQL.\u003c/p\u003e\n"],["\u003cp\u003eThe service supports a variety of MySQL sources, including Amazon RDS, self-managed MySQL, Cloud SQL for MySQL, Amazon Aurora, and Microsoft Azure Database for MySQL, with specific version compatibility.\u003c/p\u003e\n"],["\u003cp\u003eDestinations for migration are primarily Cloud SQL for MySQL, including versions 5.6, 5.7, 8.0, and 8.4 with certain limitations on 8.4, and cross-version migrations are supported if the destination is the same or one major version higher than the source.\u003c/p\u003e\n"],["\u003cp\u003eDuring the migration, the service transfers all data, schema components like primary keys, data types, and metadata components, like stored procedures and triggers, and can replicate both DDL and DML changes.\u003c/p\u003e\n"],["\u003cp\u003eVarious networking methods are supported for establishing connectivity between the source and destination, including IP allowlisting, reverse SSH tunnels, VPC peering, VPN, and Cloud Interconnect, each with different pros and cons depending on the user requirements.\u003c/p\u003e\n"]]],[],null,["# Database Migration Service for MySQL FAQ\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nMySQL \\| [PostgreSQL](/database-migration/docs/postgres/faq \"View this page for the PostgreSQL version of Database Migration Service.\") \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/faq \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n- [What is Database Migration Service?](#whatisdms)\n- [Which sources are supported?](#sources)\n- [Which destinations are supported?](#destinations)\n- [Is there cross-version support?](#crossversion)\n- [Which data, schema, and metadata components are migrated?](#migrated)\n- [Which changes are replicated during continuous migration?](#replicated)\n- [What isn't migrated?](#notmigrated)\n- [Which networking methods are used?](#networking)\n- [What are the known limitations?](#limitations)\n\n\u003cbr /\u003e\n\nWhat is Database Migration Service?\n: Database Migration Service is a service that makes it easier for you to migrate your data to Google Cloud. Database Migration Service helps you lift and shift your MySQL workloads into Cloud SQL.\n\nWhich sources are supported?\n:\n\n\n - Amazon RDS 5.6, 5.7, 8.0\n - Self-managed MySQL (on premises or on any cloud VM that you fully control) 5.5, 5.6, 5.7, 8.0\n - Cloud SQL for MySQL 5.6, 5.7, 8.0, 8.4\n - Amazon Aurora 5.6, 5.7, 8.0\n - Microsoft Azure Database for MySQL 5.7, 8.0\n\n\n For MySQL 8.0 sources, Database Migration Service also supports the following minor versions:\n 8.0.18, 8.0.26, 8.0.27, 8.0.28, 8.0.30, 8.0.31, 8.0.32, 8.0.33, 8.0.34, 8.0.35, 8.0.36, 8.0.37,\n 8.0.39, 8.0.40, 8.0.41, 8.0.42.\n\n\nWhich destinations are supported?\n:\n\n\n - Cloud SQL for MySQL 5.6 and 5.7\n - Cloud SQL for MySQL 8.0 including the following minor versions: 8.0.18, 8.0.26, 8.0.27, 8.0.28, 8.0.30, 8.0.31, 8.0.32, 8.0.33, 8.0.34, 8.0.35, 8.0.36, 8.0.37, 8.0.39, 8.0.40, 8.0.41, 8.0.42.\n - Cloud SQL for MySQL 8.4 with certain limitations. For example, migrations that use physical backup files are not supported for MySQL 8.4 destinations. For more information, see [Known limitations](/database-migration/docs/mysql/known-limitations).\n\n\nIs there cross-version support?\n:\n\n Database Migration Service supports MySQL-to-Cloud SQL migrations across any major version, where the destination is the same version or one version higher than the source database. For example, migrate a MySQL 5.6 source database to either a Cloud SQL for MySQL 5.6 or 5.7 destination.\n\nWhich data, schema, and metadata components are migrated?\n\n: Database Migration Service migrates schema, data, and metadata from the source to the destination. All of the following data, schema, and metadata components are migrated as part of the database migration: \u003cbr /\u003e\n\n Data Migration\n\n - All tables from all databases/schemas.\n\n Schema Migration\n\n \u003c!-- --\u003e\n\n - Naming\n - Primary key\n - Data type\n - Ordinal position\n - Default value\n - Nullability\n - Auto-increment attributes\n - Secondary indexes\n\n Metadata Migration\n\n \u003c!-- --\u003e\n\n - Stored Procedures\n - Functions\n - Triggers\n - Views\n - Foreign key constraints\n\nWhich changes are replicated during continuous migration?\n:\n\n DML and DDL changes (that is, changes to all data, schema, and metadata listed above) are updated during\n continuous migrations.\n\nWhat isn't migrated?\n\n: When migrating a MySQL database, the MySQL system databases which contain information about users\n and privileges aren't migrated. This means that user account/login information must be managed in\n the destination Cloud SQL instance directly.\n\n To add users to the Cloud SQL destination instance, navigate to the instance and add users\n from the **Users** tab, or add them from the MySQL client.\n\n [Learn more about creating\n and managing MySQL users](https://cloud.google.com/sql/docs/mysql/create-manage-users).\n\nWhich networking methods are used?\n: To create a migration in Database Migration Service, connectivity must be established\n between the source and the Cloud SQL destination instance. There are a variety of methods supported.\n Choose the one that works best for the specific workload.\n\n\nWhat are the known limitations?\n: See [Known limitations](/database-migration/docs/mysql/known-limitations)."]]
