Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/database-migration/docs/mysql/migration-fidelity below:

Migration fidelity | Database Migration Service

Stay organized with collections Save and categorize content based on your preferences.

When you're migrating your schema, data, and metadata from a source database to a destination database, you want to ensure that all of this information is migrated accurately. Database Migration Service provides a high-fidelity way to migrate database objects (including the schema, data, and metadata) from one database to another.

All of the following data, schema, and metadata components are migrated as part of the database migration:

• All tables from all databases and schemas, excluding the following system databases: sys, mysql, performance_schema, and information_schema.

• Naming

• Primary key

• Data type

• Ordinal position

• Default value

• Nullability

• Auto-increment attributes

• Secondary indexes

• Stored procedures

• Functions

• Triggers

• Views

• Foreign key constraints

Data manipulation language (DML) and data definition language (DDL) changes to all data, schemas, and metadata listed above are updated during continuous migrations.

When migrating a MySQL database, MySQL system databases aren't migrated. These databases contain information about users and privileges. Because of this, user account login information must be managed in the destination Cloud SQL database instance directly.

To add users to the Cloud SQL destination instance, navigate to the instance and add users from the Users tab, or add them from the MySQL client.

Learn more about creating and managing MySQL users.

In addition to users and privileges, non-default flag settings aren't migrated to the Cloud SQL destination instance. Run SHOW VARIABLES on your source database before migrating your schema, data, and metadata to the destination database, and then run it again on the Cloud SQL database. Update flag settings as needed on the Cloud SQL database to replicate the source settings.

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-07 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-07 UTC."],[[["Database Migration Service ensures accurate migration of database objects, including schema, data, and metadata, from one database to another."],["All tables, excluding MySQL system databases such as `sys`, `mysql`, `performance_schema`, and `information_schema`, are migrated."],["Schema elements like naming, primary keys, data types, and metadata components such as stored procedures, functions, and triggers are all migrated."],["User account login information and non-default flag settings are not migrated; they must be managed directly in the Cloud SQL destination instance."],["Data manipulation language (DML) and data definition language (DDL) changes to data, schema, and metadata are continuously updated during ongoing migrations."]]],[]]

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