This topic describes the release history of major Advanced Database & Application Migration (ADAM) features and provides the links to the relevant documentation.
Release date | Feature | Description | Documentation |
---|---|---|---|
November 25, 2020 | Application transformation based on static code (iBATIS in JAVA) | Static code files can be uploaded. The SQL statements that need to be transformed can be identified. | |
November 25, 2020 | ApsaraDB RDS for PostgreSQL V12.0, ApsaraDB RDS for PostgreSQL V9.4, and ApsaraDB RDS for MySQL V8.0 | ApsaraDB RDS for PostgreSQL V12.0, ApsaraDB RDS for PostgreSQL V9.4, and ApsaraDB RDS for MySQL V8.0 can be evaluated, transformed, and migrated. | |
September 24, 2020 | PolarDB-X and PolarDB for PostgreSQL | PolarDB-X and PolarDB for PostgreSQL can be evaluated, transformed, and migrated. | |
September 24, 2020 | Custom rules for schema transformation and migration | Rules can be configured before schemas are migrated. | |
September 24, 2020 | Database Gateway connection | Database Gateway can be used to access source Oracle databases when the database information is collected and databases are transformed. | |
August 20, 2020 | Schema inclusion and exclusion | Schemas can be excluded and then included when Data Transmission Service (DTS) is used to migrate data. | |
July 15, 2020 | Online database collection | The information of a database can be collected online without downloading a collection package. | |
April 2, 2020 | Migration process | The migration process that is adopted in the ADAM system is redefined to be three steps: evaluate databases, transform databases, and evaluate and transform applications. | |
April 2, 2020 | Online database transformation | Schemas can be migrated from Oracle databases to destination databases. During the migration process, schemas can be revised to simplify the procedure to construct destination databases. | |
January 19, 2020 | Database profiling | Compatibility analysis of source databases with available destination databases is supported. Destination databases can be selected by schema. | |
January 3, 2020 | Application evaluation | The planning and evaluation feature is supported to migrate large-scale Oracle databases and applications. This feature can be used to analyze the associations among databases and applications and the compatibility between source and destination databases. The feature can be used to evaluate applications and databases, generate overall transformation solutions, and provide suggestions on the transformation sequence. The feature can also be used to analyze the compatibility of SQL statements in applications and provide corresponding transformation solutions. |