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
The full data, incremental data, and schemas can be verified without interrupting the services of DTS.
The data verification feature 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 specific period of time to check whether the consistency is caused by the latency of incremental data migration or synchronization.
Billing
For more information, see Billing method of data verification.
Supported regions
Data verification is supported in all regions and cross-region scenarios. For more information, see Supported regions.
Supported scenarios
Data verification is supported in two-way synchronization scenarios between the following source and destination databases.
The following source and destination databases support Alibaba Cloud database instances and self-managed database instances.
Data verification mode | Source database type | Destination database type |
Full data verification | MySQL | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, PostgreSQL, AnalyticDB for PostgreSQL, and Oracle |
PolarDB for MySQL | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, AnalyticDB for PostgreSQL, and Oracle | |
PostgreSQL | MySQL, PostgreSQL, AnalyticDB for PostgreSQL, PolarDB for PostgreSQL, Oracle, and PolarDB for Oracle | |
PolarDB for PostgreSQL | MySQL, PostgreSQL, AnalyticDB for PostgreSQL, PolarDB for PostgreSQL, and Oracle | |
Standalone MongoDB databases | Standalone MongoDB databases | |
MongoDB databases that use the replica set architecture | MongoDB databases that use the replica set architecture | |
MongoDB databases that use the sharded cluster architecture | MongoDB databases that use the sharded cluster architecture | |
Tair and Redis databases that use the master-replica architecture | Tair and Redis databases that use the master-replica architecture | |
Tair and Redis databases that use the cluster architecture | Tair and Redis databases that use the cluster architecture | |
SQL Server | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, SQL Server, and AnalyticDB for PostgreSQL | |
Oracle | AnalyticDB for MySQL, AnalyticDB for PostgreSQL, MySQL, PolarDB for MySQL, PolarDB for PostgreSQL, PolarDB for Oracle, PostgreSQL, and Oracle | |
PolarDB for Oracle | PolarDB for Oracle, AnalyticDB for MySQL, and Oracle | |
Db2 for LUW | MySQL, PolarDB for MySQL, AnalyticDB for MySQL, and AnalyticDB for PostgreSQL | |
Db2 for i (AS/400) | MySQL | |
Incremental data verification | MySQL | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, PostgreSQL, AnalyticDB for PostgreSQL, and PolarDB for PostgreSQL |
PolarDB for MySQL cluster | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, and AnalyticDB for PostgreSQL | |
PostgreSQL | MySQL, PostgreSQL, AnalyticDB for PostgreSQL, and PolarDB for PostgreSQL | |
PolarDB for PostgreSQL | PostgreSQL, AnalyticDB for PostgreSQL, and PolarDB for PostgreSQL | |
SQL Server | MySQL, AnalyticDB for MySQL, PolarDB for MySQL, SQL Server, and AnalyticDB for PostgreSQL | |
Oracle | AnalyticDB for MySQL, MySQL, PolarDB for MySQL, and PolarDB for Oracle | |
Schema verification | MySQL | MySQL and PolarDB for MySQL |
PolarDB for MySQL | MySQL and PolarDB for MySQL | |
PostgreSQL | PostgreSQL and PolarDB for PostgreSQL | |
PolarDB for PostgreSQL | PostgreSQL and PolarDB for PostgreSQL |
References
For more information about how to configure a data verification task, see Enable data verification.
For more information about how to view the data verification details, see View data verification details.