This topic describes the release notes for Data Transmission Service (DTS) in 2020 and provides links to the relevant references.
2020
| Release date | 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 for Oracle 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 for Oracle 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 skipped. | N/A | |
| DTS can retry the connection to the source and destination databases within a specified period of time. | N/A | |
| 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 for Oracle 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 for Oracle cluster | |
| Data synchronization to an Elasticsearch cluster (version 7.4) is supported. | ||
| The task diagnostics feature is supported for data migration and data 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 for Oracle cluster is supported. | Migrate data from an ApsaraDB RDS for PPAS instance to a PolarDB for Oracle 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 at the earliest opportunity. | Configure alert rules for DTS tasks in the CloudMonitor console | |
| Regular full 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 instances. | Migrate data from an ApsaraDB RDS for MariaDB 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 was 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 for Oracle clusters are supported. These features are applicable to scenarios such as disaster recovery, read/write splitting, and nearby queries. | |
| Two-way 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 13.0) 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, DDL statements can be executed in Data Management (DMS) to change schemas online. 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. | Perform lock-free DDL operations |
| 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 13.0) 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. | N/A | |
| 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 |