The billable items for Data Transmission Service (DTS) vary by task type. This topic describes the billable items and billing rules for DTS.
The price of a DTS instance is determined by factors such as the task type, billing method, cluster type, the regions of the source and destination database instances, the number of links, and the subscription duration. For specific pricing, see DTS Product Pricing, DTS Pay-as-you-go Pricing, and DTS Subscription Pricing.
Important If the source database is a distributed database instance, such as PolarDB-X 1.0, a DMS logical database, a sharded MongoDB cluster, Simple Log Service (SLS), or Tair/Redis, the price of data synchronization and data validation tasks also depends on the number of nodes in the distributed database.
The billing rules for each task type are described below. For detailed pricing information, see Pricing Calculator.
Task type | Billable item | Billing rule |
Data migration | Incremental migration | Data migration tasks support only the pay-as-you-go billing method. The billing rules are as follows: You are charged only when incremental data migration is running. You are not charged for schema migration or full data migration.
Important You are not charged when incremental data migration is paused or has failed. Within the hour before an overdue payment occurs, if you use the instance for 30 minutes or less, you are charged for half an hour. If you use the instance for more than 30 minutes, you are charged for one hour.
|
Internet traffic | Internet traffic fees (outbound traffic fees) are incurred for traffic generated when the Access Method of the destination database instance is set to Public IP Address. The following scenarios apply when you use DTS: Outbound traffic: Charged. For example, traffic generated when you migrate data from a self-managed database on an ECS instance or an ApsaraDB database to an on-premises database over the public network.
Note Internet traffic is billed based on actual usage at USD 0.154 per GB. Usage under 1 GB is billed as 1 GB. Customers in the EU/EEA can request reduced or exempted fees for eligible use cases under the Regulation (EU) 2023/2854 (Data Act). For more information, contact Support and Services.
Inbound traffic: Not charged. For example, traffic generated when you migrate data from an on-premises database to a self-managed database on an ECS instance or an ApsaraDB database over the public network. Traffic within Alibaba Cloud: Charged when the Access Method of the destination database instance is set to Public IP Address. Not charged in other cases.
|
Data synchronization | Standard sync task | Incremental synchronization | Pay-as-you-go Billing starts after the Incremental Data Collection module starts. This means billing begins after the sync task passes the precheck and is purchased. This includes periods when incremental data synchronization is paused.
Important You are not charged when incremental data synchronization fails. Within the hour before an overdue payment occurs, if you use the instance for 30 minutes or less, you are charged for half an hour. If you use the instance for more than 30 minutes, you are charged for one hour. Subscription You are charged a one-time fee based on the selected configuration and quantity at the time of purchase.
Important For subscription tasks that you no longer use, especially those with auto-renewal enabled, manually cancel auto-renewal or release the instance to which the task belongs. This prevents extra charges. For more information, see Manage auto-renewal and Release DTS instances.
|
Serverless task | Resource (DU) usage | Serverless tasks support only the pay-as-you-go billing method. The billing rules are as follows: Billing starts after the Incremental Data Collection module starts. This means billing begins after the serverless task passes the precheck and is purchased. This includes periods when incremental data synchronization is paused. Within the hour before an overdue payment occurs, if you use the instance for 30 minutes or less, you are charged for half an hour. If you use the instance for more than 30 minutes, you are charged for one hour.
|
Change tracking | Change tracking channel | Pay-as-you-go Billing starts after the task is configured and successfully started. Within the hour before an overdue payment occurs, if you use the instance for 30 minutes or less, you are charged for half an hour. If you use the instance for more than 30 minutes, you are charged for one hour. Subscription You are charged a one-time fee based on the selected configuration and quantity at the time of purchase.
Important For subscription tasks that you no longer use, especially those with auto-renewal enabled, manually cancel auto-renewal or release the instance to which the task belongs. This prevents extra charges. For more information, see Manage auto-renewal and Release DTS instances.
|
Data traffic | Data traffic fees are incurred for the traffic generated when a client consumes data from a change tracking channel. No fees are currently charged. |
Data validation | Full validation | For more information, see Billing of data validation. |
Incremental validation |
Dedicated cluster | Cluster specification | For more information, see Billing of DTS dedicated clusters. |
Internet traffic |
Storage resource |
FAQ
Why am I still charged for a pay-as-you-go instance that is not transferring data?
A pay-as-you-go DTS instance is billed based on resource usage while an incremental task is running, regardless of whether the source data changes. After the data transfer is complete, terminate or release the instance as soon as possible. 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 it. For more information, see Release DTS instances.
Are DTS sync instances charged?
Yes, they are. Although the schema synchronization (Schema Migration in the console) and full data synchronization (Full Data Migration in the Progress section) modules are free, a sync instance includes an Incremental Data Synchronization task by default. Therefore, the sync instance incurs fees.