This topic describes the release history of Data Transmission Service (DTS) features and provides the links to the relevant documentation.

2020

Release time Description Documentation
May 2020 Incremental data migration from a TiDB database to an ApsaraDB RDS for MySQL instance, an Apsara PolarDB for MySQL cluster, or a user-created MySQL database is supported. Migrate incremental data from a user-created 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 user-created SQL Server database to an ApsaraDB RDS for SQL Server database
On-premises databases can be connected to DTS over Enterprise Network Cloud (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. Communication between the local IDC and DTS cloud services through 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 databases. Connect an on-premises database or a database hosted on a third-party cloud to Alibaba Cloud Database Gateway
March 2020 Data migration and synchronization between PolarDB databases compatible with Oracle are supported. These features are applicable to scenarios such as disaster recovery, read/write splitting, and nearby queries.
Two-way data synchronization between Apsara PolarDB for MySQL clusters is supported. This feature is applicable to scenarios such as active geo-redundancy. Configure two-way data synchronization between Apsara 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 ApsaraDB RDS for SQL Server instance to an AnalyticDB for PostgreSQL instance
The schema and data of a PostgreSQL partition table can be migrated. Migrate incremental data from a user-created PostgreSQL database (version 10.x to 12) to an ApsaraDB RDS for PostgreSQL instance
Data synchronization from a PostgreSQL database to an AnalyticDB for PostgreSQL instance is supported. Initial schema synchronization and initial 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, Data Management (DMS) Enterprise Edition 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 the table schema without locking
Data migration from Oracle databases (versions 9i, 10g, 11g, 12c, 18c, and 19c) is supported. This feature allows you to migrate data from Oracle databases to non-Oracle databases. Migrate data from a user-created Oracle database to a PolarDB cluster compatible with Oracle
Data migration from PostgreSQL databases (version 12) is supported. Migrate incremental data from a user-created PostgreSQL database (version 10.x to 12) to an ApsaraDB RDS for PostgreSQL instance
During data migration, a source or destination Apsara 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 under 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 Documentation
December 2019 Data migration from PostgreSQL databases (version 11) is supported. Migrate incremental data from a user-created PostgreSQL database (version 10.x to 12) to an ApsaraDB RDS for PostgreSQL instance
Data synchronization from a user-created PostgreSQL database (versions 9.x to 11.x) to an AnalyticDB for PostgreSQL instance is supported. Synchronize data from a user-created 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 user-created MySQL database, an ApsaraDB RDS for MySQL instance, or an Apsara 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 through SSL-encrypted migration channels. This type of migration channel is secure and reliable.
Migrate a MongoDB Atlas database to Alibaba Cloud through DTS
September 2019 Data migration from ApsaraDB for MariaDB TX instances, PolarDB databases compatible with Oracle, and ApsaraDB RDS for SQL Server 2017 instances is supported. Databases supported by DTS features
July 2019 Data migration from MongoDB databases (version 4.0) and PostgreSQL databases (version 10.x) is supported. Databases supported by DTS features
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 supported. Change tracking (new)
Data migration, data synchronization, and change tracking from MySQL databases (version 8.0) are supported. Databases supported by DTS features

Before 2019

Release time Description Documentation
July 3, 2018 Data migration from a MySQL database to an Apsara PolarDB for MySQL cluster is supported. Migrate data from a user-created MySQL database to an ApsaraDB for PolarDB cluster
June 12, 2018 Data migration from a Db2 database to a MySQL database is supported. Migrate data from a user-created Db2 database to an ApsaraDB RDS for MySQL database
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 28, 2015 Change tracking from ApsaraDB RDS for MySQL instances is supported. Track data changes from ApsaraDB RDS for MySQL (previous)
July 21, 2015 Data migration from an Oracle database to an ApsaraDB RDS for PPAS instance is supported. Migrate data from a user-created Oracle database to an ApsaraDB RDS for PPAS instance
Data migration from RDS instances on the 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 user-created SQL Server database to an ApsaraDB RDS for SQL Server database
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 user-created Oracle database to an ApsaraDB RDS for MySQL instance
Data migration between MySQL databases is supported. Migrate data from a user-created 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. Use conditions to filter data