tencent cloud

TencentDB for SQL Server

Release Notes and Announcements
Release Notes
Product Announcements
User Guide
Product Introduction
Overview
Product Architecture
Strengths
Use Cases
Regions and AZs
Major Version Lifecycle Explanation
Features and Differences
Instance Types
Instance Specifications
Storage Types
Common Concepts
Network Environment
License Statement
Purchase Guide
Billing Overview
Product Pricing
Purchase Methods
Renewal Instructions
Payment Overdue
Refund
From Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fees Description
Local Backup Space Billing
Cross-Region Backup Billing
Viewing Bill Details
Getting Started
Creating TencentDB for SQL Server Instance
Connecting to TencentDB for SQL Server Instance
Managing TencentDB for SQL Server Instance
Operation Guide
Constraints and Limits
Usage Specifications and Suggestions
Maintaining Instance
Adjusting Instance Configuration
Read-Only Instance
Network and Security
Account Management
Database Management
Data Security
Parameter Configuration
Monitoring and Alarms
Backup and Restoration 
Log Management
Publish-Subscribe
SSIS
Data Migration (New)
Data Migration (Legacy)
Data Synchronization (DTS) 
Practical Tutorial
TencentDB for SQL Server Methods for Regular Maintenance
TencentDB for SQL Server Optimization of Slow SQL
How to Better Use Tempdb
Cross-Account Backup Restoration
Creating VPC for TencentDB for SQL Server
Connecting Kingdee K/3 WISE to TencentDB for SQL Server
Account Permissions and Permission Control
Enabling and Disabling the CDC Feature
Shrinking a Database
API Documentation
History
Introduction
API Category
Making API Requests
Sales and fee related APIs
Instance Management related APIs
Operation and maintenance management related APIs
Network management related APIs
Account management related APIs
Database management related APIs
Security group management related APIs
Data security encryption related APIs
Parameter configuration related APIs
Extended Event related APIs
Log management related APIs
Read only instance management related APIs
Publish and subscribe related APIs
Backup related APIs
Rollback related APIs
Data migration (cold standby migration) related APIs
SQL Server Integration Services (SSIS) related APIs
Data migration (DTS old version) related APIs
Data Types
Error Codes
FAQs
Overview
Model Selection
Pricing and Selection
Connection and Network
Account and Permission
Backup and Rollback
Data Migration
Publish/Subscribe
Read-Only Instance
Version and Architecture Upgrade
Disk Space and Specification Adjustment
Monitoring and Alarms
Log-Related
Parameter Modification
Features
Performance, Space, and Memory-Related FAQs
Service Agreement
Service Level Agreement
Terms of Service
Performance Evaluation
Performance Test Report
Glossary
Contact Us

Payment Overdue

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-10-11 09:55:32
This document introduces the overdue payment handling mechanism of TencentDB for SQL Server instances. Top up promptly to avoid resource unavailability.
Note:
If you are a customer of a Tencent Cloud partner, the rules regarding resources when there are overdue payments are subject to the agreement between you and the partner.

Overdue Payment Handling Mechanism for Yearly/Monthly Subscription Instances

Introduction of Overdue Payment Warning

During the period from 7 days before instance expiration until the instance release time, the system will send warning messages to the users. Notifications will be sent to the Tencent Cloud account creator, global resource collaborators, and financial collaborators through methods such as email and SMS (the actual receiving method will be based on the users' message center subscription configurations).
For detailed notification mechanisms regarding message reminders from 7 days before instance expiration until instance release time, see Prepaid Billing > Billing Process.

Overdue Payment Handling Mechanism

The system will send users renewal reminder notifications 7 days before the expiration of the instance.
The instance can continue to be used within 7 days after expiration, but renewal is required as soon as possible. The system will send expiration reminder notifications for the instance.
Starting from the 8th day after expiration, the instance will no longer be used and will be moved to the recycle bin. Users can view the instance on the recycle bin page in the console and can still perform renewal operations.
The maximum retention period in the recycle bin is 7 days. If the instance is not renewed after being retained in the recycle bin for 7 days, it will be reclaimed by the system, and the data will be cleared and unrecoverable.
After expiration, the instance has 7 days available for use and 7 days not available for use, giving users a total of 14 days to renew the instance. If there is sufficient balance, instances that are set to automatic renewal will also be renewed as usual.

Overdue Payment Handling Mechanism for Pay-as-You-Go Instances

Note:
When pay-as-you-go instances are no longer used, terminate them promptly to avoid further charges.
Your actual resource consumption may change continuously. Therefore, the balance warning may have a certain degree of error.
During the period of account arrears, recovery operations cannot be performed on the pay-as-you-go instances in the recycle bin.

Introduction of Overdue Payment Warning

The system will charge for pay-as-you-go instances on the hour. When the user's account balance is less than 0, the system will notify the Tencent Cloud account creator, global resource collaborators, and financial collaborators through methods such as email and SMS (the actual receiving method will be based on the users' message center subscription configuration).
For the detailed mechanism of message reminder notifications, see Pay-as-You-Go Billing Explanation > Overdue Payment Handling Mechanism.

Overdue Payment Handling Mechanism

From the moment when your account balance is less than 0:
Within 24 hours, the instance will continue to be used and charged.
After 24 hours, the instance will be automatically shut down, charging is stopped, and it will be removed from the instance list and displayed in the recycle bin.
After automatic shutdown:
Within 7 days of shutdown, if the balance is topped up to be greater than or equal to 0, the instance can be started up, and billing will continue. If your account balance is still less than 0, the instance cannot be started up.
After 7 days of shutdown, if your account balance remains less than 0, the instance will be reclaimed, and all data will be cleared and will not be recovered. When the instance is reclaimed, the system will notify the Tencent Cloud account creator, global resource collaborators, and financial collaborators, through methods such as email and SMS.

Introduction of Topping Up the Account Balance

After the account balance is topped up to positive, the pay-as-you-go instance will become recoverable. At this point, you can go to the recycle bin to perform recovery operations on the instance.
The batch recovery operations can be performed in the recycle bin, but the billing mode of the selected instances should be the same, either in the pay-as-you-go mode or in the yearly/monthly subscription mode.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック