tencent cloud

TencentDB for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
User Tutorial
Product Introduction
Overview
Strengths
Use Cases
Database Architecture
Resource Isolation Policy
Economical Instance
Feature List
Database Instance
High Availability (Multi-AZ)
Regions and AZs
Service Regions and Service Providers
Kernel Features
Overview
Kernel Version Release Notes
Functionality Features
Performance Features
Security Features
Stability Features
TXRocks Engine
LibraDB Engine
Checking and Fixing Kernel Issues
Purchase Guide
Billing Overview
Selection Guide
Purchase Methods
Renewal
Payment Overdue
Refund
Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fee
Backup Space Billing
Database Audit Billing Overview
Commercial Billing and Activity Description for Database Proxy
Description of the Database Proxy Billing Cycle
Viewing Bills
Getting Started
Overview
Creating MySQL Instance
Connecting to MySQL Instance
SQL Insight (Database Audit)
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Log
Log Shipping
Configuring Post-Event Alarms
Modifying Audit Rule
Modifying Audit Services
Disabling Audit Service
Audit Rule Template
SQL Audit Rule (Legacy)
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
MySQL Cluster Edition
Introduction to TencentDB for MySQL Cluster Edition
Creating TencentDB for MySQL Cluster Edition Instance
Maintenance Management Instance
Viewing Instance Monitoring
Adjusting Instance Configuration
Operations for Other Features
Migrate or upgrade to TencentDB for MySQL Cluster Edition
Operation Guide
Use Limits
Operation Overview
Instance Management and Maintenance
Instance Upgrade
CPU Elastic Expansion
Read-Only/Disaster Recovery Instances
Database Proxy
Database Management Center (DMC)
Account Management
Parameter Configuration
Backup and Rollback
Data Migration
Network and Security
Monitoring and Alarms
Log Center
Read-Only Analysis Engine
Tag
Practical Tutorial
Using TencentDB for MySQL to Upgrade MySQL 5.7 to MySQL 8.0
Methods and Instructions for Upgrading from MySQL 5.6 to MySQL 5.7
Cybersecurity Classified Protection Practice for Database Audit of TencentDB for MySQL
Building All-Scenario High-Availability Architecture
Usage Specifications of TencentDB for MySQL
Configuring Automatic Application Reconnection
Impact of Modifying MySQL Source Instance Parameters
Limits on Automatic Conversion from MyISAM to InnoDB
Creating VPCs for TencentDB for MySQL
Enhancing Business Load Capacity with TencentDB for MySQL
Setting up 2-Region-3-DC Disaster Recovery Architecture
Improving TencentDB for MySQL Performance with Read/Write Separation
Migrating Data from InnoDB to RocksDB with DTS
Building LAMP Stack for Web Application
Building Drupal Website
Calling MySQL APIs in Python
The primary and secondary instances have inconsistent query data
White Paper
Performance White Paper
Security White Paper
Troubleshooting
Connections
Performance
Instance Data Sync Delay
Failure to Enable Case Insensitivity
Failure to Obtain slow_query_log_file via a Command
API Documentation
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
FAQs
Related to Selection
Billing
Backup
Rollback
Connection and Login
Parameter Modifications
Instance Upgrade
Account Permissions
Performance and Memory
Ops
Data Migration
Features
Console Operations
Logs
Event
Database audit
Instance Switch Impact
API 2.0 to 3.0 Switch Guide
Service Agreement
Service Level Agreement
Terms of Service
Reference
Standards and Certifications
Contact Us
Glossary

Renewal

PDF
Focus Mode
Font Size
Last updated: 2026-03-20 17:15:37
Yearly/monthly subscription instances will not run normally upon expiration. If you need to continue using them, you can renew them within the specified date. If you fail to renew in time, your TencentDB for MySQL instance resources will be automatically released, and your data will be deleted. This document introduces the description and operation related to instance renewal of TencentDB for MySQL.
Note:
Downtime and data deletion risks exist after the instance expires. Renew it promptly to avoid affecting your business.
If a terminated or returned yearly/monthly subscription instance is restored from the recycle bin, it cannot be terminated or returned again within 30 minutes. If you need to terminate or return the instance, perform the operation 30 minutes after it has been restored.

Prerequisites

Renewal instances should be yearly/monthly subscription instances. Pay-as-you-go instances currently do not involve expiration and renewal.

Renewal Method

You can renew instances either automatically or manually to ensure data integrity. For manual renewal, you need to periodically renew instances to extend their usage time. Automatic renewal saves you the trouble of periodic manual renewal, and helps avoid affecting the use of instances or causing business interruptions due to forgetting to renew them.

Automatic Renewal Instructions

I. Automatic Renewal Rules

Service content: Automatic renewal of TencentDB for MySQL instances.
Automatic renewal cycle: The automatic renewal cycle and mode you have set shall prevail. For example, if you select a cycle of 1 month, the system will automatically renew it for 1 month each time it expires.
Deducted amount: The instance renewal fee is the same as the new instance purchase fee. For instance fees, see the Purchase Page.
Deduction time and method: The system will start deduction on the expiration date of the product. If the deduction fails due to insufficient account balance, the service will be terminated upon expiration.

II. Enabling Automatic Renewal

You can enable automatic renewal via the following operation path.

Enabling Automatic Renewal via the Product Purchase Page

1. Select automatic renewal on the Product Purchase Page. Enable automatic renewal for new instances when purchasing instances. Devices will automatically renew monthly after expiration when the account balance is sufficient.


Enabling Automatic Renewal on the Product Console Page

Note:
For instances that have been set to be automatically renewed monthly, there is no need to set automatic renewal again. Automatically renewed instances can be viewed in the following method.

1. Log in to the MySQL console, select one or more instances in the instance list, and select More > Enable Auto-Renewal above.

2. In the pop-up dialog box, confirm that everything is correct and click OK.
Note:
As shown in the following figure, "The instance will be automatically renewed for 1 month after expiration" in the dialog box means that automatic renewal has been set, and the instance will be automatically renewed for 1 month every time it expires.


Enabling Automatic Renewal via the Expense Center > Renewal Management Page

2. Below the manual renewal items, find one or more TencentDB for MySQL instances for which you want to set automatic renewal. Select them and click Set to Auto-Renewal.

3. In the pop-up window to automatic renewal, confirm product information, select the automatic renewal cycle, and click Confirm.


III. Canceling Automatic Renewal

You can cancel automatic renewal via the following operation path.

Canceling Automatic Renewal via the Product Console Page

1. Log in to the MySQL console and find one or more TencentDB for MySQL instances for which you want to cancel automatic renewal.
2. Select the target instance, and select More > Disable Auto-Renewal above.


Canceling Automatic Renewal via the Website Expense Center > Renewal Management Page

2. Below the automatic renewal items, find one or more TencentDB for MySQL instances for which you want to cancel automatic renewal. Select them and click Set to Manual Renewal.

3. In the pop-up window to set to manual renewal, confirm product information and click Confirm.

IV. Modifying the Automatic Renewal Cycle

Modifying the Automatic Renewal Cycle via the Website Expense Center > Renewal Management Page

2. Below the automatic renewal items, find one or more TencentDB for MySQL instances for which you want to modify the automatic renewal cycle. Select them and click Modify auto-renewal period.

3. In the pop-up window to modify the automatic renewal cycle, modify the automatic renewal cycle of the instance and click OK.

V. Managing Automatic Renewal

Managing Automatic Renewal via the Website Expense Center > Renewal Management Page

On the Renewal Management page, you can also perform other renewal management operations on your instances, such as viewing the renewal status of your instances, setting non-renewal upon expiration, and setting a unified expiry date. For detailed operation instructions, see Renewal Management.

Manual Renewal Instructions

I. Manual Renewal Rules

Service content: Manual renewal of TencentDB for MySQL instances.
Manual renewal time: Within 7 days after the instance expires or at any time before the instance expires, you can manually renew the instance. The minimum renewal duration is 1 month, and the maximum is 3 years. After renewal, the instance expiration time will be extended by the selected duration of the manual renewal from the previous expiration time. For example, if your instance is expected to expire on January 1, 2025, and you perform a manual renewal for 1 month, the actual expiration time will be February 1, 2025.
Deducted amount: The instance renewal fee is the same as the new instance purchase fee. For instance fees, see the Purchase Page.
Deduction time and method: When you perform manual renewal, the page will navigate to the payment interface. The renewal will take effect immediately after payment.

II. Manual Renewal

Manual Renewal via the Product Console Page

Method 1
1. Log in to the MySQL console, select one or more instances in the instance list, and click Renew above.

2. In the pop-up dialog box, select the renewal duration and click OK.
Note:
The renewal duration can be selected as monthly or annually. As shown in the following figure, it represents a renewal for 6 months, indicating that the instance will be renewed for another 6 months after expiration. After 6 months, the instance will need to be renewed again.

3. On the order verification page, confirm that everything is correct and then pay for the order.
Method 2
Log in to the MySQL Console. In the instance list, click Instance ID to go to the instance details page. Click Renew after the Expiration Time.


III. Managing Manual Renewal

Managing Manual Renewal via the Website Expense Center > Renewal Management Page

On the Renewal Management page, you can also perform other renewal management operations on your instances, such as viewing the renewal status of your instances, setting non-renewal upon expiration, and setting a unified expiry date. For detailed operation instructions, see Renewal Management.

Help and Support

Was this page helpful?

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

Feedback