Help Center/
GaussDB(for MySQL)/
Best Practices/
From Other Cloud MySQL to GaussDB(for MySQL)/
Checking Migration Results
Updated on 2023-10-19 GMT+08:00
Checking Migration Results
You can use either of the following methods to check the migration results:
- DRS compares migration objects, users, and data and provide comparison results. For details, see Checking the Migration Results on the DRS Console.
- Log in to the destination side to check whether the databases, tables, and data are migrated. Confirm the data migration status. For details, see Checking the Migration Results on the GaussDB(for MySQL) Console.
Checking the Migration Results on the DRS Console
- Log in to the management console.
- Click in the upper left corner of the management console and select region EU-Dublin.
- Under the service list, choose Databases > Data Replication Service.
- Click the DRS instance name.
- Click Migration Comparison and select Object-Level Comparison to check whether database objects are missing.
- Choose Data-Level Comparison and check whether the number of rows of migrated objects is consistent.
- Click Account-Level Comparison and check whether the accounts and permissions of the source and destination instances are the same.
Checking the Migration Results on the GaussDB(for MySQL) Console
- Log in to the management console.
- Click in the upper left corner of the management console and select region EU-Dublin.
- Under the service list, choose Databases > GaussDB(for MySQL).
- On the Instances page, locate the destination instance, and click Log In in the Operation column.
- In the dialog box that is displayed, enter the password and click Test Connection.
- After the connection is successful, click Log In.
- Check whether the destination databases and tables are the same as the source instance. Check whether migration is complete.
Parent topic: From Other Cloud MySQL to GaussDB(for MySQL)
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.