- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Preparations
- Business Evaluation
- Network Preparation
- DTS Service Permission Preparation
- Database and Permission Preparation
- Configuring Binlog in Self-Built MySQL
- Data Migration
- Databases Supported by Data Migration
- Cross-Account TencentDB Instance Migration
- Migration to MySQL Series
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to TDSQL TDStore
- Advanced Operations for MySQL Series Migration
- Processing for MySQL Series Pre-Check Failure
- Database Connection Check
- Peripheral Check
- Version Check
- Source Instance Permission Check
- Partial Database Parameter Check
- Target Instance Permission Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Warning Item Check
- TDSQL Proxy Check
- TDSQL Kernel Check
- DDL Ring Linkage Synchronization Detection for Same Database and Table Objects
- DDL Synchronization Conflict Detection for the Same Target and Same Database and Table Object
- Offline Migration of MySQL Data
- Migrating to PostgreSQL
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from TDSQL-C PostgreSQL to TencentDB for PostgreSQL
- PostgreSQL Physical Migration
- Processing for PostgreSQL Series Pre-Check Failure
- Database Connection Check
- Object Dependency Check
- Version Check
- Source or Target Instance Permission Check
- Incremental Migration Pre Check
- Structural Compatibility Check
- Structural Conflict Check
- Account Conflict Check
- Parameter Configuration Conflict Check
- Plugin Compatibility Check
- Multi Task Conflict Detection
- Long Transaction Check
- Migrating to MongoDB
- Migration from MongoDB to MongoDB
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- MongoDB Data Consistency Verification
- Migrating to SQL Server
- Migrating to TencentDB for Redis
- Migrating to KeeWiDB
- Task Management
- Task Status Description
- Viewing Task
- Configuring Task
- Verifying Task
- Start Task
- Retrying Task (MySQL)
- Retrying Task (Redis)
- Speed Limit (MySQL)
- Speed Limit (Redis)
- Complete Task
- Terminating Task
- Deleting Task
- Pausing Task
- Resuming Task
- Changing Configuration
- Terminating Task
- Deisolating Task
- Deleting Task
- Managing Tag
- Creating a Similar Task
- Viewing Log
- Data Sync
- Databases Supported by Data Sync
- Cross-Account TencentDB Instance Sync
- Sync to MySQL series
- Sync to MySQL
- Sync to MariaDB
- Sync to TDSQL-C for MySQL
- Sync to TDSQL for MySQL
- Sync to TDSQL TDStore
- MySQL Series Advanced Sync Operations
- MySQL series Pre Validation Failed Processing
- Database Connection Check
- Peripheral Check
- Version Check
- Source Instance Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Warning Item Check
- TDSQL Proxy Check
- TDSQL kernel check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Synchronize to PostgreSQL
- Synchronization from PostgreSQL to PostgreSQL
- PostgreSQL Pre Validation does not Pass Processing
- Database Connection Check
- Object Dependency Check
- Version Check
- Source or Target Instance Permission Check
- Incremental Migration Pre Check
- Structural Compatibility Check
- Structural Conflict Check
- Account Conflict Check
- Parameter Configuration Conflict Check
- Plugin Compatibility Check
- Primary Key Dependency Check
- Check the Key Parameters of the Instance
- Multi Task Conflict Detection
- Synchronize to Kafka
- Task Management
- Task Status Description
- Viewing Task
- Configuring Task
- Verifying Task
- Starting Task
- Retrying Task (MySQL)
- Speed Limit
- Stopping Task
- Modify Sync configuration
- Pausing Task
- Resuming Task
- Resetting Task
- Deleting Task
- Changing Configuration
- Pay-as-You-Go to Monthly Subscription
- Terminating/Returning Instance
- Renewing Task
- Deisolating Task
- Deleting Instance
- Creating a Similar Task
- Viewing Log
- Deleting Task
- Data Subscription (Kafka Edition)
- Databases Supported by Data Subscription
- MySQL series Data Subscription
- Creating MySQL or TDSQL for MySQL Data Subscription
- Creating TDSQL for MySQL Data Subscription
- Creating MariaDB/Percona Data Subscription
- Consuming MySQL Data
- Advanced Subscription Operations
- Fix for Verification Failure
- Data Subscription for TDSQL PostgreSQL
- MongoDB Data Subscription
- Task Management
- Consumption Management
- Fix for Verification Failure
- Cutover Description
- Monitoring and Alarms
- Ops Management
- Practical Tutorial
- Synchronizing Local Database to the Cloud
- Creating Two-Way Sync Data Structure
- Creating Many-to-One Sync Data Structure
- Creating Multi-Site Active-Active IDC Architecture
- Selecting Data Sync Conflict Resolution Policy
- Using CLB as Proxy for Cross-Account Database Migration
- Migrating Self-Built Databases to Tencent Cloud Databases via CCN
- Best Practices for DTS Performance Tuning
- FAQs
- Error Handling
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- (NewDTS) Data Migration APIs
- DescribeMigrationJobs
- ModifyMigrationJob
- CompleteMigrateJob
- DescribeMigrationDetail
- CreateMigrationService
- CreateMigrateCheckJob
- DescribeMigrationCheckJob
- SkipCheckItem
- StartMigrateJob
- StopMigrateJob
- ResumeMigrateJob
- RecoverMigrateJob
- ModifyMigrateName
- ModifyMigrateJobSpec
- IsolateMigrateJob
- DestroyMigrateJob
- DescribeMigrateDBInstances
- PauseMigrateJob
- ContinueMigrateJob
- Data Sync APIs
- DescribeSyncJobs
- ModifySyncJobConfig
- CreateModifyCheckSyncJob
- DescribeModifyCheckSyncJobResult
- StartModifySyncJob
- CreateSyncJob
- ConfigureSyncJob
- CreateCheckSyncJob
- SkipSyncCheckItem
- DescribeCheckSyncJobResult
- StartSyncJob
- StopSyncJob
- ResumeSyncJob
- ResizeSyncJob
- RecoverSyncJob
- IsolateSyncJob
- DestroySyncJob
- PauseSyncJob
- ContinueSyncJob
- Data Consistency Check APIs
- Data Types
- Error Codes
- DTS API 2018-03-30
- SDK Documentation
- Service Agreement
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Preparations
- Business Evaluation
- Network Preparation
- DTS Service Permission Preparation
- Database and Permission Preparation
- Configuring Binlog in Self-Built MySQL
- Data Migration
- Databases Supported by Data Migration
- Cross-Account TencentDB Instance Migration
- Migration to MySQL Series
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to TDSQL TDStore
- Advanced Operations for MySQL Series Migration
- Processing for MySQL Series Pre-Check Failure
- Database Connection Check
- Peripheral Check
- Version Check
- Source Instance Permission Check
- Partial Database Parameter Check
- Target Instance Permission Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Warning Item Check
- TDSQL Proxy Check
- TDSQL Kernel Check
- DDL Ring Linkage Synchronization Detection for Same Database and Table Objects
- DDL Synchronization Conflict Detection for the Same Target and Same Database and Table Object
- Offline Migration of MySQL Data
- Migrating to PostgreSQL
- Migration from PostgreSQL to TencentDB for PostgreSQL
- Migration from TDSQL-C PostgreSQL to TencentDB for PostgreSQL
- PostgreSQL Physical Migration
- Processing for PostgreSQL Series Pre-Check Failure
- Database Connection Check
- Object Dependency Check
- Version Check
- Source or Target Instance Permission Check
- Incremental Migration Pre Check
- Structural Compatibility Check
- Structural Conflict Check
- Account Conflict Check
- Parameter Configuration Conflict Check
- Plugin Compatibility Check
- Multi Task Conflict Detection
- Long Transaction Check
- Migrating to MongoDB
- Migration from MongoDB to MongoDB
- Fix for Verification Failure
- MongoDB Connection Check
- Database/Table Content Conflict Check
- Source Database Node Role Check
- Oplog Check
- Source/Target Database Account Permission Check
- Database Version Check
- Database Capacity Check
- Target Database Load Check
- ShardKey Check
- Source Database Balancer Check
- Time Series Collection Verification
- Compression Algorithm Verification
- MongoDB Data Consistency Verification
- Migrating to SQL Server
- Migrating to TencentDB for Redis
- Migrating to KeeWiDB
- Task Management
- Task Status Description
- Viewing Task
- Configuring Task
- Verifying Task
- Start Task
- Retrying Task (MySQL)
- Retrying Task (Redis)
- Speed Limit (MySQL)
- Speed Limit (Redis)
- Complete Task
- Terminating Task
- Deleting Task
- Pausing Task
- Resuming Task
- Changing Configuration
- Terminating Task
- Deisolating Task
- Deleting Task
- Managing Tag
- Creating a Similar Task
- Viewing Log
- Data Sync
- Databases Supported by Data Sync
- Cross-Account TencentDB Instance Sync
- Sync to MySQL series
- Sync to MySQL
- Sync to MariaDB
- Sync to TDSQL-C for MySQL
- Sync to TDSQL for MySQL
- Sync to TDSQL TDStore
- MySQL Series Advanced Sync Operations
- MySQL series Pre Validation Failed Processing
- Database Connection Check
- Peripheral Check
- Version Check
- Source Instance Permission Check
- Partial Database Parameter Check
- Target Database Content Conflict Check
- Target Database Space Check
- Binlog Parameter Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Warning Item Check
- TDSQL Proxy Check
- TDSQL kernel check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Synchronize to PostgreSQL
- Synchronization from PostgreSQL to PostgreSQL
- PostgreSQL Pre Validation does not Pass Processing
- Database Connection Check
- Object Dependency Check
- Version Check
- Source or Target Instance Permission Check
- Incremental Migration Pre Check
- Structural Compatibility Check
- Structural Conflict Check
- Account Conflict Check
- Parameter Configuration Conflict Check
- Plugin Compatibility Check
- Primary Key Dependency Check
- Check the Key Parameters of the Instance
- Multi Task Conflict Detection
- Synchronize to Kafka
- Task Management
- Task Status Description
- Viewing Task
- Configuring Task
- Verifying Task
- Starting Task
- Retrying Task (MySQL)
- Speed Limit
- Stopping Task
- Modify Sync configuration
- Pausing Task
- Resuming Task
- Resetting Task
- Deleting Task
- Changing Configuration
- Pay-as-You-Go to Monthly Subscription
- Terminating/Returning Instance
- Renewing Task
- Deisolating Task
- Deleting Instance
- Creating a Similar Task
- Viewing Log
- Deleting Task
- Data Subscription (Kafka Edition)
- Databases Supported by Data Subscription
- MySQL series Data Subscription
- Creating MySQL or TDSQL for MySQL Data Subscription
- Creating TDSQL for MySQL Data Subscription
- Creating MariaDB/Percona Data Subscription
- Consuming MySQL Data
- Advanced Subscription Operations
- Fix for Verification Failure
- Data Subscription for TDSQL PostgreSQL
- MongoDB Data Subscription
- Task Management
- Consumption Management
- Fix for Verification Failure
- Cutover Description
- Monitoring and Alarms
- Ops Management
- Practical Tutorial
- Synchronizing Local Database to the Cloud
- Creating Two-Way Sync Data Structure
- Creating Many-to-One Sync Data Structure
- Creating Multi-Site Active-Active IDC Architecture
- Selecting Data Sync Conflict Resolution Policy
- Using CLB as Proxy for Cross-Account Database Migration
- Migrating Self-Built Databases to Tencent Cloud Databases via CCN
- Best Practices for DTS Performance Tuning
- FAQs
- Error Handling
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- (NewDTS) Data Migration APIs
- DescribeMigrationJobs
- ModifyMigrationJob
- CompleteMigrateJob
- DescribeMigrationDetail
- CreateMigrationService
- CreateMigrateCheckJob
- DescribeMigrationCheckJob
- SkipCheckItem
- StartMigrateJob
- StopMigrateJob
- ResumeMigrateJob
- RecoverMigrateJob
- ModifyMigrateName
- ModifyMigrateJobSpec
- IsolateMigrateJob
- DestroyMigrateJob
- DescribeMigrateDBInstances
- PauseMigrateJob
- ContinueMigrateJob
- Data Sync APIs
- DescribeSyncJobs
- ModifySyncJobConfig
- CreateModifyCheckSyncJob
- DescribeModifyCheckSyncJobResult
- StartModifySyncJob
- CreateSyncJob
- ConfigureSyncJob
- CreateCheckSyncJob
- SkipSyncCheckItem
- DescribeCheckSyncJobResult
- StartSyncJob
- StopSyncJob
- ResumeSyncJob
- ResizeSyncJob
- RecoverSyncJob
- IsolateSyncJob
- DestroySyncJob
- PauseSyncJob
- ContinueSyncJob
- Data Consistency Check APIs
- Data Types
- Error Codes
- DTS API 2018-03-30
- SDK Documentation
- Service Agreement
Billing Mode
Billing Mode | Payment Mode | Use Case and Description |
Monthly subscription | Prepaid Billing. You need to pay the fees when creating an instance. | It is more cost-effective in the long term for businesses with stable needs than pay-as-you-go billing. |
Pay-as-you-go | Postpaid Billing. A bill is generated every hour, and fees are deducted from your Tencent Cloud account based on the bill. | It is suitable for instantaneously fluctuating businesses. In this mode, instances can be released immediately after the use to save costs. Only pay-as-you-go data sync tasks can be changed to the monthly subscription billing mode. |
Billable Items and Rules
Note
You will be charged for using MySQL/TDSQL-C for MySQL/MariaDB/Percona links in data migration and data sync tasks through DTS from June 15, 2023. The existing data migration and data sync tasks created before the official billing will be charged. For more information, see Existing DTS Task Billing Rules.
Billing for all supported links in data subscription started on 2020.
Feature Instance | Billable Item | Billing Mode | Description |
Data Migration | Link configuration fees | Pay-as-you-go | Full migration is free of charge. Fees are incurred only during normal incremental migration (including data consistency check). When the task ends or is paused, billing will also stop. If you select Structural migration or Full migration for Migration Type, no fees will be incurred. If you select Full + incremental migration for Migration Type, during source database export and data import, full migration is performed free of charge. During subsequent incremental sync, incremental migration is performed and billing starts. When you click Complete, the task ends and billing stops. |
| Public network traffic fees | Pay-as-you-go | Currently, the public network traffic is free of charge. |
Data Sync | Link configuration fees | Monthly subscription and pay-as-you-go | A monthly subscribed task is billed upon purchase. A pay-as-you-go task is free of charge during configuration and will incur fees only when it starts running. Fees will incur only when it runs normally, and billing will stop when it is paused. |
| Public network traffic fees | Pay-as-you-go | Currently, the public network traffic is free of charge. |
Data Subscription | Link configuration fees | Monthly subscription | Billing will start after the configuration is completed and the instance starts successfully. |
| Data storage fees | Free | Currently, data storage is free of charge. |
| |||
In pay-as-you-go billing mode, the fees for one hour's usage will be frozen during task creation and will be unfrozen when you terminate the instance or the instance is isolated and terminated due to overdue payments. This is the case even in scenarios where no fees are incurred, for example, incremental migration is not selected in a migration task, or a pay-as-you-go sync task is purchased but not started. We recommend that you terminate completed or unwanted tasks promptly to unfreeze fees in time.
Billable DTS Links
Billable DTS Links
Only the following commercial links for data migration and sync are billed, and you will be notified if billing starts for other free links. All supported links for data subscription are billed.
Data Migration | Data Sync |
MySQL/MariaDB/Percona > MySQL MySQL/MariaDB/Percona > MariaDB MySQL/MariaDB/Percona > TDSQL-C for MySQL | MySQL/MariaDB/Percona/TDSQL-C for MySQL
> MySQL MySQL/MariaDB/Percona/TDSQL-C for MySQL > MariaDB MySQL/MariaDB/TDSQL-C for MySQL > TDSQL-C for MySQL MySQL/MariaDB/Percona/TDSQL-C for MySQL > Kafka |
Data Migration Billing Details
Link configuration fees (pay-as-you-go)
Note
For DTS link configuration billing, three key factors are specifications, cross-region selection, and target region. Prices vary depending on the combo. For more information, see the purchase page in the [DTS console](https://buy.cloud.tencent. com/migration!85f6590a97448e3282d761536d270586).
Specifications are increased from small to medium to large, xlarge, and 2xlarge. Higher specifications incur higher fees and deliver better transmission performance.
The cost of links across regions is higher than that of links in the same region. For example, "Beijing-to-Beijing" means the same region, "Beijing-to-Shanghai" means cross-region, "Beijing-to-Beijing Finance" means cross-region, and each finance region is counted as an independent region.
The billing will differ depending on whether the target region is Chinese Mainland, the finance region in Chinese Mainland, Hong Kong (China), or other countries and regions. See the table below for details. In a cross-region link, the billing outcome is always the same for the same target region regardless of the region choice made on the source side.
RPS indicates the number of incremental data rows migrated to the target table per second by DTS RPS is subject to various factors such as operational load of the source database, network bandwidth, and network latency. Therefore, the following figure data is for reference only.
Specifications | Target Region - Chinese Mainland (USD/Hour) | Target Region - Finance Regions in Chinese Mainland (USD/Hour) | Target Region - Hong Kong (China) and Other Countries/Regions (USD/Hour) | Maximum RPS | |||
| Same region | Across region | Same region | Across region | Same region | Across region | |
small | 0.14571429 | 0.20428571 | 0.27714286 | 0.38857143 | 0.21857143 | 0.30571429 | 2000 |
medium | 0.25714286 | 0.36 | 0.48857143 | 0.68428571 | 0.38571429 | 0.54 | 5000 |
large | 0.43 | 0.60142857 | 0.81714286 | 1.14428571 | 0.64571429 | 0.90428571 | 6000 |
xlarge | 0.77428571 | 1.08428571 | 1.47142857 | 2.06 | 1.16142857 | 1.62571429 | 7000 |
2xlarge | 1.37428571 | 1.92428571 | 2.61142857 | 3.65571429 | 2.06142857 | 2.88571429 | >7000 |
Data Sync Billing Details
Note
For DTS link configuration billing, three key factors are specifications, cross-region selection, and target region. Prices vary depending on the combo. For more information, see the purchase page in the DTS console.
Specifications are increased from micro to small to medium and large. Higher specifications incur higher fees and deliver better transmission performance.
The cost of links across regions is higher than that of links in the same region. For example, "Beijing-to-Beijing" means the same region, "Beijing-to-Shanghai" means cross-region, "Beijing-to-Beijing Finance" means cross-region, and each finance region is counted as an independent region.
The billing will differ depending on whether the target region is Chinese Mainland, the finance region in Chinese Mainland, Hong Kong (China), or other countries and regions. See the table below for details. In a cross-region link, the billing outcome is always the same for the same target region regardless of the region choice made on the source side.
RPS indicates the number of incremental data rows synced to the target table per second by DTS. RPS is subject to various factors such as operational load of the source database, network bandwidth, and network latency. Therefore, the following figure data is for reference only.
Link configuration fees (monthly subscription)
Specifications | Target Region - Chinese Mainland (USD/Month) | Target Region - Finance Regions in Chinese Mainland (USD/Month) | Target Region - Hong Kong (China) and Other Countries/Regions (USD/Month) | Maximum RPS | |||
| Same region | Across region | Same region | Across region | Same region | Across region | |
micro | 56.85714286 | 79.6 | 108.0285714 | 151.24 | 85.28571429 | 119.4 | 1000 |
small | 120.2857143 | 168.4 | 228.5428571 | 319.96 | 180.4285714 | 252.6 | 2000 |
medium | 168.5714286 | 236 | 320.2857143 | 448.4 | 252.8571429 | 354 | 5000 |
large | 250 | 350 | 475 | 665 | 375 | 525 | >5000 |
Link configuration fees (pay-as-you-go)
Specifications | Target Region - Chinese Mainland (USD/Hour) | Target Region - Finance Regions in Chinese Mainland (USD/Hour) | Target Region - Hong Kong (China) and Other Countries/Regions (USD/Hour) | Maximum RPS | |||
| Same region | Across region | Same region | Across region | Same region | Across region | |
micro | 0.12 | 0.16857143 | 0.22857143 | 0.32 | 0.18 | 0.25142857 | 1000 |
small | 0.25428571 | 0.35571429 | 0.48285714 | 0.67571429 | 0.38142857 | 0.53428571 | 2000 |
medium | 0.35428571 | 0.49571429 | 0.67285714 | 0.94142857 | 0.53142857 | 0.74428571 | 5000 |
large | 0.53 | 0.74142857 | 1.00714286 | 1.41 | 0.79571429 | 1.11428571 | >5000 |
Data Subscription Billing Details
Source database region | Link Configuration Fees - Monthly Subscription (USD/Month) | Link Configuration Fees - Pay-as-You-Go (USD/Hour) |
Chinese mainland | 102.8571429 | 0.35714286 |
Chinese mainland finance zones | 125.7142857 | 0.43714286 |
Hong Kong (China) and other countries/regions | 125.7142857 | 0.43714286 |
Existing DTS Task Billing Rules
Existing DTS Task Billing Rules
1. The billing rules for existing data migration tasks are as follows:
After billing started officially, the specifications of existing tasks were switched to xlarge by default, which can be modified for NewDTS but not OldDTS.
The pay-as-you-go billing mode was adopted.
As incremental migration tasks are billed, we recommend that you cut over promptly after migration is completed to avoid incurring unnecessary fees.
2. The billing rules for existing data sync tasks are as follows:
After billing started officially, the specifications of existing tasks were switched to medium by default and can be modified.
The monthly subscription billing mode was adopted, and the uniform expiration date was set to Thursday, June 15, 2023.
After billing started officially, sync tasks entered the overdue payment status first (and could still be used normally for 24 hours). You needed to renew them in the console; otherwise, they would be suspended after 24 hours and deleted automatically seven days after suspension.
Note
After billing started and the specifications were switched to the default value, the RPS limits took effect gradually.
Yes
No
Was this page helpful?