Database Transmission Service
Database Transmission Service
Database Transmission Service
Document
What's new
Overview
Constraints and limits
Billing
Pre-check items
Permission management
Getting started
Quick start guide for data migration
Quick start guide for data subscription
Quick start guide for data synchronization
Data migration
Creating a data migration task for MySQL
Volcano Engine RDS for MySQL as the source
Volcano Engine veDB for MySQL as the source
MySQL connected over public network as the source
MySQL connected over express network as the source
Creating a data migration task for PostgreSQL
Volcano Engine RDS for PostgreSQL as the source
PostgreSQL connected over public network as the source
PostgreSQL connected over express network as the source
Creating a data migration task for SQL Server
Volcano Engine SQL Server as the source
SQL Server connected over public network as the source
SQL Server connected over express network as the source
Creating a data migration task for Redis
Volcano Engine Cache for Redis as the source
Redis connected over public network as the source
Redis connected over express network as the source
Creating a data migration task for MongDB
Volcano Engine Document Database for MongoDB as the source
MongoDB connected over public network as the source
MongoDB connected over express network as the source
Creating a data migration task for Supabase
Supabase connected over public network as the source
Supabase connected over express network as the source
Data subscription
Creating a data subscription task for MySQL
Creating a data subscription task for PostgreSQL
Consuming subscription data
Data synchronization
Creating a data synchronization task for MySQL
Volcano Engine RDS for MySQL as the source
Volcano Engine veDB for MySQL as the source
MySQL connected over public network as the source
MySQL connected over express network as the source
Creating a data synchronization task for Redis
Volcano Engine Cache for Redis as the source
Redis connected over public network as the source
Redis connected over express network as the source
Creating a data synchronization task for PostgreSQL
Volcano Engine RDS for PostgreSQL as the source
PostgreSQL connected over public network as the source
PostgreSQL connected over express network as the source
Creating a data synchronization task for MongoDB
Volcano Engine Database for MongoDB as the source
MongoDB connected over public network as the source
MongoDB connected over express network as the source
Creating a data synchronization task for Milvus
ETL task management
(Beta) Data verification
(Beta) Migration evaluation
Monitoring and alerts
Best practices
Data migration
Data subscription
API reference
Billing
Data transmission
Data subscription (consumer group management)
Data verification
Migration evaluation
Pre-check
Appendix
SDK reference
FAQs
Common general questions
Pre-check
Troubleshooting
- Documentation
Database Transmission ServiceBillingConfiguration change and unsubscription
Copy page
Download PDFBilling
Configuration change and unsubscription
Copy pageDownload PDFConfiguration change and unsubscription
This topic describes the specifications for changing the configuration and unsubscribing from Database Transmission Service (DTS) tasks.
Specification for configuration change fees
DTS provides two link specifications: Compact and Standard. Resource specification changes are divided into two types: upgrade and downgrade. The specific resource specification changes for both types are as follows:
- Resource upgrade: Upgrade refers to changing the task's link specification from Compact to Standard.
- Resource downgrade: Downgrade refers to changing the task's link specification from Standard to Compact.
tip
- Currently, only data migration and synchronization tasks support specification changes.
- After changing the link specification of a migration or synchronization task, Volcano Engine will recalculate billing based on the new specification. For pay-as-you-go tasks, the new billing will take effect at the next full hour after the specification changes. Additionally, no further specification changes can be made to the task until the previous change is fully effective.
DTS offers two billing methods: pay-as-you-go and subscription. After a DTS task's specification is changed, the fee changes vary depending on the billing method, as detailed below:
- Pay-as-you-go
- Pay-as-you-go resources are billed after usage. The cost for modifying specifications is subject to the bill amount.
- Subscription
- Subscription task resource changes are divided into two types: resource upgrades and resource downgrades, as detailed below:
- Upgrade: When changing resource specifications, if the publish price (hourly publish price) of the new specification is greater than or equal to the publish price of the old specification, the system will calculate the price difference between the new and old specifications using the upgrade formula.
- Downgrade: When changing resource specifications, if the publish price (hourly publish price) of the new specification is less than the publish price of the old specification, the system will calculate the price difference between the new and old specifications using the downgrade refund formula and credit the amount to your account balance. If you downgrade the specification and renew your instance, the system gives priority to the downgrade formula when calculating the refund. If the calculation result is a refund, the system refunds the price difference between the new and old specifications to your account balance. If the calculation result is a charge, the system re-calculates it according to the upgrade formula, and you also need to pay the price difference between the new and old specifications.
- The detailed fees for resource specification changes of subscription tasks are shown in the table below:
Type of specification change | Fee description |
Upgrade | Total payable amount of upgrade order = New specification cost - residual value of old specification = Publish price of new specification (hourly) * remaining time (hour) * discount - publish price of old specification (hourly) * remaining time (hour) * discount |
Downgrade | Total payable amount of downgrade order = New specification cost - refundable residual value of old specification = Publish price of new specification (hourly) * remaining time (hour) * discount - true value of order/purchase duration of order * remaining time = Publish price of new specification (hourly) * remaining time (hour) * discount - (true value of order - true value of order * duration used/purchase duration of order * degrading refund coefficient) = Publish price of new specification (hourly) * remaining time (hour) * discount - (true value of order - true value of order * duration used/purchase duration of order) * degrading refund coefficient |
For more information on specification change fees, refer to the Billing rules for resource changes.
Specification for unsubscription fees
- Pay-as-you-go tasks are unsubscribed upon deletion, and no refunds are involved.
- Subscription instances support non-7-day unconditional unsubscription. For details on refund rules, refer to Unsubscription management.
Last updated: 2026.02.03 15:54:45
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
