tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us
DocumentationTDSQL-C for MySQLPurchase GuideSpecification Adjustment Description

Specification Adjustment Description

PDF
Focus Mode
Font Size
Last updated: 2026-03-24 16:31:21
This document describes the costs of specification adjustment for both pay-as-you-go and yearly/monthly subscribed clusters, focusing on compute nodes and storage space.
Note:
TDSQL-C for MySQL adopts a storage-computing separation architecture that allows independent specification adjustment instead of specification adjustment for both, improving the flexibility of specification adjustment.
When upgrading instances in a cluster, there is an upper limit to the storage space. The storage space cannot exceed the upper limit corresponding to the compute node. If a larger storage space is required, you can upgrade your current compute node specifications first. For detailed compute node specifications and upper storage limit, see Product Specifications.

Compute Node Specification Adjustment

Note:
Discounts and vouchers are not returned.
The refund will be returned to your Tencent Cloud account by the proportion of the cash and free credits paid for the purchase.
If the refund amount is ≤ 0, it will be calculated as 0, that is, the refund amount will be 0.

Cost of Specification Adjustment for Pay-as-You-Go Clusters

For pay-as-you-go clusters, charges are billed on an hourly basis. After specification adjustments, the next billing cycle will be charged at the new hourly rate. For example, a user in Beijing Zone 3 adjusts the specification of the TDSQL-C for MySQL cluster from a 1-core, 2-GB instance to a 2-core, 4-GB instance, resulting in a billing rate shift from 0.018396 USD per hour to 0.099936 USD.

Cost of Specification Adjustments for Yearly/Monthly Subscribed Clusters

Specification Adjustment
Billing Description
Upgrading specifications
When users upgrade their compute node specifications, the system determines the cost difference between the current and upgraded node specifications. A bill is then generated, with the calculated difference deducted from the user's account. If the account balance is insufficient, a top-up is necessary. Following the upgrade, billing is based on the updated instance specifications.
Cost difference = Unit price of new specifications × Validity period - Unit price of original specifications × Validity period
Downgrading specifications
When users downgrade their compute node specifications, the system determines the cost difference between the current and downgraded node specifications. A bill is then generated, with the calculated difference refunded to the user's account.
Refund amount = Remaining amount of the original specification - Purchase price of the new specification- Remaining amount for the original specification = Effective order amount of original specification - Used value of original specification.
Effective order amount of original specification: The amount paid for the currently effective order, excluding discounts and vouchers.
Used value of original specification: For the used part, if the usage has lasted at least one month as of the date of downgrade, fees will be deducted by month; otherwise, fees will be deducted in a pay-as-you-go manner.
Purchase value of the new specification: The current official price of the new specification multiplied by the remaining validity period.
Adding Read-only instances
The cost is charged according to the unit price of the newly purchased compute node.
Cost of new read-only instances = Compute node unit price (USD/day) × Validity period
Deleting instances
Both read-only instances and read-write instances can be deleted. For more information related to the cost of deleting instances, see Refund.
Note:
In a cluster with both read-write and read-only instances, delete the read-only instances first. Deleting the read-write instance is the same as returning the entire cluster. Alternatively, you can delete the entire cluster, removing both read-write and read-only instances.

Storage Space Specification Adjustment

Note:
When reducing storage space, the new storage space should not be lower than the used storage space. If a lower storage space is required, please clear the corresponding data first.

Cost of Specification Adjustment for Pay-as-You-Go Clusters

In the pay-as-you-go billing mode, the cost of the cluster storage space is still charged based on the hourly usage, and there is no need to purchase unused storage space in advance. However, each compute node specification has a storage space upper limit. If you require maximum storage space, you can upgrade the compute node specifications.

Cost of Specification Adjustment for Yearly/Monthly Subscribed Clusters

In the yearly/monthly subscription mode, the cost of storage space is charged based on the pre-purchased amount with a tiered pricing model. For detailed pricing information, please refer to Product Pricing.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback