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

Storage Resource Pack

PDF
Focus Mode
Font Size
Last updated: 2026-01-29 17:47:35
A storage resource package is a prepaid resource type launched by TDSQL-C for MySQL. It can be used to deduct the storage resources used by Serverless instances. The resource packages will not affect the pay-as-you-go billing mode of Serverless storage resources. After a resource package is used, settlement is performed per hour by deducting the actual usage from your purchased resource package. In this way, you can benefit from the preferential storage resource prices while enjoying the high-precision billing mode of Serverless. This document describes the specification types and prices of storage resource packages.

Specification Types and Prices

Specification Type
Applicable Scope of Storage Capacity
Unit Price in Chinese Mainland (USD/TB)
Unit Price Outside Chinese Mainland (USD/TB)
Basic Edition
2–⁠200TB (200 exclusive)
6-month validity period: 0.2568
1-year validity period: 0.271
6-month validity period: 0.2806
1-year validity period: 0.2962
General Edition
200–2000 TB (2000 exclusive)
6-month validity period: 0.2425
1-year validity period: 0.2568
6-month validity period: 0.265
1-year validity period: 0.2806
Enterprise Edition
2000–20,000 TB (20,000 exclusive)
6-month validity period: 0.2282
1-year validity period: 0.2425
6-month validity period: 0.2494
1-year validity period: 0.265

Case

We will compare the storage resource fees of two instances (one without a storage resource package and the other with a storage resource package) to more intuitively understand the cost difference between using and not using a storage resource package.
Case background
Region: Beijing.
Instance Mode: Single-Node Edition.
The first instance: Unused storage resource package will be billed on a pay-as-you-go basis, denoted as Instance A.
The second instance: Utilizing the storage resource package, a Basic Edition storage resource package was purchased and bound, offering a storage capacity of 10TB with a validity period of 6 months. Denoted as Instance B.
Operation scenario: Instance A and instance B have been running continuously for 3 hours respectively. The storage space used in the first hour is 0.5TB, the storage space used in the second hour is 1TB, and the storage space used in the third hour is 2TB. The storage resource costs of these 3 hours are calculated and compared below.
Cost comparison
Comparative item
Instance A (Unused storage resource package)
Instance B (Used storage resource package)
Billing formula
storage space fees = storage space price × storage space
total storage resource fees of running for 3 hours = fees for the first hour + fees for the second hour + fees for the third hour
storage space fees = storage space price × storage space
total storage resource fees of running for 3 hours = fees for the first hour + fees for the second hour + fees for the third hour
Billing model
pay as you go
storage resource pack
Storage space fees
(unit price)
0.00072 USD per GB
Approximately equal to 0.72 USD per TB
0.2568 USD per TB
Storage space
the storage space used in the first hour: 0.5TB
the storage space used in the second hour: 1TB
the storage space used in the third hour: 2TB
the storage space used in the first hour: 0.5TB
the storage space used in the second hour: 1TB
the storage space used in the third hour: 2TB
Storage resource fees
0.72 x 0.5 + 0.72 x 1 + 0.72 x 2 = 2.52 USD
0.2568 x 0.5 + 0.2568 x 1 + 0.2568 x 2 = 0.8988 USD
Subsequent billing
subsequent operations of instance A will continue to use pay-as-you-go billing, resulting in new fees
the total storage resource package purchased by instance B is 10TB. In the past 3 hours, 3.5TB has been consumed, and the remaining amount is 6.5TB. This storage resource package will continue to be consumed in the future. Instance B will not be restored until the storage resource package is consumed or expires. For pay-as-you-go billing, you can also continue to purchase and bind other storage resource packages before the storage resource package is consumed.
Compare results
It can be seen from the above comparison that since the unit price of storage space in a storage resource package is lower than that of pay-as-you-go, the overall storage resource fees is reduced, and it is more favorable to use a storage resource package. The unit prices of storage resource packages for Basic Edition, General Edition, and Enterprise Edition are different. You can choose the appropriate specification type based on the actual storage required.

Note

Storage resource packages will accumulate the actual storage usage on an hourly basis for deduction, which is more cost-effective and flexible than the pay-as-you-go option. Before the deduction of the serverless cluster, you must first bind a storage resource pack. The cluster will not be terminated when the resource pack is unbound, used up, or expires. It will instead be billed on a pay-as-you-go basis. It is important to note the following points:
Storage resource packs are classified into two types: those for the Chinese mainland and those for regions outside the Chinese mainland. Each type is specified to be shared by all serverless clusters in the region, that is, one storage resource pack can be shared by multiple serverless clusters.
A serverless cluster can be bound to a maximum of ten storage resource packages, with support for adjusting the consumption priority order of multiple storage resource packages. The cluster will consume resources in ascending order based on the priority level numbers.
Storage resource packages will accumulate the consumption on an hourly basis for deduction.
Storage resource packages do not support downgrade once purchased.

Management

Refund

For resource packages that remain unused within their validity period, each Tencent Cloud account (primary account) is calculated on a calendar year basis, with a maximum of 20 refundable resource packages per year. As for resource packages that have expired or been fully utilized, refunds are currently not supported. For detailed refund instructions, see Requesting Refund for Resource Pack.
Note:
Regarding the limitation on the number of refunds, the system calculates this on a calendar year basis. The first calendar year cycle is from June 30, 2023, at 23:59:59 to July 1, 2024, at 00:00:00. The count refreshes on July 1 at 00:00:00 every year, thus the second calendar year cycle is from July 1, 2024, at 00:00:00 to June 30, 2025, at 23:59:59, and so on.

Relevant Documents

Related APIs

API
Description
This API (CreateResourcePackage) is used to purchase new resource pack.

Help and Support

Was this page helpful?

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

Feedback