2024
Data Transmission Service (DTS) product feature updates and related documentation for 2024.
December 2024
|
Type |
Key Content |
References |
|
New feature |
Synchronizing or migrating MongoDB data to MySQL databases is now supported. |
|
|
New feature |
Synchronizing or migrating MongoDB data to PolarDB for MySQL clusters is now supported. |
|
|
New feature |
Source databases support Tair (Enterprise Edition) instances with SSD storage media. |
|
|
New feature |
Self-managed MongoDB 7.0 is now supported. |
|
|
Optimization |
Cross-Alibaba Cloud account support is available when the target Database Type is MongoDB and the Access Method is Alibaba Cloud Instance. |
November 2024
|
Type |
Key Content |
References |
|
New feature |
DTS instances can now connect to databases through VPC data channels. |
|
|
New feature |
Synchronizing or migrating events from source databases is now supported. |
|
|
New region |
The China (Wuhan - Local Region) region now supports creating DTS Serverless instances. |
|
|
New feature |
Abnormal database tables in DTS instances can now be recovered using the one-click fix feature. |
October 2024
|
Type |
Key Content |
References |
|
New feature |
Sequence values in destination databases can now be updated for some synchronization or migration instances. |
|
|
Optimization |
Full instance synchronization of MySQL databases to the cloud is now supported. |
September 2024
|
Type |
Key Content |
References |
|
New feature |
Added support for synchronizing or migrating SQL Server data to PostgreSQL databases. |
|
|
New feature |
Added support for synchronizing or migrating PolarDB for MySQL data to the Lindorm Table engine of Lindorm instances. |
|
|
New feature |
Added support for synchronizing or migrating MySQL or PolarDB for MySQL data to self-managed Doris databases. |
|
|
Optimization |
When the source database is MongoDB, incremental data is collected from the source database using Change Stream. |
August 2024
|
Type |
Key Content |
References |
|
New feature |
Migrating OceanBase (MySQL mode) data to Lindorm instances is now supported, reducing your database O&M costs. |
|
|
Optimization |
When the source or destination database is a multi-node deployment self-managed MongoDB database, you can enter multiple connection addresses to enhance DTS instance stability. |
Create instances with high availability MongoDB as the source or destination database |
|
Optimization |
Data synchronization or migration instances with a destination Database Type of Kafka support the add additional columns feature. |
|
|
Optimization |
Cross-Alibaba Cloud account support is available when the target Database Type is Tair/Redis and the Access Method is Alibaba Cloud Instance. |
July 2024
|
Type |
Key Content |
References |
|
New feature |
Added support for synchronizing or migrating MySQL data to the Lindorm Table engine of Lindorm instances. |
|
|
New feature |
Added support for synchronizing or migrating MongoDB data to AnalyticDB for MySQL 3.0 clusters. |
|
|
New feature |
Two-way synchronization instances now support the Exactly-Once write feature. This helps you accurately synchronize full and incremental data from tables without primary keys or UNIQUE constraints to destination tables. |
Synchronize tables without primary keys and UNIQUE constraints |
|
New feature |
Two-way synchronization instances between MySQL databases and between PolarDB for MySQL instances support setting independent conflict resolution policies for incremental synchronization tasks. |
|
|
New feature |
For synchronization or migration instances with SQL Server as the source, the SQL Server Incremental Synchronization Mode for incremental tasks now supports Polling and querying CDC instances for incremental synchronization. |
|
|
Optimization |
Added support for connecting to SQL Server and MongoDB database instances with Secure Sockets Layer (SSL) encryption enabled. |
June 2024
|
Type |
Key Content |
References |
|
New feature |
Data synchronization or migration instances between MySQL, PolarDB for MySQL, or MariaDB support the add additional columns feature. |
|
|
Optimization |
Connecting to PostgreSQL database instances with Secure Sockets Layer (SSL) encryption enabled is now supported. |
April 2024
|
Type |
Key Content |
References |
|
New feature |
Instances with MySQL or PolarDB for MySQL clusters as source databases and PolarDB for MySQL clusters as destination databases support synchronizing or migrating accounts and permissions from the source database. |
|
|
New feature |
Synchronizing or migrating MongoDB data to AnalyticDB for PostgreSQL is now supported. |
|
|
Optimization |
The target PolarDB for MySQL cluster supports cross-Alibaba Cloud account operations. |
March 2024
|
Type |
Key Content |
References |
|
New feature |
PostgreSQL 16 is now supported. |
|
|
New feature |
One-click creation of reverse incremental synchronization instances for one-way synchronization instances between MySQL databases is now supported. |
|
|
New feature |
Secondary nodes of Cluster Edition ApsaraDB RDS for MySQL instances can now be used as source databases. |
Create instances with Cluster Edition ApsaraDB RDS for MySQL secondary nodes as source databases |
February 2024
|
Type |
Key Content |
References |
|
New feature |
Source databases support Tair (Enterprise Edition) instances with ESSD storage media. |
January 2024
|
Type |
Key Content |
References |
|
New specification |
Highly elastic, fully managed, and low-cost Serverless instances are now available. These instances automatically adjust resources based on changing business demands. |
|
|
New feature |
Synchronizing or migrating PolarDB for MySQL cluster data to SelectDB is now supported to meet your massive data analytics needs. |
|
|
New feature |
SQL Server 2022 and Redis 7.0 are now supported. |
|
|
Optimization |
When a self-managed MongoDB source connects to DTS via Express Connect, VPN Gateway, or Smart Access Gateway, Public IP Address, or Cloud Enterprise Network (CEN), select the Architecture. If the source database is a sharded cluster architecture self-managed MongoDB, select Sharded Cluster as the Architecture. This eliminates the need to create a task for each shard node. |