Data Replication
NineData Data Replication helps you synchronize schema and data between two data sources by combining schema replication, full data replication, and incremental data replication.
Overview
Use this page to create a standard data replication task. The available replication phases and supported capabilities depend on the selected source and target data sources, so review the support tables before you create the task.
- One-Way Replication
- Bidirectional Replication
| Source Database | Target Database | Schema Repl. | Full Repl. | Incre Repl. | Schema Comp. | Data Comp. | Incre Comp. |
|---|---|---|---|---|---|---|---|
| MySQL | MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| MySQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| MySQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB MySQL-compatible | MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB MySQL-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB MySQL-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL-C MySQL | MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL-C MySQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL-C MySQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| MySQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Elasticsearch | ✔️ | ✔️ | ✔️ | - | - | - |
| PolarDB MySQL-compatible | Elasticsearch | ✔️ | ✔️ | ✔️ | - | - | - |
| TDSQL-C MySQL | Elasticsearch | ✔️ | ✔️ | ✔️ | - | - | - |
| MySQL | Kafka | - | ✔️ | ✔️ | - | - | - |
| PolarDB MySQL-compatible | Kafka | - | ✔️ | ✔️ | - | - | - |
| TDSQL-C MySQL | Kafka | - | ✔️ | ✔️ | - | - | - |
| MySQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Redshift | - | ✔️ | ✔️ | - | - | - |
| PolarDB MySQL-compatible | Redshift | - | ✔️ | ✔️ | - | - | - |
| TDSQL-C MySQL | Redshift | - | ✔️ | ✔️ | - | - | - |
| MySQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | SingleStore | - | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | SingleStore | - | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | SingleStore | - | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | Hive | ✔️ | ✔️ | - | - | ✔️ | - |
| PolarDB MySQL-compatible | Hive | ✔️ | ✔️ | - | - | ✔️ | - |
| TDSQL-C MySQL | Hive | ✔️ | ✔️ | - | - | ✔️ | - |
| MySQL | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | - | - |
| PolarDB MySQL-compatible | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | - | - |
| TDSQL-C MySQL | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | - | - |
| MySQL | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | ShardingJDBC | - | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | ShardingJDBC | - | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | ShardingJDBC | - | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB MySQL-compatible | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL-C MySQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| MySQL | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB MySQL-compatible | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL-C MySQL | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| MySQL | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MySQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB MySQL-compatible | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL-C MySQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | SQL Server | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| SQL Server | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Kafka | - | ✔️ | ✔️ | - | - | - |
| SQL Server | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Azure SQL Database | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SQL Server | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PostgreSQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PostgreSQL | PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PostgreSQL | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PolarDB PostgreSQL-compatible | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Kafka | - | ✔️ | ✔️ | - | - | - |
| PostgreSQL | Kafka | - | ✔️ | ✔️ | - | - | - |
| PolarDB PostgreSQL-compatible | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TDSQL Centralized PostgreSQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| PostgreSQL | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Sybase | - | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Sybase | - | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB PostgreSQL-compatible | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PostgreSQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized PostgreSQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | Oracle | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Oracle | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Kafka | - | ✔️ | ✔️ | - | - | - |
| Oracle | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| Oracle | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Oracle | GoldenDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| OceanBase Oracle | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| OceanBase Oracle | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| OceanBase Oracle | OceanBase Oracle | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| OceanBase Oracle | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| OceanBase Oracle | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | Kafka | - | ✔️ | ✔️ | - | - | - |
| OceanBase Oracle | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| OceanBase Oracle | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase Oracle | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| OceanBase MySQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | Kafka | - | ✔️ | ✔️ | - | - | - |
| OceanBase MySQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| OceanBase MySQL | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| TDSQL Centralized MySQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | Kafka | - | ✔️ | ✔️ | - | - | - |
| TDSQL Centralized MySQL | DWS | ✔️ | ✔️ | ✔️ | - | - | - |
| TDSQL Centralized MySQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | AnalyticDB PostgreSQL | ✔️ | ✔️ | ✔️ | - | - | - |
| TDSQL Centralized MySQL | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TDSQL Centralized MySQL | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | Kafka | - | ✔️ | ✔️ | - | - | - |
| Db2 | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Db2 | GoldenDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| MongoDB | MongoDB | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| Redis | Redis | - | ✔️ | ✔️ | - | ✔️ | - |
| Doris | MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | PolarDB MySQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | SQL Server | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | OceanBase Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | OceanBase MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Db2 | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Doris | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | ClickHouse | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Dameng | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Greenplum | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | StarRocks | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | TiDB | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | openGauss MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | openGauss Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | openGauss PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | KingbaseES Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | PolarDB Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Doris | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Doris | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SelectDB | MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | PolarDB MySQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | SelectDB (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | ClickHouse | ✔️ | ✔️ | - | - | ✔️ | - |
| SelectDB | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| SelectDB | StarRocks | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | PolarDB MySQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | SQL Server | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | OceanBase Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | OceanBase MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Db2 | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Doris | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | ClickHouse | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Dameng | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Greenplum | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | StarRocks | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | TiDB | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | openGauss MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | openGauss Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | openGauss PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | KingbaseES Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | PolarDB Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| ClickHouse | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| ClickHouse | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | Dameng | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Dameng | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Dameng | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| DWS (no datasource) | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Greenplum | MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | PolarDB MySQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | SQL Server | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | OceanBase Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | OceanBase MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Db2 | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Doris | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | ClickHouse | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Dameng | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Greenplum | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | StarRocks | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | TiDB | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | PolarDB Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| Greenplum | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Greenplum | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| StarRocks | MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | PolarDB MySQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | SQL Server | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | OceanBase Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | OceanBase MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | TDSQL Centralized MySQL (no datasource) | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Db2 | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Doris | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | ClickHouse | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Dameng | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Greenplum | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | StarRocks | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | TiDB | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | openGauss MySQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | openGauss Oracle | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | openGauss PostgreSQL | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | KingbaseES Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | PolarDB Oracle-compatible | ✔️ | ✔️ | - | - | ✔️ | - |
| StarRocks | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| StarRocks | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| TiDB | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | TiDB | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| TiDB | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | PolarDB-X 2.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| TiDB | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Sybase | PostgreSQL | - | ✔️ | ✔️ | - | ✔️ | - |
| Sybase | TDSQL Centralized PostgreSQL | - | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized Oracle-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized PostgreSQL-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized MySQL (B/M compatible) | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | Kafka | - | ✔️ | ✔️ | - | - | - |
| GaussDB Centralized Oracle-compatible | Kafka | - | ✔️ | ✔️ | - | - | - |
| GaussDB Centralized PostgreSQL-compatible | Kafka | - | ✔️ | ✔️ | - | - | - |
| GaussDB Centralized MySQL (B/M compatible) | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | DWS | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized MySQL (B/M compatible) | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized MySQL (B/M compatible) | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized Oracle-compatible | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized Oracle-compatible | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized Oracle-compatible | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized PostgreSQL-compatible | GaussDB Centralized MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized PostgreSQL-compatible | GaussDB Centralized Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized PostgreSQL-compatible | GaussDB Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | ✔️ |
| GaussDB Centralized MySQL (B/M compatible) | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized MySQL (B/M compatible) | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized Oracle-compatible | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GaussDB Centralized PostgreSQL-compatible | DataHub | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss MySQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss MySQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss Oracle | openGauss MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss Oracle | openGauss Oracle | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss Oracle | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss PostgreSQL | openGauss MySQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss PostgreSQL | openGauss Oracle | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss PostgreSQL | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| openGauss MySQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss MySQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss Oracle | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| openGauss PostgreSQL | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | Kafka | ✔️ | ✔️ | ✔️ | - | - | - |
| KingbaseES PostgreSQL-compatible | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| KingbaseES PostgreSQL-compatible | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES PostgreSQL-compatible | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | SelectDB (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Kafka | ✔️ | ✔️ | ✔️ | - | - | - |
| KingbaseES Oracle-compatible | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | KingbaseES PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | KingbaseES Oracle-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| KingbaseES Oracle-compatible | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| KingbaseES Oracle-compatible | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | TDSQL-C MySQL (no datasource) | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Doris | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | ClickHouse | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Dameng | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Greenplum | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | openGauss MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | openGauss Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | openGauss PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| PolarDB Oracle-compatible | Vastbase G100 PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB Oracle-compatible | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB-X 2.0 Distributed | PolarDB-X 1.0 Distributed | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| PolarDB-X 1.0 Distributed | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | - | - | - |
| PolarDB-X 2.0 Centralized | PolarDB-X 2.0 Centralized | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Azure SQL Database | SQL Server | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Azure SQL Database | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Azure SQL Database | PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Azure SQL Database | TDSQL Centralized PostgreSQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Azure SQL Database | Azure SQL Database | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | - |
| Vastbase G100 Oracle | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 PostgreSQL | MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 PostgreSQL | PolarDB MySQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | PolarDB PostgreSQL-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 PostgreSQL | OceanBase Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | OceanBase MySQL | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | StarRocks | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | TiDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | PolarDB Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Vastbase G100 Oracle | Vastbase G100 Oracle-compatible | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GoldenDB | Oracle | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GoldenDB | Db2 | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| GoldenDB | GoldenDB | ✔️ | ✔️ | ✔️ | - | ✔️ | - |
| Source Database | Target Database | Schema Repl. | Full Repl. | Incre Repl. |
|---|---|---|---|---|
| MySQL | MySQL | ✔️ | ✔️ | ✔️ |
| Oracle | ✔️ | ✔️ | ✔️ | |
| OceanBase Oracle | ✔️ | ✔️ | ✔️ | |
| OceanBase MySQL | ✔️ | ✔️ | ✔️ | |
| TDSQL MySQL | ✔️ | ✔️ | ✔️ | |
| PolarDB-X | ✔️ | ✔️ | ✔️ | |
| SQL Server | SQL Server | ✔️ | ✔️ | ✔️ |
| Azure SQL Database | ✔️ | ✔️ | ✔️ | |
| PostgreSQL | PostgreSQL | ✔️ | ✔️ | ✔️ |
| Oracle | MySQL | ✔️ | ✔️ | ✔️ |
| PolarDB-X | ✔️ | ✔️ | ✔️ | |
| OceanBase Oracle | OceanBase Oracle | ✔️ | ✔️ | ✔️ |
| OceanBase MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ |
| PolarDB-X | ✔️ | ✔️ | ✔️ | |
| TDSQL MySQL | OceanBase MySQL | ✔️ | ✔️ | ✔️ |
| PolarDB-X | ✔️ | ✔️ | ✔️ | |
| Redis | Redis | - | ✔️ | ✔️ |
| TiDB | PolarDB-X | ✔️ | ✔️ | ✔️ |
| Sybase | PostgreSQL | - | ✔️ | ✔️ |
| PolarDB-X | PolarDB-X | ✔️ | ✔️ | ✔️ |
| Azure SQL Database | SQL Server | ✔️ | ✔️ | ✔️ |
| Azure SQL Database | ✔️ | ✔️ | ✔️ |
A complete one-way data replication workflow can include the following phases:
- Schema replication: Synchronizes database and table structures from the source data source to the target data source.
- Full data replication: Synchronizes existing data from the source data source to the target data source.
- Incremental data replication: Synchronizes ongoing source-side data changes to the target database in real time.
After replication completes, verify data and schema compatibility on the target data source. If verification passes, switch application traffic or downstream workloads to the target data source.
Run these phases together or separately based on your business requirements. For example, run only schema replication, only full data replication, or only incremental data replication.
Bidirectional replication adds reverse incremental replication from the target data source back to the source data source.
Link capability notes
- When a relational database replicates to Kafka, the delivery format can be Canal JSON or Avro. Avro delivery requires a Confluent Schema Registry endpoint and, when applicable, its authentication credentials.
- YashanDB can be used as a target for schema and full replication from relational sources such as MySQL, Oracle, PostgreSQL, and SQL Server. Incremental availability depends on the replication types displayed for the selected link. When YashanDB is the source, schema and full replication are currently supported, but incremental replication is not.
- For Oracle-source incremental replication, the writer resolves conflicts between dependent rows and adjusts the write order, reducing write failures caused by dependencies such as foreign keys.
- For SQL Server sources, incremental DDL replication can convert
TRUNCATE TABLE. - Oracle-to-TiDB and TiDB-to-Oracle incremental DDL replication can convert
COMMENTsyntax. - PostgreSQL-to-GaussDB replication supports column type mapping.
- A replication task that has reached a terminal state cannot be started again, preventing a terminated task from running again and causing inconsistent data.
- Oracle-to-PolarDB Oracle schema and incremental replication support Materialized View Log objects.
- When row-level logical merge by primary key is disabled, table-batch writing can group and write
INSERT,UPDATE, andDELETEoperations concurrently by operation type while preserving intermediate DML for downstream subscribers. - SQL Server metadata retrieval filters a broader set of system tables to avoid subscribing to system-table changes.
- Incremental replication tasks that involve Kafka periodically check Kafka server connectivity. If the server is unavailable, use the error displayed in the replication task details to check the Kafka address, network, and authentication settings.
- Data Replication prechecks check object-configuration conflicts in unfinished replication tasks, including replication loops and multiple tasks that replicate the same table.
- After you create a bidirectional replication task, starting the forward task does not depend on the reverse task having started. If the precheck reports an object-configuration conflict, resolve the conflicting task as instructed before starting.
- PostgreSQL incremental replication supports parsing and replicating
COMMENT ON CONSTRAINTstatements. - When GaussDB is the source, incremental replication supports
CREATEandDROPDDL for non-table objects such asprocedure,function, andsequence.
tip
Schema replication and incremental data replication cannot be selected together unless full data replication is also selected.
Before you begin
Add the source and target data sources to NineData. For details, see Add a Data Source.
For bidirectional replication, keep the source and target database versions consistent when possible.
If the task does not include schema replication, make sure the target data source already contains the table structures to be replicated.
When MySQL is the source, enable Binlog and set the following Binlog parameters:
binlog_format=ROWbinlog_row_image=FULLtipIf the source data source is a standby database, enable
log_slave_updatesso NineData can obtain the complete Binlog.
Restrictions
- Data replication applies only to user databases in the data source. System databases are not replicated. For example, MySQL system databases such as
information_schema,mysql,performance_schema, andsysare not replicated. - The source account must have
SELECTprivileges for schema and full data replication,SHOW VIEWprivileges for view replication, andREPLICATION CLIENTandREPLICATION SLAVEprivileges for incremental replication. The target account must have DML and DDL privileges. - Before starting data synchronization, evaluate the performance of the source and target data sources. Run synchronization during off-peak hours when possible. Otherwise, full data initialization consumes read and write resources on both data sources and increases database load.
- If the source data source contains views, functions, stored procedures, triggers, or events, the definer information of these objects is changed on the target data source to the account used by the current synchronization task to access the target data source.
- Make sure every table in the synchronization objects has a primary key or unique constraint, and that column names are unique. Otherwise, duplicate rows may be synchronized.
- If triggers exist in the source data source, NineData synchronizes the triggers only after incremental synchronization ends.
Procedure
Sign in to the NineData Console.
In the left navigation pane, click Replication > Data Replication.
On the Replication page, click Create Replication.
On the Source & Target tab, configure the fields in the table, and click Next.
Parameter Description Name Enter a name for the data synchronization task. To make the task easier to find and manage later, use a meaningful name. Up to 64 characters are supported. Source The data source that contains the objects to synchronize. Datahub Project Select the target Datahub Project. Data from the source data source will be written to the specified Project. Target Object Name Select the case conversion rule for object names after they are migrated from the source to the target. - Convert all to Lowercase: Regardless of the naming rule on the source, all target names are lowercase.
- Consistent with Source: Keep the naming rule of the source.
- Convert all to Uppercase: Regardless of the naming rule on the source, all target names are uppercase.
Replication Mode Select the replication mode. - Uni-directional: A unidirectional data replication task from the source data source to the target data source.
- Bi-directional: A bidirectional incremental data replication task between the source and target data sources.
Type Required when Replication Mode is Bi-directional.Select the replication type. - Schema: Synchronize only the database and table schemas of the source data source, without synchronizing data.
- Full: Synchronize all objects and data from the source data source, namely full data replication. The switch on the right enables periodic full replication. For more information, see Periodic Full Replication.
- Incremental: After full synchronization completes, perform incremental synchronization based on the logs of the source data source.The
icon is used to configure incremental operation types. Clear the operation types to exclude. Cleared operation types will be ignored during incremental synchronization.
Forward Type Required when Replication Mode is Bi-directional. Select the forward replication type. - Schema: Synchronize only the database and table schemas of the source data source, without synchronizing data.
- Full: Synchronize all objects and data from the source data source, namely full data replication.
- Incremental: After full synchronization completes, perform incremental synchronization based on the logs of the source data source.The icon is used to configure incremental operation types. Clear the operation types to exclude. Cleared operation types will be ignored during incremental synchronization.
Incremental Started Required only when Type is Incremental. - From Started: Use the current replication task start time as the baseline for incremental replication.
- Customized Time: Select the point in time from which incremental replication starts. Select a time zone based on the region of your business. If the configured time point is earlier than the current replication task start time and DDL operations occurred during that period, the replication task will fail.
Forward Incremental Started Required only when Forward Type is Incremental. - From Started: Use the current replication task start time as the baseline for incremental replication.
- Customized Time: Select the point in time from which incremental replication starts. Select a time zone based on the region of your business. If the configured time point is earlier than the current replication task start time and DDL operations occurred during that period, the replication task will fail.
Reverse Type The replication type from the target data source to the source data source. This parameter is displayed only when Replication Mode is Bi-directional. Only Incremental is supported, and it is selected by default and cannot be disabled. Spec The specification of the replication task. A larger specification provides a higher replication rate. Hover over the 
icon to view the rate and configuration information of each specification. If you configure the data replication task before purchasing resources, you can select the required specification here. If you purchase resources before configuring the task, NineData selects the specification specified during purchase, and you cannot change it in the task configuration.If target table already exists (Required when Schema is selected) - Pre-Check Error and Stop Task: Stop the task when a table with the same name is detected during the precheck stage.
- Skip and Continue Task: When a table with the same name is detected during the precheck stage, display a message and continue the task. During schema replication, ignore the table with the same name. If you also perform data replication, data is appended to the table with the same name and existing data is not overwritten.
- Delete Objects and Rewrite: When a table with the same name is detected during the precheck stage, display a message and continue the task. During schema replication, delete the table with the same name in the target database and replicate the table schema again based on the source database. If you also perform data replication, data is written after schema replication completes.
Target Table Exists Data (Required when Full is selected) - Pre-Check Error and Stop Task: Stop the task when data is detected in the target table during the precheck stage.
- Ignore existing target data and append to it.: When data is detected in the target table during the precheck stage, ignore that data and append other data.
- Clear target existing data before write: When data is detected in the target table during the precheck stage, delete that data and write it again.
Incremental data conflict handling strategy for target table (Required when Incremental is selected) - Runtime error: During incremental replication, report an error when target data already exists and wait for manual intervention.
- Do not update target data: During incremental replication, do not write data when target data already exists, and continue subsequent tasks.
- Update target data: During incremental replication, overwrite the target data when target data already exists.
On the Objects tab, configure the parameters in the table, and click Next.
Parameter Description Replication Objects Select the content to replicate. Select All Objects to replicate all content in the source database, or select Customized Object, select the content to replicate in the Source Object list, and click > to add it to the Target Object list on the right. Blacklist Click Add to add a blacklist record, and select the database or object to add to the blacklist. The selected content will not be replicated. This is used to exclude specific databases or objects when performing full-database replication for Customized Object or Full Instance. - Left drop-down list: Select the database name to add to the blacklist.
- Right drop-down list: Select objects in the corresponding database. Select multiple objects if required. Leave it empty to add the entire database to the blacklist.
To create multiple replication tasks with the same replication objects, import a configuration file. Click Import Config, click Download Template to download the template, edit the file, and then click Upload to upload it and import the objects in bulk. For field descriptions and examples, see Import Replication Object Templates. The configuration file uses these fields:
Parameter Description Example source_table_nameThe exact source table name of the object to synchronize. example_tbl_nametarget_table_nameThe target table name that receives the synchronized object. example_tbl_namesource_database_nameThe source database name of the object to synchronize. test_dbtarget_database_nameThe target database name that receives the synchronized object. test_db_bakcolumn_listThe list of columns to synchronize. ["col1", "clo2", "col3"]extra_configurationA JSON string containing additional configuration. Use column_rulesfor column mappings and value rules:column_nameis the source column,target_column_nameis the target column,target_column_typeis the target column type, andcolumn_valueis the column value. Usefilter_conditionfor row-level filtering.{"extra_config": {"column_rules": [...]}}tipThe following JSON represents the two example rows in the downloaded Excel template. When uploading the file, keep the Excel column names and enter the
extra_configurationvalue as a JSON string. This code block is not a JSON file that you can upload directly.[
{
"source_table_name": "example_tbl_name",
"target_table_name": "example_tbl_name",
"source_database_name": "test_db",
"target_database_name": "test_db_bak",
"column_list": ["col1", "clo2", "col3"],
"extra_configuration": {
"extra_config": {
"column_rules": [
{
"column_name": "example_column_name",
"target_column_name": "example_target_column_name",
"target_column_type": "int",
"column_value": "current_timestamp()"
},
{
"column_name": "example_column_name",
"target_column_name": "example_target_column_name",
"target_column_type": "int"
}
],
"filter_condition": "example_condition_expression"
}
}
},
{
"source_table_name": "example_order_tbl",
"target_table_name": "example_order_tbl",
"source_database_name": "test_db",
"target_database_name": "test_db_bak",
"column_list": ["col1", "clo2", "col3"],
"extra_configuration": {
"extra_config": {
"column_rules": [
{
"column_name": "example_column_name",
"target_column_name": "example_target_column_name",
"target_column_type": "int",
"column_value": "current_timestamp()"
},
{
"column_name": "example_column_name",
"target_column_name": "example_target_column_name",
"target_column_type": "int"
}
],
"filter_condition": "example_condition_expression"
}
}
}
]On the Mapping tab, configure the mapping that matches the selected replication type, then click Save and Pre-Check. If source or target metadata changes while you configure mappings, click Refresh Metadata to refresh the metadata.
Includes Schema: Configure the table name after synchronization to the target data source.
Does not include Schema: NineData selects the database with the same name in the target data source by default. If no such database exists, select the target database manually. The table names and column names in the target database must match the synchronization objects. If they do not match, map the table names and column names manually.
Other available actions:
- Click Mapping & Filtering to customize the column names after synchronization to the target data source.
- On the Mapping & Filtering page, enter a comparison expression in the text box below Data Filter as the filtering condition. Only data that meets the filtering conditions is synchronized to the target data source. For example, if the filtering condition is set to
emp_no>=10005, data whose emp_no column value is less than 10005 is not synchronized to the target data source. - Click the
icon to the right of "Target Table" to search for a table name and replace it with the target name. - Enter a table name in the Search Table text box to quickly locate the target table.
- Click Batch Configuration to define common rules in batches, such as table name and column name case conversion, prefix or suffix addition, and replacement. Use this option to apply mapping configuration to many tables and columns at the same time.
On the Pre-check tab, wait for NineData to complete the precheck. After the precheck passes, click Launch.
Select Enable data consistency comparison to start a data consistency comparison task based on the source data source after synchronization completes. Based on the selected Type, Enable data consistency comparison starts at these times:
- Schema: Starts after schema replication completes.
- Schema+Full: Starts after full replication completes.
- Full: Starts after full replication completes.
- Schema+Full+Incremental, Incremental: Starts when incremental data is consistent with the source data source for the first time and Delay is 0 seconds. Click View Details to view synchronization delay on the Details page.
If the precheck fails, click Details in the Actions column for the failed check item, review the cause, fix the issue, and then click Check Again to run the precheck again until it passes.
Items with Warning in Result can be fixed or ignored if required.
On the Launch page, the Launch Successfully message appears, indicating that the synchronization task has started. Then perform these actions:
- Click View Details to view the execution status of each stage of the synchronization task.
- Click Back to list to return to the Replication task list page.
Modify incremental synchronization positions
For a task whose replication type includes Incremental and whose task details provide position management, you can view and modify synchronization positions. The available position types and input format depend on the data source and replication link. Follow the options displayed for the current task. If a position is shown as - or no position type is available for selection, the current task has no position available for modification.
This feature is intended for specific operations and maintenance scenarios where you need to specify a new log-read position or synchronization-write position for an incremental task. The read position controls where the task continues reading from the source, while the write position controls where it continues processing synchronized writes. After you submit the change, the task pauses and restarts so that the new position can take effect.
In the replication task list, click the Task ID of the target task to open its details.
On the Incremental tab, click Synchronous site management to view the current read site and write site.
Click modify site. Under site type, select the read site or write site to adjust, and then enter the value for Adjustment point according to the position type displayed for the task.
Confirm the value and scope of impact, and click Verify and submit. The task enters a pause and relaunch process. After the task resumes running, open Synchronous site management again to confirm that the position has been updated.
danger
Modifying the synchronization point will adjust the point of log reading or synchronization writing, which may cause data loss, so operate with caution! Modifying either position may cause data loss or inconsistency between the source and target. Perform this operation only in an authorized test environment or during a maintenance window with a backup and rollback plan. A task whose incremental replication has finished cannot have its position reset.
Result
Sign in to the NineData Console.
In the navigation menu, select Replication > Data Replication.
On the Replication page, click the Task ID of the target synchronization task. The task details page shows the following information.
Number Function Description 1 Sync Delay The synchronization delay between the source and target data sources. 0seconds means the target has caught up with the source. Switch traffic based on your migration plan.2 Configure Alerts When the task fails, NineData notifies the selected channel through the configured alert. 3 More - Pause: Pause the task. Only tasks with Running status are selectable.
- Duplicate: Create a new replication task with the same configuration as the current task.
- Terminate: Terminate tasks that are incomplete or still listening (that is, in incremental synchronization). After a task is terminated, it cannot be restarted, so proceed with caution. If the replication objects include triggers or events, the dialog displays termination options for the applicable object type:
- Migrate triggers and terminate or Migrate events and terminate: Migrate the applicable objects to the target data source before terminating the task.
- Do not migrate triggers; terminate immediately or Do not migrate events; terminate immediately: Terminate the task immediately without migrating the applicable objects.
- Delete: Delete the task. Once deleted, it cannot be recovered, so proceed with caution.
4 Structure Replication (displayed in scenarios involving structure replication) Displays the progress and detailed information of structure replication. - Select Log to view the execution logs of structure replication.
- Select the
to view the latest information. - Select View DDL in the Actions column for the target object in the list to view SQL replay.
5 Full Replication (displayed in scenarios involving full replication) Displays the progress and detailed information of full replication. - Select Monitor to view various monitoring indicators during full replication. During full replication, select Flow Control Settings on the monitoring page to limit the rate of writing to the target data source per second. The unit is rows/second.
- Select Log to view the execution logs of full replication.
- Select the to view the latest information.
6 Incremental Replication (displayed in scenarios involving incremental replication) Displays incremental replication indicators. - Select View Threads to view the operations currently being executed by the current replication task, including:
- Thread ID: Replication tasks are executed in multiple threads, and this shows the current thread number.
- Execute SQL: Details of the SQL statement currently being executed by the current thread.
- Response Time: The response time of the current thread. If this value increases, it indicates that the current thread may be stuck for some reason.
- Event Time: The timestamp when the current thread was started.
- Status: The status of the current thread.
- Select Flow Control Settings to limit the rate of writing to the target data source per second. The unit is rows/second.
- Select Log to view the execution logs of incremental replication.
- Select the to view the latest information.
7 Modify Object Displays the modification records of synchronization objects. - Select Modify Objects to configure the synchronization objects.
- Select the to view the latest information.
8 Data Comparison Displays the comparison results between the source and target data sources. If data comparison is not enabled, select Enable Comparison on the page to enable it. - Select Re-compare to rerun the comparison for the current source and target data sources.
- Select Stop to stop the comparison task immediately after it starts.
- Select Log to view the execution logs of consistency comparison.
- Select Monitor (displayed only in data comparison) to view the trend chart of RPS (records per second) comparison. Select Details to view earlier records.
- Select the
in the Actions column in the comparison list (displayed under the Data tab only when inconsistencies are found) to view details of the comparison between the source and target data sources. - Select the
in the Actions column in the comparison list (displayed only when inconsistencies are found): Generate change SQL. Copy this SQL to the target data source and run it to fix the mismatch.
9 Expand Displays detailed information of the current replication task. Common actions: - Export table configuration: Export the current task's database and table configuration for quick import when creating another replication task with the same objects.
- Alert Rules: Configure alerts for the current task.