This topic describes the release notes for Data Transmission Service (DTS) and provides links to the relevant references.

2021

Release time Description References
April 2021 A logical database that is configured by using Data Management (DMS) can be synchronized to an AnalyticDB for MySQL cluster. Coming Soon
March 2021 DTS instances can be filtered based on the system parameter RegionId. DescribeMigrationJobStatus (example)
January 2021 If DMS is used to perform online DDL operations on the source database, whether to synchronize the temporary tables generated by online DDL operations can be specified in the DTS console.

2020

Release time Description References
December 2020 Schema migration and full data migration from a MaxCompute project to a self-managed MySQL database or an ApsaraDB RDS for MySQL instance are supported. Migrate data from a MaxCompute project to an ApsaraDB RDS for MySQL instance
Schema migration from a Db2 for i database to a self-managed MySQL database or an ApsaraDB RDS for MySQL instance is supported. Migrate data from a self-managed Db2 database to an ApsaraDB RDS for MySQL instance
Partitioned tables can be migrated from an Oracle database to a self-managed MySQL database, an ApsaraDB RDS for MySQL instance, or a PolarDB O Edition cluster.
November 2020 Full data migration and incremental data migration from a PolarDB for PostgreSQL cluster to a self-managed Oracle database are supported. Migrate data from a PolarDB for PostgreSQL cluster to a self-managed Oracle database
October 2020 DTS Avro or Canal JSON can be used as the format to store the data that is synchronized from a self-managed MySQL database or an ApsaraDB RDS for MySQL instance to a Message Queue for Apache Kafka instance or a self-managed Kafka cluster. The Canal JSON format ensures that Canal users can migrate data with ease. Data formats of a Kafka cluster
DTS Avro or SharePlex JSON can be used as the format to store the data that is migrated from a PolarDB O Edition cluster to a Message Queue for Apache Kafka instance or a self-managed Kafka cluster. Data formats of a Kafka cluster
Data migration from a self-managed Oracle database to a Message Queue for Apache Kafka instance or a self-managed Kafka cluster is supported. Migrate data from a self-managed Oracle database to a Message Queue for Apache Kafka instance
Alerts for precheck items can be ignored. None
DTS can retry the connection to the source and destination databases within a specified period of time. None
The tags for DTS tasks can be edited.
September 2020 Data synchronization from a self-managed TiDB database to an AnalyticDB for MySQL cluster is supported. The data synchronization feature facilitates data transmission and analysis. Synchronize data from a self-managed TiDB database to an AnalyticDB for MySQL cluster
The ROWID values in tables without primary keys can be migrated from a self-managed Oracle database to a PolarDB O Edition cluster. This feature can be used to deduplicate and verify data in tables without primary keys. Migrate data from a self-managed Oracle database to a PolarDB O Edition cluster
Data synchronization to an Elasticsearch cluster (version 7.4) is supported.
The task diagnostics feature is supported for data migration and synchronization. DTS analyzes the performance of incremental data migration and provides insights for you to identify and solve issues.
August 2020 Data migration from a MySQL database to a self-managed Kafka cluster with a public IP address is supported. The source MySQL database can be a self-managed MySQL database, an ApsaraDB RDS for MySQL instance, or a PolarDB for MySQL cluster. Migrate data from an ApsaraDB RDS for MySQL instance to a self-managed Kafka cluster
Data migration from an ApsaraDB RDS for PPAS instance (version 9.3, 9.6, or 10.0) to a PolarDB O Edition cluster is supported. Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB O Edition cluster
July 2020 A single data migration task can migrate the incremental data of multiple SQL Server databases. This feature improves migration efficiency. Migrate incremental data from a self-managed SQL Server database to an ApsaraDB RDS for SQL Server instance
The policy for synchronizing data to multiple Kafka partitions can be specified. This feature improves synchronization performance.
DTS is integrated with CloudMonitor. Alert rules can be set for DTS tasks in the CloudMonitor console. Abnormal data can be detected and errors can be troubleshooted in a timely manner. Set alert rules for DTS tasks in the Cloud Monitor console
Regular data migration is upgraded to data integration. Data warehouses such as a T+1 data warehouse can be flexibly built by using the data integration feature.
The task diagnosis feature is supported. DTS tasks can be monitored by using metrics such as network connection status, network latency, and bandwidth.
Tables without primary keys can be migrated from ApsaraDB RDS for MariaDB TX instances. Migrate data from an ApsaraDB RDS for MariaDB TX instance to an ApsaraDB RDS for MySQL instance
Date migration from a self-managed Oracle database to a PolarDB for MySQL cluster is supported. Migrate data from a self-managed Oracle database to a PolarDB for MySQL cluster
June 2020 Data migration from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance is supported in the China (Shanghai), China (Beijing), and China (Shenzhen) regions. Real-time data warehouses can be built by using the data migration feature. Migrate data from a self-managed Oracle database to an AnalyticDB for PostgreSQL instance
Data migration from MongoDB databases (version 4.2) is supported. Overview of data migration scenarios
A PolarDB-X database that is created based on private ApsaraDB RDS for MySQL instances can be used as the source or destination database for data synchronization. PolarDB-X is formerly known as Distributed Relational Database Service (DRDS). Overview of data synchronization scenarios
May 2020 Incremental data migration from a TiDB database to an ApsaraDB RDS for MySQL instance, a PolarDB for MySQL cluster, or a self-managed MySQL database is supported. Migrate incremental data from a self-managed TiDB database to an ApsaraDB RDS for MySQL instance
The stability of incremental data migration for SQL Server databases is improved. The issue of data synchronization failure caused by log truncation is solved. Migrate incremental data from a self-managed SQL Server database to an ApsaraDB RDS for SQL Server instance
On-premises databases can be connected to DTS over Cloud Enterprise Network (CEN). An on-premises database can be used as the source or destination database for data migration or synchronization. DTS provides secure data migration to Alibaba Cloud. Connect an on-premises database to DTS by using CEN
April 2020 An on-premises database or a database hosted on a third-party cloud can be connected to DTS over Database Gateway. These databases can be used as the source or destination database. Connect an on-premises database or a database hosted on a third-party cloud to Alibaba Cloud by using Database Gateway
March 2020 Data migration and synchronization between PolarDB O Edition clusters are supported. These features are applicable to scenarios such as disaster recovery, read/write splitting, and nearby queries.
Two-way data synchronization between PolarDB for MySQL clusters is supported. This feature is applicable to scenarios such as active geo-redundancy. Configure two-way data synchronization between PolarDB for MySQL clusters
Data synchronization from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for PostgreSQL instance is supported. This feature is applicable to scenarios such as real-time data analysis. Synchronize data from an ApsaraDB RDS for SQL Server instance to an AnalyticDB for PostgreSQL instance
The schema and data of a PostgreSQL partitioned table can be migrated. Migrate incremental data from a self-managed PostgreSQL database (version 10.1 to 12) to an ApsaraDB RDS for PostgreSQL instance
Data synchronization from a PostgreSQL database to an AnalyticDB for PostgreSQL instance is supported. Schema synchronization and full data synchronization of sequences are supported.
Action-level permissions on DTS instances can be granted to RAM users. This feature is applicable to scenarios such as precise access control. Use a custom policy to authorize a RAM user to manage DTS instances
February 2020 During data synchronization, DMS Enterprise can be used to perform online DDL schema changes.
Note If your data synchronization task was created before February 14, 2020, and has not been restarted on or after this date, you cannot use the preceding feature. In this case, you must stop and restart the data synchronization task before you can use the feature.
Change schemas without locking tables
Data migration from Oracle databases (version 9i, 10g, 11g, 12c, 18c, or 19c) is supported. Migrate data from a self-managed Oracle database to a PolarDB for Oracle cluster
Data migration from PostgreSQL databases (version 12) is supported. Migrate incremental data from a self-managed PostgreSQL database (version 10.1 to 12) to an ApsaraDB RDS for PostgreSQL instance
During data migration, a source or destination PolarDB for MySQL cluster can be switched across different zones in the same region. This operation does not interrupt the data migration task. None
January 2020 Permissions on specific DTS instances can be granted to RAM users. A RAM user of an Alibaba Cloud account can access DTS instances that are owned by another Alibaba Cloud account by assuming an authorized RAM role. This allows you to have precise access control over specific DTS instances. Use a custom policy to authorize a RAM user to manage DTS instances

2019

Release time Description References
December 2019 Data migration from PostgreSQL databases (version 11) is supported. Migrate incremental data from a self-managed PostgreSQL database (version 10.1 to 12) to an ApsaraDB RDS for PostgreSQL instance
Data synchronization from a self-managed PostgreSQL database (versions 9.x to 11.x) to an AnalyticDB for PostgreSQL instance is supported. Synchronize data from a self-managed PostgreSQL database to an AnalyticDB for PostgreSQL instance
Data migration from a MySQL database to an AnalyticDB for MySQL cluster (version 3.0) is supported. The source MySQL database can be a self-managed MySQL database, an ApsaraDB RDS for MySQL instance, or a PolarDB for MySQL cluster. Overview of data migration scenarios
Disaster recovery instances can be created for ApsaraDB RDS for MySQL instances. Create a disaster recovery instance
October 2019 Data migration from MongoDB Atlas databases is supported. Transaction logs are supported.
Note DTS connects to MongoDB Atlas by using SSL-encrypted migration channels. This type of migration channel is secure and reliable.
Migrate data from a MongoDB Atlas database to Alibaba Cloud
September 2019 Data migration from ApsaraDB for MariaDB TX instances, PolarDB O Edition clusters, and ApsaraDB RDS for SQL Server instances (version 2017) is supported. Supported databases
July 2019 Data migration from MongoDB databases (version 4.0) and PostgreSQL databases (version 10.x) is supported. Supported databases
Notification of alert clearance events is supported. If an alert is cleared, you will receive an SMS message. This reduces your O&M costs. None
June 2019 The online query feature is optimized to improve the user experience of change tracking. View tracked data changes
The full data migration feature is upgraded. The logic for resuming migration tasks is optimized to achieve near-lossless resumable transmission. None
May 2019 The new change tracking feature is available. Change tracking (new)
Data migration, data synchronization, and change tracking are supported for MySQL databases (version 8.0). Supported databases

Before 2019

Release time Description References
July 3, 2018 Data migration from a MySQL database to a PolarDB for MySQL cluster is supported. Migrate data from a self-managed MySQL database to a PolarDB for MySQL cluster
June 12, 2018 Data migration from a Db2 database to a MySQL database is supported. Migrate data from a self-managed Db2 database to an ApsaraDB RDS for MySQL instance
October 30, 2015 Data synchronization between RDS instances is supported.
August 11, 2015
  • During data migration, databases can be automatically created in destination instances.
  • After data is migrated, the CIDR blocks of DTS servers are automatically removed from the whitelists of RDS instances.
None
July 21, 2015 Data migration from an Oracle database to an ApsaraDB RDS for PPAS instance is supported. Migrate data from a self-managed Oracle database to an ApsaraDB RDS for PPAS instance
Data migration from RDS instances deployed on Alibaba Finance Cloud is supported. None
June 5, 2015 Data migration between ApsaraDB RDS for SQL Server instances is supported. Migrate incremental data from a self-managed SQL Server database to an ApsaraDB RDS for SQL Server instance
May 28, 2015 Incremental data migration between ApsaraDB RDS for MySQL instances is supported. Migrate data between RDS instances
April 28, 2015 Data migration from an Oracle database to a MySQL database is supported. Migrate data from a self-managed Oracle database to an ApsaraDB RDS for MySQL instance
Data migration between MySQL databases is supported. Migrate data from a self-managed MySQL database to an ApsaraDB RDS for MySQL instance
Object name mapping for columns, tables, and databases is supported. Object name mapping
Columns, tables, and databases can be selected as the objects to be migrated. None
Objects can be filtered based on specific conditions. Filter the data to be migrated