Billable items and billing rules of DTS - Data Transmission Service

The billable items of Data Transmission Service (DTS) vary based on the type of the DTS instance that you use. This topic describes the billable items and billing rules of DTS.

When you purchase a DTS instance, you are charged based on the billing method, features, and cluster type of the DTS instance, the regions in which the source and destination database instances reside, the quantity of DTS instances that you want to purchase, and the subscription duration. You are not charged based on the amount of data in database instances. For more information, visit the DTS pricing page.

Important

If the source database is a distributed database instance, such as a PolarDB-X instance, a Data Management (DMS) logical database, or a MongoDB database, you are also charged based on the number of nodes of the distributed database instance when you use the data synchronization or data verification feature of DTS.

Instance	Billable item	Billing rule
Data migration instance	Instance usage	Only the pay-as-you-go billing method is supported. You are charged only when incremental data migration is in progress. You are not charged for schema migration or full data migration. Important You are not charged during the period in which incremental data migration is paused or fails. Within the hour before an overdue payment occurs, if you have used an instance for no more than half an hour, you are charged for half an hour of instance usage. If you have used an instance for more than half an hour, you are charged for one hour of instance usage.
Data migration instance	Internet traffic	You are charged Internet traffic fees for the outbound traffic that is generated if you set Access Method to Public IP Address for the destination database in a data migration instance. When you use DTS to migrate data, the following types of traffic may be generated: Outbound traffic: You are charged for outbound traffic. For example, you are charged for the traffic that is generated when you migrate data from a self-managed database on an Elastic Compute Service (ECS) instance or an Alibaba Cloud database to an on-premises database over the Internet. Note You are charged Internet traffic fees based on the actual traffic that is generated. The unit price is USD 0.154 per GB. Traffic of less than 1 GB is charged as 1 GB. Inbound traffic: You are not charged for inbound traffic. For example, you are not charged for the traffic that is generated when you migrate data from an on-premises database to a self-managed database hosted on an ECS instance or an Alibaba Cloud database over the Internet. Traffic within Alibaba Cloud: If you set Access Method to Public IP Address for the destination database in a data migration instance, you are charged for traffic within Alibaba Cloud. In other cases, you are not charged for traffic within Alibaba Cloud.
Data synchronization instance	Instance usage	Pay-as-you-go The billing starts when the Incremental Data Collection module is started after your data synchronization instance passes the precheck and is purchased. You are charged during the period in which incremental data synchronization is paused. Important You are not charged during the period in which incremental data synchronization fails. Within the hour before an overdue payment occurs, if you have used an instance for no more than half an hour, you are charged for half an hour of instance usage. If you have used an instance for more than half an hour, you are charged for one hour of instance usage. Subscription You are charged a one-off fee based on the instance specifications and quantity when you purchase instances.
Change tracking instance	Instance usage	Pay-as-you-go The billing starts after an instance is configured and started. Within the hour before an overdue payment occurs, if you have used an instance for no more than half an hour, you are charged for half an hour of instance usage. If you have used an instance for more than half an hour, you are charged for one hour of instance usage. Subscription You are charged a one-off fee based on the instance specifications and quantity when you purchase instances.
Change tracking instance	Data transfer	The data transfer fees for the traffic that is generated when a client consumes the data that is tracked by a change tracking instance. Free of charge.
Data verification task	Instance usage	For more information, see Billing of data verification tasks.
Dedicated cluster	Cluster specifications, Internet traffic, and storage	For more information, see Billing of DTS dedicated clusters.

FAQ

Why am I still charged for a pay-as-you-go instance that does not transfer data?
When an incremental task is running on a pay-as-you-go DTS instance, you are charged based on the actual resource usage regardless of whether data changes occur in the source database. We recommend that you terminate or release the DTS instance at the earliest opportunity after the data transfer is complete. For more information, see Terminate a DTS instance and Release DTS instances.
How do I delete a DTS instance?
You can delete a DTS instance by releasing the instance. For more information, see Release DTS instances.
Am I charged for a DTS synchronization instance?
Yes, you are charged for a DTS synchronization instance. By default, a synchronization instance includes Incremental Data Synchronization tasks. Therefore, you are charged after the Incremental Data Collection module is started.
Am I charged for schema synchronization and full data synchronization performed by a DTS synchronization instance?
The schema synchronization (Schema Migration in the console) and full data synchronization (Full Data Migration in the console) modules are free of charge. However, when a synchronization instance runs as expected, you are charged for using the Incremental Data Collection module.
Note
By default, a synchronization instance includes the Incremental Data Collection module. This module is used to collect incremental data from the source database and automatically runs after the instance passes the precheck and is purchased. The system continues to run the Schema Migration, Full Data Migration, and Incremental Write modules only after the Incremental Data Collection module is successfully run.