What's New
The tables below describe the functions released in each Database and Application Migration UGO version and corresponding documentation updates. New features will be successively launched in each region.
March 2024
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Rules |
You can export rule templates and import user-defined templates. |
Commercial use |
|
|
2 |
A migration link added |
MySQL can be migrated to GaussDB Primary/Standby (Compatible with M). |
Commercial use |
January 2024
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A migration link added |
PostgreSQL and Microsoft SQL Server can be migrated to GaussDB 8.0. |
Commercial use |
November 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
SQL Review added |
You can check whether SQL statements comply with specifications and affect performance. |
Commercial use |
|
|
2 |
New source databases supported |
The source database can be Oracle 21c or Microsoft SQL Server. |
Commercial use |
October 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A migration link added |
You can migrate GoldenDB to GaussDB. |
Commercial use |
|
|
2 |
DB_LINK object collection added |
During the migration from Oracle to GaussDB 3.2 Enterprise Edition, DB_LINK objects can be collected, converted, and migrated. |
Commercial use |
August 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
New source and target databases supported |
Oracle and MySQL can be migrated to GaussDB 8.0 Enterprise Edition. |
Commercial use |
July 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A section added |
The section "Configuring a Conversion Plan" is added. |
Commercial use |
June 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A section added |
The section "Re-Collecting Objects" is added. |
Commercial use |
|
|
2 |
A function added |
Compatibility mode check is added. |
Commercial use |
|
|
3 |
A section added |
The section "Conversion Configuration" is added. |
Commercial use |
April 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
An FAQ added |
The FAQ "How Does UGO Collect Data from the Source Database?" is added. |
Commercial use |
|
|
2 |
A section added |
The section "Re-Evaluating a Task" is added. |
Commercial use |
|
|
3 |
Migration links and WebUI optimized |
|
Commercial use |
|
|
4 |
Alarm information optimized |
The alarm information during syntax conversion is modified. |
Commercial use |
|
|
5 |
Migration links added |
|
Commercial use |
|
|
6 |
GaussDB version number updated |
GaussDB versions are updated based on Huawei Cloud International website. |
Commercial use |
March 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Custom schema name added |
There is a custom schema name when the source database type is MySQL. |
Commercial use |
What Is the Function of the dsc_ora_ext Schema Generated After Migration to the Target Database? |
|
2 |
New migration links added |
There are guidelines about how to create GaussDB databases that are compatible with the source databases DB2 and PostgreSQL. |
Commercial use |
How Do I Create GaussDB Databases Compatible with Source Databases? |
|
3 |
Mapping between GaussDB 3.2 and kernel versions added |
The mapping between GaussDB 3.2 and kernel versions is added. |
Commercial use |
|
|
4 |
Functions optimizated |
|
Commercial use |
|
|
5 |
Schemas that are ignored during the migration |
There are schemas that are ignored during the migration when the source databases are MySQL, DB2, and PostgreSQL. |
Commercial use |
Which Schemas in Source Databases Are Ignored for Migration? |
|
6 |
A column added |
The Skip column is added. |
Commercial use |
|
|
7 |
Console optimized |
Refresh button icons are updated. |
Commercial use |
|
|
8 |
Migration links added |
You can migrate MySQL or Oracle to GaussDB 3.2 after you submit an application. |
Commercial use |
|
|
9 |
Prerequisites added |
The prerequisites for creating an evaluation project are added when Oracle is the source database type. |
Commercial use |
February 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Evaluation information of a new migration link added & GUI optimized |
|
Commercial use |
|
|
2 |
Two migration links added |
|
Commercial use |
|
|
3 |
Description and screenshots updated & Description optimized |
|
Commercial use |
|
|
4 |
Password rules optimized |
The password rules are optimized. |
Commercial use |
|
|
5 |
User experience improved |
The console is optimized, and the GUI elements and screenshots are updated. |
Commercial use |
January 2023
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
New function |
The stopped evaluation projects can be resumed. |
Commercial use |
|
|
2 |
Check items updated |
The check items are changed when MySQL is used as the source database type. |
Commercial use |
|
|
3 |
Re-conversion process optimized |
The re-conversion process is optimized. |
Commercial use |
|
|
4 |
MySQL migration constraints removed |
You do not need to submit an application when you migrate MySQL. |
Commercial use |
|
|
5 |
Two migration links added |
|
Commercial use |
December 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A migration link added |
MySQL 5.6 can be used as a source database. If you want to migrate MySQL 5.6, submit an application. |
Commercial use |
|
|
2 |
Description for source database profiling modified |
TPS, QPS, and table complexity are not displayed in the source database profiling. |
Commercial use |
|
|
3 |
GaussDB version number changed |
GaussDB 2.3 is changed to GaussDB 2.7. |
Commercial use |
|
|
4 |
Screenshots updated |
MySQL 5.6 can be used as a source database and GaussDB 2.3 is changed to GaussDB 2.7. Some screenshots are updated. |
Commercial use |
|
|
5 |
A note added |
You need to upload the specified certificate type for the target database GaussDB. |
Commercial use |
|
|
6 |
Description updated |
TPS, QPS, and table complexity are not displayed in the source database profiling. |
Commercial use |
|
|
7 |
Description optimized |
The content and GUI elements in the Compatibility Analysis area on the Target DB Analysis tab page are updated. |
Commercial use |
|
|
8 |
New function |
You can enter the full -screen mode or exit the mode on the object correction page. |
Commercial use |
|
|
9 |
Description for an FAQ updated |
The description of an FAQ is updated due to GUI optimization. |
Commercial use |
November 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A note added |
The following note is added: One Way SSL is not suitable for the target database GaussDB. |
Commercial use |
|
|
2 |
A note added |
The following note is added: When the target database is GaussDB Centralized 3.1, DB Information Input Type is set to Manually Input. |
Commercial use |
|
|
3 |
Migration link table optimized |
A two-dimensional table is used to display migration links. |
Commercial use |
|
|
4 |
Screenshots updated |
Some screenshots are updated because GaussDB Centralized 3.1 can be used as the target database. |
Commercial use |
|
|
5 |
A migration link added |
GaussDB Centralized 3.1 can be used as the target database during the migration. |
Commercial use |
October 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
A migration link added |
The migration from MySQL to GaussDB Centralized-2.3 is supported. |
Commercial use |
|
|
2 |
Database information input types updated |
When the target database type is GaussDB, you can select Select Instance for DB Information Input Type. |
Commercial use |
|
|
3 |
Check items updated |
The pre-check items of the source database MySQL are updated. |
Commercial use |
|
|
4 |
Collection types updated |
SQL object types are not collected during evaluation project creation. |
Commercial use |
|
|
5 |
An FAQ added |
The FAQ "Why Cannot I Use Some Functions?" is added. |
Commercial use |
September 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Version numbers updated |
GaussDB version numbers are updated. |
Commercial use |
|
|
2 |
A region added |
The LA-Santiago region is added. |
Commercial use |
|
|
3 |
Constraints added |
If you select MySQL or DB2 as the source database type, you need to enable the whitelist. |
Commercial use |
|
|
4 |
Screenshots updated |
The screenshots for migration project creation are updated. |
Commercial use |
|
|
5 |
GUI for evaluation project information optimized |
The GUI for the evaluation project information is optimized. |
Commercial use |
August 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
MySQL and DB2 information added in the evaluation project creation |
Information about MySQL and DB2 as source databases are added in the evaluation project creation. |
Commercial use |
|
|
2 |
Screenshots on migration project creation updated |
The screenshots for migration project creation are updated. |
Commercial use |
|
|
3 |
Screenshots on evaluation project creation updated |
The screenshots for evaluation project creation are updated. |
Commercial use |
|
|
4 |
Evaluation project details of MySQL and DB2 added |
The evaluation project details of MySQL and DB2 are added. |
Commercial use |
|
|
5 |
Screenshots on project migration updated and GUI element updated |
The screenshots for project migration are updated. Summary Report is changed to Migrate and Verify Report. |
Commercial use |
|
|
6 |
MySQL and DB2 information added in the project migration |
Information about MySQL and DB2 as source databases are added in the project migration. |
Commercial use |
|
|
7 |
Object migration details modified |
The content in the table in section "Viewing Object Migration Details" is modified. |
Commercial use |
|
|
8 |
Note on SQL statement conversion modified and Screenshots updated |
The note on SQL statement conversion is modified. Screenshots for SQL statement conversion are updated. |
Commercial use |
|
|
9 |
A note added |
A note is added in the section "Running Differentiation Analysis and Viewing the Generated Report". |
Commercial use |
Running Differentiation Analysis and Viewing the Generated Report |
|
10 |
A note added |
A note on incremental evaluation is added. |
Commercial use |
July 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Source and target database types added |
MySQL-8.0 can be used as a source database. The following databases can be used target databases: distributed GaussDB 2.7.T0710, centralized GaussDB 2021, and centralized GaussDB 2.7.T0710. |
Commercial use |
|
|
2 |
Screenshots update |
Screenshots are updated to show new source and target database types. |
Commercial use |
June 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
New source databases added |
DB2 and MySQL databases can be used as source databases. |
Commercial use |
|
|
2 |
GUI update |
The Basic Details and Precheck pages are updated. |
Commercial use |
|
|
3 |
Permission check before database evaluation project creation |
When you create a database evaluation task, UGO checks the permissions of the source database first. |
Commercial use |
|
|
4 |
GUI update |
The Target DB Analysis page is updated. |
Commercial use |
|
|
5 |
Report descriptions added |
Restrictions on password usage and descriptions of reports are added. |
Commercial use |
|
|
6 |
GUI element update |
Update Status is changed to Bulk Update Status, and Bulk Update is changed to Bulk Statement Update. |
Commercial use |
May 2022
|
No. |
Feature |
Description |
Phase |
Document |
|---|---|---|---|---|
|
1 |
Database and Application Migration UGO |
Commercial use of the first version of Database and Application Migration UGO. |
Commercial use |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
