Billing method | Supported instances | Description |
Subscription | | A subscription instance is an instance for which you pay in advance to use.
Note If the source or destination database of a data synchronization instance is locked because the database instance expires, DTS can still connect to the source or destination database. In this case, we recommend that you release the DTS instance at the earliest opportunity to avoid additional fees. If a data verification task is created on a subscription synchronization instance, additional fees are incurred. For more information, see Billing of data verification tasks.
The subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term use. Subscription instances cannot be manually released. If a subscription instance is not renewed, the instance expires at the end of the subscription duration. In the new DTS console, you can change the billing method of an instance between subscription and pay-as-you-go. In the old DTS console, you can change the billing method only from pay-as-you-go to subscription. We recommend that you use the new DTS console. For more information, see Change the billing method.
|
Pay-as-you-go | | A pay-as-you-go instance is an instance for which you are charged per hour based on your resource usage. The hourly fees are calculated based on the instance class that you specify in the purchase order and are deducted from the balance of your Alibaba Cloud account.
Note If the source or destination database of a DTS instance is locked because the database instance expires, DTS can still connect to the source or destination database. In this case, we recommend that you release the DTS instance at the earliest opportunity to avoid additional fees. The pay-as-you-go billing method is suitable for short-term use. If you no longer require a pay-as-you-go instance, you can release it to reduce costs. For more information, see Release DTS instances. Take note of the following items when you configure a data synchronization instance: You are charged based on the instance class after the Incremental Data Collection module is started. You are still charged for the data synchronization instance during the period in which the data synchronization instance is paused.
Take note of the following items when you configure a data migration instance: If you do not select Incremental Data Migration as a migration type, you are not charged for the data migration instance. If you select Incremental Data Migration as a migration type, you are charged based on the instance class after the Incremental Write module is started. You are not charged for the data migration instance during the period in which the data migration instance is paused.
Take note of the following items when you configure a change tracking instance: For information about the billing method of data verification tasks, see Billing of data verification tasks. You can change the billing method of an instance from pay-as-you-go to subscription. For more information, see Change the billing method.
Important The billing method of data migration instances cannot be changed. After a DTS instance starts to be billed, the billing stops only if the instance fails, completes the task, or is released. You are still charged for a data synchronization instance during the period in which the instance is paused, regardless of whether the source or destination database can be connected. This is because the paused instance still consumes resources such as CPU and memory. After the instance is paused, DTS stops writing data to the destination database but continues trying to read logs from the source database. This helps resume the data synchronization instance immediately after the instance is restarted.
|
Serverless | Data synchronization instance | Serverless is a dynamic billing method that allows you to dynamically adjust the resource specifications of an instance at a one-minute interval based on the workload of the instance. You are charged for the instance per hour based on your resource usage. This helps you save a lot of costs.
Note If the source or destination database of a DTS instance is locked because the database instance expires, DTS can still connect to the source or destination database. In this case, we recommend that you release the DTS instance at the earliest opportunity to avoid additional fees. Serverless instances are suitable for scenarios where business data volumes change irregularly. You can use a serverless instance if the amount of data to be transmitted is large in the early stage and levels off in later stages or if the amount of data to be transmitted is unpredictable. If your DTS task is complete, you can release the instance. For more information, see Release DTS instances. Take note of the following items when you configure a data synchronization instance: You are charged based on the instance class after the Incremental Data Collection module is started. You are still charged for the data synchronization instance during the period in which the data synchronization instance is paused.
|