Features and documentation updates for DTS in 2021.
December 2021
|
Type |
Highlights |
References |
|
New |
Incremental migration from PolarDB for PostgreSQL (Compatible with Oracle) to a self-managed Oracle database supports the following DDL operations:
|
Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to a self-managed Oracle database |
|
Incremental synchronization and migration from DB2 for LUW to AnalyticDB for PostgreSQL supports the following DDL operations:
|
Documentation is in progress |
|
|
Optimization |
DTS synchronization and migration tasks support SQL Server 2019 as the source and destination instance. |
November 2021
|
Type |
Description |
References |
|
New |
Synchronize data from a PolarDB-X 1.0 source instance across Alibaba Cloud accounts (New console). |
|
|
Schema synchronization between PolarDB-X 1.0 instances (new console). |
||
|
Optimization |
View retry details for retrying DTS tasks (new console). |
None |
|
Optimized DTS tasks that use PolarDB-X 1.0, Redis, or DataHub as the source. |
October 2021
|
Type |
Description |
References |
|
New |
Synchronize or migrate data from a self-managed Oracle database to Alibaba Cloud Message Queue for Apache Kafka or a self-managed Kafka cluster (New console). |
|
|
Synchronize data from a self-managed PostgreSQL database to PolarDB for PostgreSQL (Compatible with Oracle) (New console). |
||
|
Optimization |
Sort DTS tasks by synchronization or incremental migration latency (new console). |
None |
September 2021
|
Type |
Description |
References |
|
New |
Synchronize data between Tair (compatible with Redis) instances. Synchronize data from a Tair (compatible with Redis) instance across Alibaba Cloud accounts (New console). |
|
|
Two-way synchronization between ApsaraDB for MongoDB sharded cluster instances (new console). |
Two-way synchronization between ApsaraDB for MongoDB sharded cluster instances |
August 2021
|
Type |
Description |
References |
|
New |
Change tracking for PolarDB-X 1.0 (new console). |
|
|
Synchronize or migrate data from PolarDB-X 2.0 to Elasticsearch (New console). |
July 2021
|
Type |
Description |
References |
|
New |
Two-way synchronization between self-managed PostgreSQL databases and between ApsaraDB RDS for PostgreSQL instances (new console). Note
This feature is available only in the China (Hangzhou), China (Shanghai), and China (Qingdao) regions. |
|
|
Change tracking for self-managed PostgreSQL, ApsaraDB RDS for PostgreSQL, and PolarDB for PostgreSQL (Compatible with Oracle) (new console). Note
Change tracking tasks in the China (Hangzhou) and China (Shanghai) regions support schema updates for the source instance. |
||
|
The new console supports the following tasks:
|
|
|
|
Synchronize or migrate data from PolarDB-X 2.0 to Alibaba Cloud Message Queue for Apache Kafka or a self-managed Kafka cluster (new console). |
||
|
Upgrade link specifications of subscription and pay-as-you-go instances (new console). |
||
|
Switch between subscription and pay-as-you-go billing methods. The instance ID remains unchanged (new console). |
June 2021
|
Type |
Description |
References |
|
New |
Data synchronization from ApsaraDB RDS for SQL Server to ApsaraDB RDS for MySQL (New console). |
Synchronize data from ApsaraDB RDS for SQL Server to ApsaraDB RDS for MySQL |
|
Data migration from a self-managed HBase cluster to AnalyticDB for MySQL is supported in the new console. |
Migrate data from a self-managed HBase cluster to AnalyticDB for MySQL 3.0 |
|
|
Data synchronization from a self-managed Oracle database to DataHub is supported in the Legacy Console. |
Synchronize data from a self-managed Oracle database to DataHub |
May 2021
|
Type |
Description |
References |
|
New |
The ETL feature is available in the new console. It supports PolarDB for MySQL as the source and AnalyticDB for MySQL as the destination. Note
The ETL feature is in public preview. Click the application link to enable the feature. |
|
|
Migrate and synchronize data from MySQL (self-managed and ApsaraDB RDS) and PolarDB for MySQL to AnalyticDB for MySQL 3.0 (new console). |
||
|
Data synchronization between SQL Server instances (self-managed SQL Server and ApsaraDB RDS for SQL Server) (New console). |
Synchronize data between ApsaraDB RDS for SQL Server instances |
|
|
Schema migration and full data migration from Teradata to AnalyticDB for PostgreSQL (New console). Note
This feature is available only in the China (Shanghai), China (Qingdao), and China (Zhangjiakou) regions. |
||
|
The new console supports configuring change tracking instances (new version). Note
The legacy change tracking feature was taken offline on March 31, 2020. Upgrade to the new change tracking feature. |
April 2021
|
Type |
Description |
References |
|
New |
The ETL feature is in public preview. Use it to cleanse and transform data in databases. Note
|
|
|
The new console supports the following tasks:
|
|
|
|
Synchronize data from a self-managed Oracle database to AnalyticDB for PostgreSQL (new console). |
Synchronize data from a self-managed Oracle database to AnalyticDB for PostgreSQL |
|
|
Migrate or synchronize data from PostgreSQL (self-managed and ApsaraDB RDS) to MySQL (self-managed and ApsaraDB RDS), with schema migration and synchronization support. |
||
|
Synchronize data from a logical database configured in Data Management (DMS) to AnalyticDB for MySQL (new console). Important
This feature is available only in the China (Shanghai) and Singapore regions. |
Synchronize data from a DMS logical database to AnalyticDB for MySQL 3.0 |
March 2021
|
Type |
Description |
References |
|
New |
Synchronize data between PolarDB-X 2.0 instances (new console). |
|
|
Synchronize data from PolarDB-X 2.0 to ApsaraDB RDS for MySQL or PolarDB for MySQL (new console). |
||
|
Migrate data from PostgreSQL (self-managed and ApsaraDB RDS) to MySQL (self-managed and ApsaraDB RDS). |
Migrate data from ApsaraDB RDS for PostgreSQL to ApsaraDB RDS for MySQL |
|
|
A Change Data Capture (CDC)-based mode is added for ApsaraDB RDS for SQL Server sources, resolving log truncation interruptions and enabling migration of heap tables and tables without primary keys. |
||
|
Quick diagnostics for migration and synchronization tasks can now detect Database Autonomy Service (DAS) exceptions when diagnosing source database performance. Note
The source instance must be connected to DAS, and the database type must be MySQL. |
||
|
Optimization |
Filter DTS instances by RegionId when calling OpenAPI operations. |
February 2021
|
Type |
Description |
References |
|
Optimization |
Timestamp-based incremental mode is available as a scheduling policy for data integration tasks to AnalyticDB for MySQL. |
January 2021
|
Type |
Description |
References |
|
New |
You can synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for MySQL. |
Synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for MySQL 3.0 |
|
Configure a case sensitivity policy for object names in the destination database during migration or synchronization. |
Case sensitivity policy for the names of objects in the destination database |
|
|
When an Online DDL operation is performed on the source via Data Management (DMS), you can choose whether to migrate or synchronize the resulting temporary tables in the DTS console. |