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

Resource Package FAQs

PDF
Focus Mode
Font Size
Last updated: 2025-05-28 14:43:09
This document introduces FAQs related to resource packages.

What Is a Resource Package?

A resource package is a prepaid resource type introduced by TDSQL-C for MySQL. It is divided into computing resource packages and storage resource packages, which can be used to offset the computing and storage resources consumed by Serverless clusters. The unit price of a resource package is more affordable compared to pay-as-you-go billing. It is recommended to purchase and bind resource packages to Serverless instances first.

Can a Provisioned Resource Cluster Use Resource Packages?

Provisioned resource clusters support mounting read-only instances with provisioned resources and Serverless read-only instances. However, only Serverless read-only instances support using resource packages. A Serverless cluster can use resource packages.

What Types of Resource Packages Are Available?

Resource packages are divided into computing resource packages and storage resource packages. The computing resource package is a fixed quota resource package for computing resources, used to offset the computing resources of Serverless instances bound to the resource package. Once the resource package quota is used up, the cluster will continue to charge based on pay-as-you-go billing. The storage resource package is a fixed quota resource package for storage resources, used to offset the storage resources of Serverless instances bound to the resource package. Once the resource package quota is used up, the cluster will continue to charge based on pay-as-you-go billing.

How Many Resource Packages Can Be Bound to a Cluster?

A cluster can be bound to up to 10 computing resource packages and 10 storage resource packages simultaneously.

How to Use a Resource Package?

If you have purchased a Serverless cluster, you can directly purchase a Serverless resource package to offset the computing and storage resource fees within the cluster.
If you have purchased a provisioned resource cluster and mounted a Serverless read-only instance by enabling Serverless, you can directly purchase a Serverless computing resource package to offset the computing resource fees of the Serverless read-only instance within the cluster.
If you have not purchased any Serverless clusters, you can quickly use the resource package by following these three steps.
If your current provisioned resource cluster has not enabled Serverless, you only need the following three steps to quickly use a Serverless computing resource package.

How to Purchase a Resource Package?

You can purchase a resource package through the resource package purchase page or the console. For detailed operations, see Purchasing Resource Packages.

What Is the Consumption Order of Multiple Resource Packages?

When multiple resource packages of the same type (computing or storage) are bound, the backend will automatically set the consumption order based on the order of binding. You can manually adjust this order by modifying the consumption priority ranking. The consumption rule follows the priority level (1-10) in ascending order, with lower numbers being consumed first. For details, see Adjusting Consumption Priority Order.

Will Unused Resources in a Resource Package Expire?

Resource packages have a validity period. You can choose a validity period of 6 months or 1 year when purchasing the package. If the resources are consumed before the validity period expires, or if the validity period ends, the resource package can no longer be used. You will need to purchase and bind a new resource package. You can check the resource package usage details and expiration time via Viewing Resource Package Usage.

Is It Necessary to Purchase a Serverless Resource Package After Purchasing a Serverless Cluster?

No, after you purchase a Serverless cluster, the billing mode is pay-as-you-go. You can choose whether to purchase a Serverless computing or storage resource package. After purchasing and binding, the resource package will automatically offset the computing or storage resource fees in the Serverless cluster. If the resource package is used up and no new resource package is bound, the Serverless cluster will continue to charge based on the pay-as-you-go mode.

Do Serverless Clusters Created Before a Serverless Resource Package Is Purchased Support Using Resource Packages?

It is supported.

Do Provisioned Resource Clusters that Enable Serverless Before a Serverless Resource Package Is Purchased Support Using Resource Packages?

Yes, but only computing resource packages can be bound, and they are used to offset the elastic computing resources of Serverless read-only instances under the provisioned resource cluster.

Can Resource Packages Be Upgraded?

It is not supported.

Can Resource Packages Be Renewed?

It is not supported.

Can the Validity Period of a Resource Package Be Modified?

No, since the unit prices of 6-month and 1-year resource packages differ, modifying the validity period after purchase is not supported.

How to Request a Refund for a Resource Package?

Resource packages that have been used up or have expired do not support refunds.
For resource packages that have remaining resources within the validity period, self-service refunds can be requested via the console. Each Tencent Cloud account (root account) can request up to 20 resource package refunds per calendar year. For refund instructions, see Requesting Refund for Resource Package.
Note:
Regarding the limit of refunds, the system calculates it based on the calendar year. The first calendar cycle is from June 30, 2023, 23:59:59 to July 1, 2024, 00:00:00. The number of refunds is reset at 00:00:00 on July 1 each year. The second cycle runs from July 1, 2024, 00:00:00 to June 30, 2025, 23:59:59, and so on.

Help and Support

Was this page helpful?

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

Feedback