This topic describes the release notes for Data Transmission Service (DTS) and provides links to the relevant references.
December 2021
Category | Key feature | References |
New feature | The following DDL operations are supported for incremental data migration from a PolarDB for Oracle cluster to a self-managed Oracle database:
| |
The following DDL operations are supported for incremental data synchronization and migration from DB2 for LUW databases to an AnalyticDB for PostgreSQL instance:
| Available soon | |
Optimized feature | DTS data synchronization and migration from an SQL Server instance and to an SQL Server instance are supported. |
November 2021
Category | Description | References |
New feature | Data synchronization across Alibaba Cloud accounts from a PolarDB-X 1.0 instance is supported in the new DTS console. | |
Schema synchronization between PolarDB-X 1.0 instances is supported in the new DTS console. | Available soon | |
Optimized feature | During a DTS task retry, the retry details can be viewed in the new DTS console. | None |
Data migration and synchronization tasks from PolarDB-X 1.0 instances, Redis and DataHub databases are optimized. |
October 2021
Category | Description | References |
New feature | Data synchronization and migration from a self-managed Oracle databases to Alibaba Cloud Message Queue for Apache Kafka or self-managed Kafka are supported in the new DTS console. | |
Data synchronization from a self-managed PostgreSQL database to a PolarDB for Oracle cluster is supported in the new DTS console. | ||
Optimized feature | The ranking of data synchronization or migration tasks based on latency is supported on the task list page in the new DTS console. | None |
September 2021
Category | Description | References |
New feature | Data synchronization between ApsaraDB for Redis instances within an Alibaba Cloud account or across accounts is supported in the new DTS console. | |
Two-way synchronization between ApsaraDB for MongoDB instances (sharded cluster architecture) is supported in the new DTS console. | Configure two-way data synchronization between ApsaraDB for MongoDB sharded cluster instances |
August 2021
Category | Description | References |
New feature | Change tracking for a Polar-X 1.0 instance is supported in the new DTS console. | |
Data synchronization and migration from a PolarDB-X instance to Elasticsearch are supported in the new DTS console. | Available soon |
July 2021
Category | Description | References |
New feature | Two-way synchronization between self-managed PostgreSQL databases and that between ApsaraDB RDS for PostgreSQL instances are supported in the new DTS console. Note You can configure the data synchronization task only in the China (Hangzhou), China (Shanghai), or China (Qingdao) region. | Configure two-way data synchronization between ApsaraDB RDS for PostgreSQL instances |
Change tracking for self-managed PostgreSQL databases, ApsaraDB RDS for PostgreSQL instances, and PolarDB for Oracle clusters is supported in the new DTS console. Note You can track schema updates from an instance only in the China (Hangzhou) or China (Shanghai) region. | ||
The following tasks can be configured in the new DTS console:
| ||
Data synchronization and migration from a PolarDB-X instance to Message Queue for Apache Kafka and self-managed Kafka databases are supported in the new DTS console. |
| |
DTS instances can be upgraded in the new DTS console. | ||
The billing method of a DTS instance can be switched between subscription and pay-as-you-go without changing the instance ID in the new DTS console. |
June 2021
Category | Description | References |
New feature | Data synchronization from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance is supported in the new DTS console. | Synchronize data from an ApsaraDB RDS for SQL Server instance to an ApsaraDB RDS for MySQL instance |
Data migration from a self-managed HBase database to an AnalyticDB for MySQL cluster is supported in the new DTS console. | Migrate data from a self-managed HBase database to an AnalyticDB for MySQL V3.0 cluster | |
Data synchronization from a self-managed Oracle database to DataHub is supported in the DTS console of the previous version. | Available soon |
May 2021
Category | Description | References |
New feature | The ETL (Extract Transform Load) feature is applicable to use DTS for scenarios in which the source is a PolarDB for MySQL cluster and the destination is an AnalyticDB for PostgreSQL instance in the new DTS console. Note The ETL feature is now in public preview in the new DTS console. During public preview, you can click the link for the request to enable the ETL feature. | |
Data synchronization and migration from a self-managed MySQL database, an ApsaraDB RDS for MySQL instance, or a PolarDB for MySQL cluster to an AnalyticDB for MySQL cluster version 3.0 are supported in the new DTS console. |
| |
Data synchronization between self-managed SQL Server databases and data synchronization between ApsaraDB RDS for MySQL instances are supported in the new DTS console. | Synchronize data between ApsaraDB RDS for SQL Server instances | |
Schema migration and full data migration from a Teradata database to an AnalyticDB for PostgreSQL instance are supported in the new DTS console. Note You can configure a data migration task for this scenario only in the China (Shanghai), China (Qingdao), or China (Zhangjiakou) region. | Migrate data from a Teradata database to an AnalyticDB for PostgreSQL instance | |
Change tracking instances can be configured in the new DTS console. Note We recommend that you update the change tracking feature to the new version because the new DTS console does not support the change tracking feature of the previous version since March 31, 2020. |
April 2021
Category | Description | References |
New feature | The ETL feature is in public preview in the new DTS console. ETL can be used to cleanse and process data in a database, which delivers the data you need precisely and efficiently. Note
| |
The following tasks can be configured in the new DTS console:
| ||
Data synchronization from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance is supported in the new DTS console. | Synchronize data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance | |
Schema migration and synchronization from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance to a self-managed MySQL database or an ApsaraDB RDS for MySQL instance are supported. | ||
A logical database that is configured by using Data Management (DMS) can be synchronized to an AnalyticDB for MySQL cluster in the new DTS console. Important You can configure a data migration or synchronization for this scenario only in the China (Shanghai) and Singapore (Singapore) regions. | Synchronize data from a DMS logical database to an AnalyticDB for MySQL V3.0 cluster |
March 2021
Category | Description | References |
New feature | Data synchronization between PolarDB-X instances is supported in the new DTS console. | Available soon |
Data synchronization from a PolarDB-X instance to an ApsaraDB RDS for MySQL instance or a PolarDB for MySQL cluster is supported in the new DTS console. |
| |
Data migration from a self-managed PostgreSQL database or an ApsaraDB RDS for PostgreSQL instance to a self-managed MySQL database or an ApsaraDB RDS for MySQL instance is supported. | Migrate data from an ApsaraDB RDS for PostgreSQL instance to an ApsaraDB RDS for MySQL instance | |
The change data capture (CDC) mode is supported for data migration and synchronization based on SQL Server log parsing from an ApsaraDB RDS for SQL Server instance. This way, data migration cannot be interrupted by log truncation. The CDC feature is not supported for the migration of heap tables and tables without primary keys. | ||
The task diagnostics feature can be used to diagnose exceptions of Database Autonomy Service (DAS) for source databases during a data migration or synchronization task. Note For this scenario, the source database must be connected to DAS, and the database must be a MySQL database. | ||
Optimized feature | DTS instances can be filtered based on the system parameter RegionId. | DescribeMigrationJobStatus (example) |
February 2021
Category | Description | References |
Optimized feature | If the destination instance of a data integration task is AnalyticDB for MySQL, the scheduling policy can be set to Timestamp-based Incremental Data Mode. |
January 2021
Category | Description | References |
New feature | Data synchronization from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for MySQL cluster is supported. | |
The capitalization of object names in a data migration or synchronization instance can be specified to meet the requirements of the destination database. | Specify the capitalization of object names in the destination instance | |
If DMS is used to perform online DDL operations on the source database, whether to migrate or synchronize the temporary tables generated by online DDL operations can be specified in the DTS console. |