Data Transmission Service (DTS) provides the data verification feature to help you detect inconsistent data between the source and destination databases at the earliest opportunity without interrupting the services of DTS.

Benefits

  • Both full data and incremental data can be verified without interrupting the services of DTS.
  • Data verification is supported for heterogeneous databases.
  • Full data verification checks the row-level data of the source and destination databases. Incremental data verification checks whether the incremental data is consistent between the source and destination databases.
  • If inconsistent data is detected, DTS verifies the relevant data again after a certain period to check whether the consistency is caused by incremental migration or synchronization latency.

Billing

The data verification feature is in public preview during which you can use it for free.
Important When the public preview ends, the instances that are running will be charged. The end of the public preview will be notified in advance by announcements and text messages.

Supported regions

  • Full data verification: All regions and cross-region tasks are supported. For more information about the supported regions, see Supported regions.
  • Incremental data verification: The China (Hangzhou), China (Shanghai), China (Qingdao), China (Beijing), and China (Zhangjiakou) regions are supported. The instances used for cross-region tasks are not supported.

Supported instances

  • Full data verification:
    • DTS instances that are used to synchronize or migrate data and whose source or destination database is an ApsaraDB for MySQL instance, an AnalyticDB for MySQL instance, a PolarDB for MySQL cluster, an ApsaraDB RDS for SQL Server instance, an ApsaraDB RDS for PostgreSQL instance, an AnalyticDB for PostgreSQL instance, a PolarDB for PostgreSQL cluster, or a self-managed Oracle database.
    • DTS instances that are used to synchronize or migrate data between ApsaraDB for MongoDB instances.
    • DTS instances that are used to synchronize or migrate data between ApsaraDB for Redis Enhanced Edition (Tair) and Redis databases.
    • DTS instances that are used to synchronize or migrate data from a self-managed Oracle database to a PolarDB for Oracle cluster.
    • DTS instances that are used to synchronize or migrate data from a Db2 for i (AS/400) database to a MySQL instance.
  • Incremental data verification:
    • DTS instances that are used to synchronize or migrate data and whose source or destination database is an ApsaraDB for MySQL instance, an AnalyticDB for MySQL instance, a PolarDB for MySQL cluster, an ApsaraDB RDS for SQL Server instance, an ApsaraDB RDS for PostgreSQL instance, an AnalyticDB for PostgreSQL instance, or a PolarDB for PostgreSQL cluster.
    • DTS instances that are used to migrate data from a self-managed Oracle database to an ApsaraDB RDS for MySQL instance, an AnalyticDB for MySQL instance, a PolarDB for MySQL cluster, or a PolarDB for Oracle cluster.
    • DTS instances that are used to synchronize data from a self-managed Oracle database to a PolarDB for Oracle cluster.
Note
  • Data verification is supported in the two-way data synchronization tasks between the preceding source and destination databases.
  • The preceding source and destination databases support Alibaba Cloud instances and self-managed database instances.

References