All Products
Search
Document Center

Data Transmission Service:Ikhtisar database yang didukung

Last Updated:Sep 15, 2026

DTS mendukung transmisi data antara sumber data RDBMS, NoSQL, dan OLAP, termasuk migrasi data, sinkronisasi data, dan pelacakan perubahan.

Catatan
  • Untuk informasi lebih lanjut mengenai istilah seperti jenis migrasi, jenis sinkronisasi, dan jenis data pelacakan perubahan, lihat Istilah.

  • Tugas cross-region didukung untuk semua tautan data kecuali ketika tujuannya adalah Function Compute (FC).

  • Untuk tautan data di mana sumber atau tujuannya adalah database RDS for MySQL, instans Serverless ApsaraDB RDS for MySQL didukung. Untuk tautan data di mana sumber atau tujuannya adalah database RDS for PostgreSQL, instans Serverless ApsaraDB RDS for PostgreSQL hanya didukung sebagai tujuan. Instans Serverless ApsaraMQ for Kafka tidak didukung.

  • Dukungan tugas cross-account bergantung pada jenis database dan jenis koneksi. Jika didukung, opsi Replicate Data Across Alibaba Cloud Accounts akan muncul saat Anda mengonfigurasi instans sumber atau tujuan. Atur ke Yes untuk membuat tugas cross-account. Konfigurasikan tugas lintas Akun Alibaba Cloud.

  • DTS dapat mengakses instans ApsaraDB for MyBase. Atur Access Method ke Alibaba Cloud Instance, lalu ikuti petunjuk yang relevan dalam tabel di bawah ini.

Sinkronisasi data

Sinkronisasi data mereplikasi data antar sumber secara real time. Kasus penggunaan tipikal meliputi redundansi geo-aktif, pemulihan bencana geo, pemulihan bencana data on-premises, sinkronisasi lintas batas, offloading kueri dan laporan, intelijen bisnis (BI) cloud, serta gudang data real-time.

Tabel-tabel berikut dan Ikhtisar solusi sinkronisasi data mencantumkan database, versi, dan jenis sinkronisasi yang didukung.

Catatan

Jika jenis database sumber Anda tidak tersedia dalam daftar Database Type untuk fitur sinkronisasi data DTS, Anda dapat menggunakan fitur pengiriman data. Untuk informasi lebih lanjut, lihat Pengiriman data.

MySQL yang dikelola sendiri atau RDS for MySQL

Penting
  • Database dalam PolarDB-X 1.0 harus dibuat berdasarkan instans ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat berdasarkan PolarDB for MySQL.

  • Jika tujuannya adalah instans PolarDB-X 1.0, sinkronisasi skema dan inisialisasi skema tidak didukung. Jika tujuannya adalah instans PolarDB-X 2.0, keduanya didukung.

  • Kami menyarankan menggunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk informasi lebih lanjut, lihat Lihat dan upgrade versi mesin instans PolarDB for Xscale.

Source database

Destination database

Synchronization type

Synchronization topology

References

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

  • ApsaraDB RDS for MySQL

    All versions

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

Oracle (RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, or 19c

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to a self-managed Oracle database

PolarDB-X 1.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to PolarDB-X 1.0

PolarDB-X 2.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to PolarDB-X 2.0

AnalyticDB for MySQL

Versions 2.0 or 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

  • PostgreSQL yang dikelola sendiri

    Versi 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, atau 18.x

  • ApsaraDB RDS for PostgreSQL

    Versi 9.4, 10, 11, 12, 13, 14, 15, 16, 17, atau 18

sinkronisasi skema

sinkronisasi data penuh

sinkronisasi data inkremental

sinkronisasi satu arah

Synchronize ApsaraDB RDS for MySQL to ApsaraDB RDS for PostgreSQL

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, or 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to AnalyticDB for PostgreSQL

  • ApsaraMQ for Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for Kafka

ApsaraDB for ClickHouse

Version 20.8 or later

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for MySQL to ApsaraDB for ClickHouse

DataHub

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to DataHub

Elasticsearch

Versions 5.5, 5.6, 6.x, 7.x, or 8.x

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to Elasticsearch

MaxCompute

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to MaxCompute

Tair

Versions 4.0, 5.0, 6.0, or 7.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for MySQL to Tair

Tablestore

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to Tablestore

Function Compute

Version 2.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to Function Compute

ApsaraDB for SelectDB

migrasi skema

full data synchronization

incremental data synchronization

Migrasikan data dari ApsaraDB RDS for MySQL ke ApsaraDB for SelectDB

Synchronize ApsaraDB RDS for MySQL to ApsaraDB for SelectDB

ApsaraDB for Lindorm

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to ApsaraDB for Lindorm

Doris

Version 1.2 or later

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for MySQL to a self-managed Doris database

Message Queue for Apache RocketMQ

4.x and 5.x series

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize ApsaraDB RDS for MySQL to ApsaraMQ for RocketMQ

Source: PolarDB for MySQL

Penting
  • Database dalam PolarDB-X 1.0 harus dibuat berdasarkan instans ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat berdasarkan PolarDB for MySQL.

  • Jika tujuannya adalah instans PolarDB-X 1.0, sinkronisasi skema dan inisialisasi skema tidak didukung. Jika tujuannya adalah instans PolarDB-X 2.0, keduanya didukung.

  • Kami menyarankan menggunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk informasi lebih lanjut, lihat Lihat dan upgrade versi mesin instans PolarDB for Xscale.

Source database

Destination database

Type

Topology

Documentation

PolarDB for MySQL

All versions

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

  • self-managed MySQL

    Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

Synchronize data from PolarDB for MySQL to ApsaraDB RDS for MySQL

PolarDB-X 1.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to PolarDB-X 1.0

PolarDB-X 2.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to PolarDB-X 2.0

AnalyticDB for MySQL

Version 2.0 or 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to AnalyticDB for PostgreSQL

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to Message Queue for Apache Kafka

DataHub

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to DataHub

ApsaraDB for ClickHouse

Version 20.8 or later

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to ApsaraDB for ClickHouse

Elasticsearch

Version 5.5, 5.6, 6.x, 7.x, or 8.x

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to Elasticsearch

MaxCompute

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to MaxCompute

Oracle (RAC or non-RAC)

Version 9i, 10g, 11g, 12c, 18c, or 19c

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to a self-managed Oracle

ApsaraDB for SelectDB

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to ApsaraDB for SelectDB

Doris

Version 1.2 or later

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to a self-managed Doris

ApsaraDB for Lindorm

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from PolarDB for MySQL to ApsaraDB for Lindorm

Source: PolarDB for PostgreSQL

Source

Destination

Synchronization type

Topology

Documentation

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

  • self-managed PostgreSQL database

    Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronizing PolarDB for PostgreSQL to AnalyticDB for PostgreSQL

Alibaba Cloud SelectDB

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronizing PolarDB for PostgreSQL to Alibaba Cloud SelectDB

PolarDB-X as the source

Penting
  • Database dalam PolarDB-X 1.0 harus dibuat berdasarkan instans ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat berdasarkan PolarDB for MySQL.

  • Jika tujuannya adalah instans PolarDB-X 1.0, sinkronisasi skema dan inisialisasi skema tidak didukung. Jika tujuannya adalah instans PolarDB-X 2.0, keduanya didukung.

  • Kami menyarankan menggunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk informasi lebih lanjut, lihat Lihat dan upgrade versi mesin instans PolarDB for Xscale.

Source database

Destination database

Synchronization type

Synchronization topology

References

PolarDB-X 1.0

PolarDB-X 1.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data between PolarDB-X 1.0 instances

  • self-managed MySQL

    Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

  • RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to an RDS for MySQL instance

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to a PolarDB for MySQL cluster

AnalyticDB for MySQL

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to AnalyticDB for MySQL 3.0

DataHub

schema synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to a DataHub project

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to an AnalyticDB for PostgreSQL instance

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to Message Queue for Apache Kafka

Elasticsearch

Version 5.5, 5.6, 6.x, 7.x, or 8.x

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to an Elasticsearch cluster

PolarDB-X 2.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 1.0 instance to a PolarDB-X 2.0 instance

PolarDB-X 2.0

PolarDB-X 2.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

  • self-managed MySQL

    Version 5.1, 5.5, 5.6, 5.7, 8.0, or 8.4

  • RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to an RDS for MySQL instance

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a PolarDB for MySQL cluster

AnalyticDB for MySQL

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to AnalyticDB for MySQL 3.0

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to Message Queue for Apache Kafka

DataHub

schema synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a DataHub project

MaxCompute

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a MaxCompute project

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to an AnalyticDB for PostgreSQL instance

Elasticsearch

Version 5.5, 5.6, 6.x, 7.x, or 8.x

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to an Elasticsearch cluster

Oracle (RAC or non-RAC architecture)

Version 9i, 10g, 11g, 12c, 18c, or 19c

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Migrasi dari PolarDB-X 1.0 ke AnalyticDB for PostgreSQL

Tablestore

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a Tablestore instance

PolarDB-X 1.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to a PolarDB-X 1.0 instance

Alibaba Cloud SelectDB

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB-X 2.0 instance to an Alibaba Cloud SelectDB instance

PolarDB for PostgreSQL (Compatible with Oracle) as a source

Source database

Destination database

Synchronization type

Synchronization topology

Documentation

PolarDB for PostgreSQL (Compatible with Oracle) cluster

All versions

PolarDB for PostgreSQL (Compatible with Oracle) cluster

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

two-way synchronization

  • Message Queue for Kafka

    Versions 0.10.1.0–2.x

  • self-managed Kafka cluster

    Versions 0.10.1.0–2.7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to Message Queue for Kafka

AnalyticDB for MySQL cluster

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a PolarDB for PostgreSQL (Compatible with Oracle) cluster to AnalyticDB for MySQL 3.0

Source: Oracle

Penting

Source database

Destination database

Synchronization type

Synchronization topology

References

Self-managed Oracle database (RAC or non-RAC)

Version 9i, 10g, 11g, 12c, 18c, or 19c

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to AnalyticDB for PostgreSQL

DataHub

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to DataHub

PolarDB-X 2.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to PolarDB-X 2.0

PolarDB for MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to PolarDB for MySQL

MaxCompute

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to MaxCompute

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to PolarDB for PostgreSQL (Compatible with Oracle)

ApsaraMQ for Kafka

Versions 0.10.1.0 to 2.x

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a self-managed Oracle database to ApsaraMQ for Kafka

Source: self-managed PostgreSQL or RDS for PostgreSQL

Penting

Instans RDS for PostgreSQL serverless dapat digunakan sebagai database tujuan, tetapi tidak sebagai database sumber.

Source database

Destination database

Synchronization type

Synchronization topology

References

  • self-managed PostgreSQL

    Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

  • self-managed PostgreSQL

    Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Two-way synchronization

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize RDS for PostgreSQL to AnalyticDB for PostgreSQL

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • RDS for MySQL

    All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize RDS for PostgreSQL to RDS for MySQL

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize self-managed PostgreSQL to PolarDB for PostgreSQL (Compatible with Oracle)

SelectDB

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize RDS for PostgreSQL to SelectDB

Source: Self-managed or ApsaraDB RDS for SQL Server

Penting
  • SQL Server yang dikelola sendiri sebagai sumber harus merupakan salah satu edisi berikut: Enterprise, Developer, Enterprise Evaluation, Standard, atau Web.

  • SQL Server yang dikelola sendiri sebagai tujuan harus merupakan salah satu edisi berikut: Enterprise, Developer, Enterprise Evaluation, Standard, atau Web.

  • Kluster SQL Server dan grup ketersediaan Always On SQL Server didukung.

  • Jika database sumber adalah Azure SQL Database, atur parameter SQL Server Incremental Synchronization Mode ke Polling and querying CDC instances for incremental synchronization.

  • Database sumber berikut tidak didukung: SQL Server yang dikelola sendiri versi 2005 dan ApsaraDB RDS for SQL Server versi 2008 atau 2008 R2.

  • Dalam mode parsing log hibrid, di mana SQL Server Incremental Synchronization Mode diatur ke Log-based Parsing for Non-heap Tables and CDC-based Incremental Synchronization for Heap Tables (Hybrid Log-based Parsing), database sumber berikut didukung:

    • Edisi Enterprise atau Enterprise Evaluation: 2012, 2014, 2016, 2019, 2022, atau 2025.

    • Edisi Standard: 2016, 2019, 2022, atau 2025.

  • Jika database sumber adalah edisi Web SQL Server, parameter SQL Server Incremental Synchronization Mode hanya dapat diatur ke Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

Source

Destination

Sync type

Topology

Guide

  • Self-managed SQL Server

    Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • ApsaraDB RDS for SQL Server

    Versions 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • Self-managed SQL Server

    Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • ApsaraDB RDS for SQL Server

    Versions 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data between ApsaraDB RDS for SQL Server instances

  • Self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for SQL Server to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a self-managed SQL Server to PolarDB for MySQL

AnalyticDB for MySQL

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for SQL Server to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

ApsaraDB RDS for PostgreSQL

Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from a self-managed SQL Server to ApsaraDB RDS for PostgreSQL

DataHub

schema synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for SQL Server to DataHub

Source: MariaDB

Source

Destination

Sync type

Topology

Documentation

  • RDS for MariaDB

    • 10.x

  • A self-managed MariaDB database

    • 10.x, 11.0–11.4

  • ApsaraDB RDS for MariaDB

  • A self-managed MariaDB database

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

ApsaraDB RDS for MySQL

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for MySQL

ApsaraDB RDS for PostgreSQL

Versions 9.4, 10, 11, 12, 13, 14, 15, and 16

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from ApsaraDB RDS for MariaDB to ApsaraDB RDS for PostgreSQL

Source: Self-managed or Alibaba Cloud MongoDB

Source

Destination

Sync type

Topology

Guide

Replica set architecture

  • self-managed MongoDB

    Versi 3.0 hingga 7.0

  • Alibaba Cloud MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

Replica set or sharded cluster architecture

  • self-managed MongoDB

    Versions 3.0 to 8.0

  • Alibaba Cloud MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize a replica set to a replica set or sharded cluster

Sharded cluster architecture

  • self-managed MongoDB

    Versions 3.0 to 8.0

  • Alibaba Cloud MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

Replica set or sharded cluster architecture

  • self-managed MongoDB

    Versions 3.0 to 8.0

  • Alibaba Cloud MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize a sharded cluster to a replica set or sharded cluster

Alibaba Cloud MongoDB (sharded cluster architecture)

Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

Alibaba Cloud MongoDB (sharded cluster architecture)

Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

schema synchronization

full data synchronization

incremental data synchronization

two-way synchronization

Two-way synchronization between Alibaba Cloud MongoDB sharded clusters

Alibaba Cloud MongoDB (replica set architecture)

Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

Alibaba Cloud MongoDB (replica set architecture)

Versions 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

schema synchronization

full data synchronization

incremental data synchronization

two-way synchronization

Two-way synchronization between Alibaba Cloud MongoDB replica sets

Replica set or sharded cluster architecture

  • self-managed MongoDB

    Versions 3.0 to 8.0

  • Alibaba Cloud MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0

Function Compute

Version 2.0

incremental data synchronization

one-way synchronization

Lindorm

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to Lindorm

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to AnalyticDB for PostgreSQL

AnalyticDB for MySQL 3.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to AnalyticDB for MySQL 3.0

  • Database MySQL swakelola

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS untuk MySQL

    All versions

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to Alibaba Cloud RDS for MySQL

PolarDB for MySQL

All versions

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to PolarDB for MySQL

  • ApsaraMQ for Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize MongoDB to Message Queue for Apache Kafka

Source: Self-managed Redis or Tair (Redis OSS-Compatible)

Penting
  • Redis adalah database NoSQL dan tidak memerlukan sinkronisasi skema.

  • Hanya sinkronisasi dua arah antar instans Tair (Enterprise Edition) yang didukung.

  • Ketika database sumber adalah Redis yang dikelola sendiri atau instans Tair (Redis OSS-Compatible), sinkronisasi data penuh dan sinkronisasi data inkremental didukung dan ditampilkan bersama sebagai Incremental Data Synchronization.

  • Mendukung versi RDB hingga 11, yang sesuai dengan Redis 7.2.

Source database

Destination database

Type

Topology

References

  • Self-managed Redis (standalone or cluster architecture)

    Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2

  • Tair (Redis OSS-Compatible) instance (cluster, standard, or read/write splitting architecture)

    Versions 4.0, 5.0, 6.0, and 7.0

  • Self-managed Redis (standalone or cluster architecture)

    Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2

  • Tair (Redis OSS-Compatible) instance (cluster, standard, or read/write splitting architecture)

    Versions 4.0, 5.0, 6.0, and 7.0

Full data synchronization

Incremental data synchronization

One-way synchronization

Tair (Redis OSS-Compatible) Enterprise Edition instance (cluster, standard, or read/write splitting architecture)

Tair (Redis OSS-Compatible) Enterprise Edition instance (cluster, standard, or read/write splitting architecture)

Full data synchronization

Incremental data synchronization

Two-way synchronization

Source: TiDB

Source database

Destination database

Synchronization type

Synchronization topology

Documentation

TiDB

AnalyticDB for MySQL cluster

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize a self-managed TiDB database to an AnalyticDB for MySQL V3.0 cluster

PolarDB-X 2.0 instance

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Coming soon

Source: Db2 for LUW

Penting
  • Db2 for LUW ditampilkan sebagai DB2 for LUW di konsol.

  • Instans tujuan PolarDB-X 2.0 harus versi 5.4.11 atau yang lebih baru. Untuk instruksi upgrade, lihat Lihat dan upgrade versi instans.

Source database

Destination database

Synchronization type

Synchronization topology

Configuration document

Db2 for LUW

Versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5

  • Self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • RDS for MySQL

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from Db2 for LUW to an RDS for MySQL instance

PolarDB for MySQL

All versions

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from Db2 for LUW to a PolarDB for MySQL cluster

PolarDB-X 2.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from Db2 for LUW to a PolarDB-X 2.0 instance

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from Db2 for LUW to an AnalyticDB for PostgreSQL instance

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • Self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize data from Db2 for LUW to a self-managed Kafka cluster

Source: Db2 for i (AS/400)

Penting

Konsol menampilkan Db2 for i sebagai DB2 for iSeries (AS/400).

Source database

Destination database

Synchronization type

Synchronization topology

Documentation

Db2 for i

Versions 7.3 and 7.4

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Available soon

PolarDB for MySQL

All versions

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Available soon

Source: AnalyticDB for MySQL 3.0

Penting

Cluster sumber AnalyticDB for MySQL 3.0 harus menjalankan versi kernel 3.2.1.0 atau yang lebih baru.

Source database

Destination database

Synchronization type

Synchronization topology

Configuration guide

AnalyticDB for MySQL

Version 3.0

AnalyticDB for MySQL

Version 3.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize data from AnalyticDB for MySQL 3.0 to AnalyticDB for MySQL 3.0

Source: AnalyticDB for PostgreSQL

Penting

Instans sumber AnalyticDB for PostgreSQL memerlukan versi kernel 7.2.1.4 atau yang lebih baru.

Source

Destination

Type

Topology

Document

AnalyticDB for PostgreSQL

Version 7.0

AnalyticDB for PostgreSQL

Version 7.0

schema synchronization

full data synchronization

incremental data synchronization

one-way synchronization

Data Synchronization Between AnalyticDB for PostgreSQL Instances

AnalyticDB for PostgreSQL

Version 7.0

Message Queue for Apache Kafka

Versions 0.10.1.0 to 2.x

full data synchronization

incremental data synchronization

one-way synchronization

Synchronize Data from an AnalyticDB for PostgreSQL Instance to a Message Queue for Apache Kafka Instance

DMS logical database as a source

Penting

Database logis DMS harus dibuat dari shard beberapa kluster PolarDB for MySQL.

Source database

Destination database

Synchronization type

Synchronization topology

Configuration document

DMS logical database

AnalyticDB for MySQL

Version 3.0

Schema synchronization

Full data synchronization

Incremental data synchronization

One-way synchronization

Synchronize a DMS logical database to AnalyticDB for MySQL 3.0

Source: AWS database

Source database

Destination database

Synchronization type

Synchronization topology

Configuration document

AWS database

Lihat Konsol.

Use DTS to synchronize data between ApsaraDB RDS and Amazon EC2 over a VPN gateway

Migrasi data

Migrasi data memindahkan data antara sumber homogen atau heterogen. Kasus penggunaan tipikal meliputi migrasi ke cloud, migrasi antar instans, serta sharding dan scale-out database.

Untuk informasi tentang database, versi, jenis migrasi, dan dokumen konfigurasi yang didukung, lihat tabel-tabel berikut atau Skema migrasi.

Migrasi dari MySQL yang dikelola sendiri atau RDS for MySQL

Penting
  • Database dalam instans PolarDB-X 1.0 harus dibangun di atas ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibangun di atas PolarDB for MySQL.

  • DTS mendukung migrasi skema ke instans PolarDB-X 2.0, tetapi tidak ke instans PolarDB-X 1.0.

  • Kami menyarankan menggunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk instruksi cara upgrade instans, lihat Lihat dan update versi mesin instans PolarDB for Xscale.

  • Konsol baru tidak mendukung migrasi ke AnalyticDB for MySQL 2.0. Gunakan konsol sebelumnya untuk tugas ini.

Source

Destination

Type

References

  • Self-managed MySQL database

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

  • Self-managed MySQL database

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

PolarDB-X 1.0

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to PolarDB-X 1.0

PolarDB-X 2.0

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to PolarDB-X 2.0

AnalyticDB for MySQL

Versions 2.0 and 3.0

schema migration

full data migration

incremental data migration

Migrate from ApsaraDB RDS for MySQL to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate from ApsaraDB RDS for MySQL to AnalyticDB for PostgreSQL

  • Self-managed PostgreSQL database

    Versions 9.4.8 or later, including 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to ApsaraDB RDS for PostgreSQL

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • Self-managed Kafka cluster

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to Message Queue for Apache Kafka

ApsaraDB for ClickHouse

Version 20.8 or later

schema migration

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to ApsaraDB for ClickHouse

DataHub

All versions

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to DataHub

Alibaba Cloud Elasticsearch

Versions 5.5, 5.6, 6.x, 7.x, and 8.x

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to Alibaba Cloud Elasticsearch

MaxCompute

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to MaxCompute

Self-managed Oracle database (in a RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

schema migration

full data migration

incremental data migration

Migrate from ApsaraDB RDS for MySQL to a self-managed Oracle database

Tair (cluster, standard, or read/write splitting architecture)

Versions 4.0, 5.0, 6.0, and 7.0

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to Tair/Redis

Tablestore

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for MySQL to Tablestore

ApsaraDB for SelectDB

schema migration

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to ApsaraDB for SelectDB

Lindorm

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to Lindorm

Doris

Version 1.2 or later

schema migration

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to a self-managed Doris database

Message Queue for Apache RocketMQ

4.x and 5.x series

full data migration

incremental data migration

Migrate data from ApsaraDB RDS for MySQL to Message Queue for Apache RocketMQ

Skema migrasi untuk sumber MariaDB

Source database

Destination database

Migration type

Configuration document

  • RDS for MariaDB

    • 10.x

  • self-managed MariaDB

    • 10.x, 11.0–11.4

  • RDS for MariaDB

  • self-managed MariaDB

schema migration

full data migration

incremental data migration

RDS for MySQL

schema migration

full data migration

incremental data migration

Migrate from RDS for MariaDB to RDS for MySQL

RDS for PostgreSQL

Versions 9.4 and 10–18

schema migration

full data migration

incremental data migration

Migrate from RDS for MariaDB to RDS for PostgreSQL

Migrasi dari ApsaraDB RDS for PPAS

Source database

Destination database

Migration type

Documentation

ApsaraDB RDS for PPAS

All versions

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

Schema migration

Full data migration

Incremental data migration

Migrate data from ApsaraDB RDS for PPAS to PolarDB for PostgreSQL (Compatible with Oracle)

Migrasi dari PolarDB for MySQL

Penting
  • Database dalam instans PolarDB-X 1.0 harus berbasis ApsaraDB RDS for MySQL. DTS tidak mendukung jenis instans ini jika databasenya berbasis PolarDB for MySQL.

  • Migrasi skema tidak didukung untuk instans PolarDB-X 1.0 tetapi didukung untuk instans PolarDB-X 2.0.

  • Gunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk instruksi upgrade, lihat Lihat dan update versi mesin instans PolarDB for Xscale.

Source

Destination

Migration type

Documentation

PolarDB for MySQL cluster

All versions

PolarDB for MySQL cluster

All versions

Schema migration

Full data migration

Incremental data migration

Migrate between PolarDB for MySQL clusters

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an ApsaraDB RDS for MySQL instance

PolarDB-X 1.0 instance

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 1.0 instance

PolarDB-X 2.0 instance

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a PolarDB-X 2.0 instance

AnalyticDB for MySQL cluster

Version 3.0

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster

AnalyticDB for PostgreSQL instance

Versions 4.3, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an AnalyticDB for PostgreSQL instance

  • ApsaraMQ for Kafka instance

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka cluster

    Versions 0.10.1.0 to 2.7.0

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to Kafka

DataHub project

All versions

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a DataHub project

ApsaraDB for ClickHouse cluster

Version 20.8 or later

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for ClickHouse cluster

self-managed Oracle database (RAC, PDB, or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a self-managed Oracle database

Elasticsearch cluster

Versions 5.5, 5.6, 6.x, 7.x, and 8.x

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an Elasticsearch cluster

MaxCompute project

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a MaxCompute project

ApsaraDB for SelectDB instance

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to an ApsaraDB for SelectDB instance

Doris database

Version 1.2 or later

Schema migration

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a self-managed Doris database

Lindorm instance

Full data migration

Incremental data migration

Migrate data from a PolarDB for MySQL cluster to a Lindorm instance

Migrasi dari PolarDB for PostgreSQL (Compatible with Oracle)

Source

Destination

Type

Documentation

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

schema migration

full data migration

incremental data migration

Migrate data between PolarDB for PostgreSQL (Compatible with Oracle) instances

self-managed Oracle database (RAC, PDB, or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, or 19c

full data migration

incremental data migration

Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to a self-managed Oracle database

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka cluster

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate data from PolarDB for PostgreSQL (Compatible with Oracle) to Message Queue for Apache Kafka

AnalyticDB for MySQL

version 3.0

migrasi skema

Migrasi data penuh

migrasi data inkremental

Migrasikan data dari PolarDB for PostgreSQL (Compatible with Oracle) ke AnalyticDB for MySQL

Migrasi dari PolarDB-X

Penting
  • Anda hanya dapat mengonfigurasi skenario migrasi ini di konsol DTS baru.

  • Database dalam instans PolarDB-X 1.0 harus dibuat di atas ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat berdasarkan PolarDB for MySQL.

  • Kami menyarankan menggunakan PolarDB-X 2.0 versi 5.4.11 atau yang lebih baru. Untuk instruksi upgrade, lihat Lihat dan upgrade versi instans.

Source

Destination

Migration type

Documentation

PolarDB-X 1.0

PolarDB-X 2.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to PolarDB-X 2.0

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to AnalyticDB for PostgreSQL

DataHub

schema migration

incremental data migration

Migrate PolarDB-X 1.0 to DataHub

Elasticsearch

Versions 5.5, 5.6, 6.x, 7.x, and 8.x

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to Elasticsearch

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to Message Queue for Apache Kafka

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 1.0 to ApsaraDB RDS for MySQL

PolarDB-X 2.0

PolarDB-X 2.0

schema migration

full data migration

incremental data migration

Migrate data between PolarDB-X 2.0 instances

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to PolarDB for MySQL

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to AnalyticDB for PostgreSQL

MaxCompute

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to MaxCompute

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to Message Queue for Apache Kafka

DataHub

All versions

schema migration

incremental data migration

Migrate from PolarDB-X 2.0 to DataHub

Elasticsearch

Versions 5.5, 5.6, 6.x, 7.x, and 8.x

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to Elasticsearch

self-managed Oracle (RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to a self-managed Oracle database

Tablestore

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to Tablestore

PolarDB-X 1.0

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to PolarDB-X 1.0

ApsaraDB for SelectDB

schema migration

full data migration

incremental data migration

Migrate from PolarDB-X 2.0 to ApsaraDB for SelectDB

Migrasi dari PolarDB for PostgreSQL

Source database

Destination database

Migration type

Documentation

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

Schema migration

Full data migration

Incremental data migration

Migrate data between PolarDB for PostgreSQL clusters

  • Self-managed PostgreSQL

    Versions 9.5.x, 9.6.x, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

Schema migration

Full data migration

Incremental data migration

Migrate data from PolarDB for PostgreSQL to ApsaraDB RDS for PostgreSQL

Self-managed Oracle (RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

Full data migration

Incremental data migration

Migrate data from PolarDB for PostgreSQL to self-managed Oracle

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate data from PolarDB for PostgreSQL to AnalyticDB for PostgreSQL

ApsaraDB for SelectDB

Schema migration

Full data migration

Incremental data migration

Migrate data from PolarDB for PostgreSQL to ApsaraDB for SelectDB

Skema migrasi dari MaxCompute

Source

Destination

Type

Documentation

MaxCompute

All versions

  • Self-managed MySQL database

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

Schema migration

Full data migration

Migrate data from MaxCompute to ApsaraDB RDS for MySQL

Migrasi dari OceanBase (mode MySQL)

Source database

Destination database

Migration type

Documentation

  • ApsaraDB for OceanBase

    cluster and tenant instances (MySQL mode)

  • OceanBase (MySQL mode)

    Community Edition

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrating from OceanBase (MySQL mode) to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrating from OceanBase (MySQL mode) to PolarDB for MySQL

Lindorm

full data migration

incremental data migration

Migrating from OceanBase (MySQL mode) to Lindorm

Skema migrasi sumber Oracle

Penting
  • Database dalam instans PolarDB-X 1.0 harus berbasis instans RDS for MySQL. DTS tidak mendukung database berbasis kluster PolarDB for MySQL.

  • Migrasi skema tidak didukung untuk instans PolarDB-X 1.0, tetapi didukung untuk instans PolarDB-X 2.0.

  • Instans PolarDB-X 2.0 Anda harus versi 5.4.11 atau yang lebih baru. Untuk instruksi upgrade, lihat Lihat dan upgrade versi mesin instans PolarDB for Xscale.

Source

Destination

Migration type

References

self-managed Oracle (RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

schema migration

full data migration

incremental data migration

self-managed Oracle (RAC or non-RAC architecture)

Versions 9i, 10g, 11g, 12c, 18c, and 19c

schema migration

full data migration

incremental data migration

Migration between self-managed Oracle databases

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to RDS for MySQL

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to PolarDB for MySQL

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to PolarDB for PostgreSQL

PolarDB-X 1.0 and 2.0

full data migration

incremental data migration

Migrate a self-managed Oracle database to PolarDB-X 2.0

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to AnalyticDB for PostgreSQL

  • self-managed PostgreSQL

    Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

  • RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

schema migration

full data migration

incremental data migration

  • Alibaba Cloud Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to Alibaba Cloud Message Queue for Apache Kafka

DataHub

All versions

schema migration

full data migration

incremental data migration

Migrate a self-managed Oracle database to DataHub

Migrasi dari sumber PostgreSQL

Penting

ApsaraDB RDS for PostgreSQL Serverless hanya didukung sebagai database tujuan, bukan sebagai database sumber.

Source

Destination

Type

References

  • self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, or 18.x

  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18

  • self-managed PostgreSQL database

    Version 9.4.8 or later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, or 18.x

  • ApsaraDB RDS for PostgreSQL

    Version 9.4, 10, 11, 12, 13, 14, 15, 16, 17, or 18

schema migration

full data migration

incremental data migration

PolarDB for PostgreSQL

Version 11, 14, 15, 16, 17, or 18

schema migration

full data migration

incremental data migration

Migrate a self-managed PostgreSQL database to a PolarDB for PostgreSQL cluster

  • self-managed MySQL database

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for PostgreSQL to ApsaraDB RDS for MySQL

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

schema migration

full data migration

incremental data migration

Migrate a self-managed PostgreSQL database to PolarDB for PostgreSQL (Compatible with Oracle)

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

schema migration

full data migration

incremental data migration

Migrate a self-managed PostgreSQL database to AnalyticDB for PostgreSQL

ApsaraDB for SelectDB

schema migration

full data migration

incremental data migration

Migrate ApsaraDB RDS for PostgreSQL to ApsaraDB for SelectDB

Migrasi dari SQL Server yang dikelola sendiri atau RDS

Penting
  • SQL Server yang dikelola sendiri sebagai sumber harus merupakan salah satu edisi berikut: Enterprise, Developer, Enterprise Evaluation, Standard, atau Web.

  • SQL Server yang dikelola sendiri sebagai tujuan harus merupakan salah satu edisi berikut: Enterprise, Developer, Enterprise Evaluation, Standard, atau Web.

  • Migrasi data inkremental tidak didukung jika SQL Server yang dikelola sendiri sebagai sumber adalah versi 2005, atau jika RDS for SQL Server sebagai sumber adalah versi 2008 atau 2008 R2.

  • Jika database sumber adalah Azure SQL Database, atur parameter SQL Server Incremental Synchronization Mode ke Polling and querying CDC instances for incremental synchronization.

  • Kluster SQL Server dan grup ketersediaan Always On SQL Server didukung.

  • Dalam mode parsing log hibrid (ketika parameter SQL Server Incremental Synchronization Mode diatur ke log-based parsing for non-heap tables and CDC-based incremental synchronization for heap tables), mode ini mendukung database sumber berikut (termasuk RDS for SQL Server dan SQL Server yang dikelola sendiri):

    • Enterprise atau Enterprise Evaluation: 2012, 2014, 2016, 2019, 2022, atau 2025.

    • Standard: 2016, 2019, 2022, atau 2025.

  • Jika database sumber adalah edisi Web SQL Server, parameter SQL Server Incremental Synchronization Mode hanya mendukung Incremental Synchronization Based on Logs of Source Database (Heap tables are not supported).

Source

Destination

Migration type

Documentation

  • self-managed SQL Server

    Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • RDS for SQL Server

    Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • self-managed SQL Server

    Versions 2005, 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

  • RDS for SQL Server

    Versions 2008, 2008 R2, 2012, 2014, 2016, 2017, 2019, 2022, or 2025

schema migration

full data migration

incremental data migration

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate from RDS for SQL Server to RDS for MySQL

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrate from RDS for SQL Server to PolarDB for MySQL

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

incremental data migration

Migrate from RDS for SQL Server to AnalyticDB for MySQL 3.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate from a self-managed SQL Server to AnalyticDB for PostgreSQL

RDS for PostgreSQL

Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

schema migration

full data migration

incremental data migration

Migrate from a self-managed SQL Server to RDS for PostgreSQL

DataHub

schema migration

incremental data migration

Migrate from RDS for SQL Server to DataHub

Migrasi dari MongoDB yang dikelola sendiri atau ApsaraDB for MongoDB

Source database

Destination database

Migration type

Configuration document

Standalone architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Version 3.4 or 4.0

Standalone, replica set, or sharded cluster architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Migrate a standalone ApsaraDB for MongoDB instance to an ApsaraDB for MongoDB instance of any architecture

Replica set architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Replica set or sharded cluster architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate a replica set ApsaraDB for MongoDB instance to a replica set or sharded cluster ApsaraDB for MongoDB instance

Sharded cluster architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Replica set or sharded cluster architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Schema migration

Full data migration

Incremental data migration

Migrate a self-managed sharded cluster MongoDB database to a replica set or sharded cluster ApsaraDB for MongoDB instance

Replica set or sharded cluster architecture

  • Self-managed MongoDB database

    Versions 3.0 to 7.0

  • ApsaraDB for MongoDB

    Versions 3.4, 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0

Lindorm

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to Lindorm

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to AnalyticDB for PostgreSQL

AnalyticDB for MySQL 3.0

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to AnalyticDB for MySQL 3.0

  • Self-managed MySQL database

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

Full data migration

Incremental data migration

Migrate data from ApsaraDB for MongoDB to PolarDB for MySQL

  • Message Queue for Apache Kafka

    Versions 0.10.1.0 to 2.x

  • Self-managed Kafka cluster

    Versions 0.10.1.0 to 2.7.0

Full data migration

Incremental data migration

Synchronize data from ApsaraDB for MongoDB to Message Queue for Apache Kafka

Migrasi dari Redis atau ApsaraDB for Tair

Penting
  • Redis adalah database NoSQL dan tidak memerlukan migrasi skema.

  • Jika database sumber adalah instans Redis yang dikelola sendiri atau instans ApsaraDB for Tair (Redis-compatible), migrasi data penuh dan migrasi data inkremental didukung. Jenis migrasi ini ditampilkan sebagai Incremental Data Migration.

  • Mendukung versi RDB hingga 11, yang sesuai dengan Redis 7.2.

Source database

Destination database

Migration type

Guide

  • self-managed Redis (standalone or cluster architecture)

    Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2

  • ApsaraDB for Tair (Redis-compatible) instance (cluster, standard, or read/write splitting architecture)

    Versions 4.0, 5.0, 6.0, and 7.0

  • self-managed Redis (standalone or cluster architecture)

    Versions 2.8, 3.0, 3.2, 4.0, 5.0, 6.0, 7.0, and 7.2

  • ApsaraDB for Tair (Redis-compatible) instance (cluster, standard, or read/write splitting architecture)

    Versions 4.0, 5.0, 6.0, and 7.0

Full data migration

Incremental data migration

TiDB sebagai sumber migrasi

Source database

Destination database

Migration type

References

TiDB

  • self-managed MySQL

    5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate data from self-managed TiDB to ApsaraDB RDS for MySQL

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrate data from self-managed TiDB to PolarDB for MySQL

PolarDB-X 2.0

schema migration

full data migration

incremental data migration

Documentation coming soon.

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

incremental data migration

Migrate data from self-managed TiDB to AnalyticDB for MySQL 3.0

Migrasi dari Db2 for LUW

Penting

Source database

Destination database

Migration type

References

Db2 for LUW

Versions 9.5, 9.7, 10.1, 10.5, 11.1, and 11.5

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • RDS for MySQL

    All versions

schema migration

full data migration

incremental data migration

Migrate from Db2 for LUW to RDS for MySQL

PolarDB-X 2.0

full data migration

incremental data migration

Migrate from Db2 for LUW to PolarDB-X 2.0

AnalyticDB for PostgreSQL

Versions 4.3, 6.0, and 7.0

schema migration

full data migration

incremental data migration

Migrate from Db2 for LUW to AnalyticDB for PostgreSQL

  • Message Queue for Kafka

    Versions 0.10.1.0 to 2.x

  • self-managed Kafka

    Versions 0.10.1.0 to 2.7.0

schema migration

full data migration

incremental data migration

Migrate from Db2 for LUW to Message Queue for Kafka

PolarDB for MySQL

All versions

schema migration

full data migration

incremental data migration

Migrate from Db2 for LUW to PolarDB for MySQL

Migrasi Db2 for i (AS/400)

Penting

Di konsol, Db2 for i ditampilkan sebagai DB2 iSeries(AS/400).

Source database

Destination database

Migration type

Documentation

Db2 for i

Versions 7.3 and 7.4

  • Self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

Schema migration

Full data migration

Incremental data migration

Available soon

PolarDB for MySQL

All versions

Schema migration

Full data migration

Incremental data migration

Available soon

Migrasi dari Teradata

Penting

Tugas ini hanya dapat dikonfigurasi di konsol baru. Instans migrasi data harus berada di wilayah China (Shanghai), China (Qingdao), atau China (Zhangjiakou).

Source database

Destination database

Migration type

Configuration document

Teradata

Version 17 or earlier

AnalyticDB for PostgreSQL

Version 4.3, 6.0, or 7.0

Schema migration

Full data migration

Migrate data from Teradata to AnalyticDB for PostgreSQL

Migrasi dari HBase yang dikelola sendiri

Penting

Migrasi ini hanya dapat dikonfigurasi di konsol baru.

Source

Destination

Type

Documentation

self-managed HBase

Version 1.x

AnalyticDB for MySQL

Version 3.0

schema migration

full data migration

Migrate data from a self-managed HBase instance to AnalyticDB for MySQL V3.0

Migrasi dari AnalyticDB for MySQL V3.0

Catatan

Migrasi data inkremental memerlukan kluster sumber AnalyticDB for MySQL V3.0 memiliki versi kernel 3.2.1.0 atau yang lebih baru.

Source

Target

Type

Documentation

AnalyticDB for MySQL

V3.0

AnalyticDB for MySQL

V3.0

schema migration

full data migration

incremental data migration

Migrate data between AnalyticDB for MySQL V3.0 clusters

Migrasi dari AnalyticDB for PostgreSQL

Catatan

Untuk migrasi data inkremental, instans sumber AnalyticDB for PostgreSQL harus memiliki versi kernel 7.2.1.4 atau yang lebih baru.

Source database

Target database

Migration type

References

AnalyticDB for PostgreSQL

Version 7.0

AnalyticDB for PostgreSQL

Version 7.0

schema migration

full data migration

incremental data migration

Migrating data between AnalyticDB for PostgreSQL instances

Migrasi dari cloud pihak ketiga

Data Transmission Service (DTS) melakukan migrasi data dari cloud pihak ketiga, seperti Amazon RDS for MySQL dan Amazon RDS for Oracle, ke produk Alibaba Cloud seperti ApsaraDB RDS for MySQL.

Source database

Destination database

Type

References

Databases on Microsoft Azure

See the console.

Connect an Azure VNet to an Alibaba Cloud VPC

Amazon RDS for MySQL

ApsaraDB RDS for MySQL

schema migration

full data migration

incremental data migration

Migrate data from Amazon RDS for MySQL to ApsaraDB RDS for MySQL

Amazon RDS for Oracle

ApsaraDB RDS for MySQL

schema migration

full data migration

incremental data migration

Migrate data from Amazon RDS for Oracle to ApsaraDB RDS for MySQL

Amazon RDS for PostgreSQL

ApsaraDB RDS for PostgreSQL

schema migration

full data migration

incremental data migration

Incrementally migrate data from Amazon RDS for PostgreSQL to ApsaraDB RDS for PostgreSQL

schema migration

full data migration

Fully migrate data from Amazon RDS for PostgreSQL to ApsaraDB RDS for PostgreSQL

Amazon RDS for SQL Server

ApsaraDB RDS for SQL Server

schema migration

full data migration

Fully migrate data from Amazon RDS for SQL Server to ApsaraDB RDS for SQL Server

Amazon Aurora MySQL

ApsaraDB RDS for MySQL

schema migration

full data migration

incremental data migration

Migrate data from Amazon Aurora MySQL to ApsaraDB RDS for MySQL

PolarDB for MySQL

schema migration

full data migration

incremental data migration

Migrate data from Amazon Aurora MySQL to PolarDB for MySQL

Amazon Aurora PostgreSQL

ApsaraDB RDS for PostgreSQL

schema migration

full data migration

Migrate data from Amazon Aurora PostgreSQL to ApsaraDB RDS for PostgreSQL

MongoDB Atlas

ApsaraDB for MongoDB

full data migration

incremental data migration

Migrate data from MongoDB Atlas to ApsaraDB for MongoDB

Catatan
  • Migrasi data dapat menggantikan sinkronisasi data dalam beberapa skenario, tetapi keduanya berbeda dalam hal skenario, database yang didukung, fitur, dan penagihan. Apa perbedaan antara migrasi data dan sinkronisasi data?

  • Untuk migrasi data inkremental jangka panjang, gunakan sinkronisasi data, yang menyediakan stabilitas jaringan yang lebih baik dan fitur yang lebih lengkap.

Pelacakan perubahan

Pelacakan perubahan mengambil data inkremental real-time dari database seperti MySQL yang dikelola sendiri dan RDS for MySQL. Kasus penggunaan meliputi pembaruan cache, penguraian keterkaitan asinkron, sinkronisasi lintas sumber, dan proses ETL kompleks. Anda dapat mengonsumsi data yang dilacak melalui SDK, Flink, atau klien lainnya. Untuk informasi tentang solusi pelacakan perubahan yang didukung dan dokumen konfigurasi, lihat tabel berikut atau Rencana pelacakan perubahan.

Source database

Supported types

Documentation

  • self-managed MySQL

    Versions 5.1, 5.5, 5.6, 5.7, 8.0, and 8.4

  • ApsaraDB RDS for MySQL

    All versions

  • data update

  • schema update

Track data changes from an ApsaraDB RDS for MySQL instance

PolarDB for MySQL

All versions

  • data update

  • schema update

Create a PolarDB for MySQL change tracking task

PolarDB-X 1.0

Penting

Database dasar untuk PolarDB-X harus berbasis ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat di atas PolarDB for MySQL.

  • data update

  • schema update

Create a PolarDB-X 1.0 change tracking task

PolarDB-X 2.0

Penting

Database dasar untuk PolarDB-X harus berbasis ApsaraDB RDS for MySQL. DTS tidak mendukung database yang dibuat di atas PolarDB for MySQL.

  • data update

  • schema update

Create a PolarDB-X 2.0 change tracking task

PolarDB for PostgreSQL (Compatible with Oracle)

All versions

data update

Create a change tracking task for PolarDB for PostgreSQL (Compatible with Oracle)

self-managed Oracle (non-RAC architecture)

Versions 9i, 10g, and 11g

  • data update

  • schema update

Create an Oracle change tracking task

  • ApsaraDB RDS for PostgreSQL

    Versions 9.4, 10, 11, 12, 13, 14, 15, 16, 17, and 18

  • self-managed PostgreSQL

    Versions 9.4.8 and later, 9.5, 9.6, 10.x, 11.x, 12.x, 13.x, 14.x, 15.x, 16.x, 17.x, and 18.x

data update

Create an RDS PostgreSQL Change Tracking task

Data Management (DMS) logical database

Penting

Database logis harus terdiri dari shard database dari beberapa instans PolarDB for MySQL.

data update

Create a DMS logical database change tracking task

PolarDB for PostgreSQL

Versions 11, 14, 15, 16, 17, and 18

  • data update

  • schema update

Create a change tracking task for PolarDB for PostgreSQL