Tencent Cloud

Billing Overview

Last updated: 2024-08-23 09:54:52

This document describes all the billable items of TDSQL-C for MySQL.
Billable items
Billable Item
Description
Charge Applicable
Supported Billing Mode
Compute node
Compute nodes include read-write nodes and read-only nodes.
Such fees are subject to the node region, specification, and usage duration.
Note：
Currently, the LibraDB engine for read-only instances does not support the Serverless billing mode.
Charged upon purchase/use
Monthly subscription
Pay-as-you-go
Serverless
Storage space
Storage space refers to the space used by data files, index files, log files (redo logs, undo logs, slow logs, and error logs), and temporary files. Fees are charged for the used storage space.
Such fees are subject to the data volume and storage duration.
Note:
Data files are stored in three replicas for strong data consistency and reliability, and fees are charged based on the data volume in only one replica.

Charged upon purchase/use
Monthly subscription
Pay-as-you-go
Backup storage space
Backup files take up the storage space. Backup modes include automatic and manual, and backup objects include log and data. Storage space used by all backup files incurs fees under this billable item.
Such fees are subject to the capacity and retention duration.
Free of charge for now

Pay-as-you-go
Database audit
TDSQL-C for MySQL provides database audit capabilities, which can record accesses to databases and executions of SQL statements to help you manage risks and improve the database security.
You need to pay for database audit only after it is enabled.

Charged upon purchase/use


Pay-as-you-go
Supported billing modes
Instance Mode
Billing Mode
Supported Engine
Billing Mode
Use Cases

Provisioned Resource
(Provisioned Specified Specs)
Monthly subscription
TXSQL/LibraDB
Prepaid Billing. You need to pay the fees when creating an instance.
It is more cost-effective in the long term for businesses with stable needs than pay-as-you-go billing. Moreover, the longer a service is purchased, the less it costs.
﻿
Pay-as-you-go
TXSQL/LibraDB
Postpaid. You can apply for resources for on-demand use and will be charged based on the actual usage of resources upon settlement.
It is suitable for instantaneously fluctuating businesses. In this mode, instances can be released immediately after the use to save costs.
Serverless
Compute: Number of CCUs
Storage: usage in GB
TXSQL
Compute and storage resources are billed separately: compute resources are billed by the number of CCUs, while storage resources are billed by the usage in GB. The billing system calculates the usage by second and settles fees by hour.
It is suitable for business scenarios with low frequency and uncertain load such as development and testing.
Note:
A serverless instance will start with the minimum CPU specification during initialization and will be downgraded if there are no requests in ten minutes after startup. Therefore, even if you don't use the instance after purchasing it, compute node fees will be charged for ten minutes.
TDSQL-C Compute Unit (CCU) is the computing and billing unit for the Serverless Edition. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size.
﻿
Resource pack
TXSQL
Prepaid resource packs include compute resource pack and storage resource pack, which can be used to deduct the storage and compute resources used by the serverless cluster.
It is suitable for the scenarios that require flexible management of compute and storage resources and upfront payments based on actual usage, such as short-term projects, applications with fluctuating traffic, large-scale data processing.

tencent cloud

Recent Pages

Billing Overview

Billable items

Supported billing modes

Was this page helpful?

Was this page helpful?

Billable Item	Description	Charge Applicable	Supported Billing Mode
Compute node	Compute nodes include read-write nodes and read-only nodes. Such fees are subject to the node region, specification, and usage duration. Note： Currently, the LibraDB engine for read-only instances does not support the Serverless billing mode.	Charged upon purchase/use	Monthly subscription Pay-as-you-go Serverless
Storage space	Storage space refers to the space used by data files, index files, log files (redo logs, undo logs, slow logs, and error logs), and temporary files. Fees are charged for the used storage space. Such fees are subject to the data volume and storage duration. Note: Data files are stored in three replicas for strong data consistency and reliability, and fees are charged based on the data volume in only one replica.	Charged upon purchase/use	Monthly subscription Pay-as-you-go
Backup storage space	Backup files take up the storage space. Backup modes include automatic and manual, and backup objects include log and data. Storage space used by all backup files incurs fees under this billable item. Such fees are subject to the capacity and retention duration.	Free of charge for now	Pay-as-you-go
Database audit	TDSQL-C for MySQL provides database audit capabilities, which can record accesses to databases and executions of SQL statements to help you manage risks and improve the database security. You need to pay for database audit only after it is enabled.	Charged upon purchase/use	Pay-as-you-go

Instance Mode	Billing Mode	Supported Engine	Billing Mode	Use Cases
Provisioned Resource (Provisioned Specified Specs)	Monthly subscription	TXSQL/LibraDB	Prepaid Billing. You need to pay the fees when creating an instance.	It is more cost-effective in the long term for businesses with stable needs than pay-as-you-go billing. Moreover, the longer a service is purchased, the less it costs.
Provisioned Resource (Provisioned Specified Specs)		Pay-as-you-go	TXSQL/LibraDB	Postpaid. You can apply for resources for on-demand use and will be charged based on the actual usage of resources upon settlement.	It is suitable for instantaneously fluctuating businesses. In this mode, instances can be released immediately after the use to save costs.
Serverless	Compute: Number of CCUs Storage: usage in GB	TXSQL	Compute and storage resources are billed separately: compute resources are billed by the number of CCUs, while storage resources are billed by the usage in GB. The billing system calculates the usage by second and settles fees by hour.	It is suitable for business scenarios with low frequency and uncertain load such as development and testing. Note: A serverless instance will start with the minimum CPU specification during initialization and will be downgraded if there are no requests in ten minutes after startup. Therefore, even if you don't use the instance after purchasing it, compute node fees will be charged for ten minutes. TDSQL-C Compute Unit (CCU) is the computing and billing unit for the Serverless Edition. A CCU is approximately equal to 1 CPU core and 2 GB memory. The number of CCUs used in each billing cycle is the greater of the number of CPU cores used by the database and 1/2 of the memory size.
Serverless		Resource pack	TXSQL	Prepaid resource packs include compute resource pack and storage resource pack, which can be used to deduct the storage and compute resources used by the serverless cluster.	It is suitable for the scenarios that require flexible management of compute and storage resources and upfront payments based on actual usage, such as short-term projects, applications with fluctuating traffic, large-scale data processing.

tencent cloud

Sign Up

Log in

Recent Pages

Billing Overview

Billable items

Supported billing modes

Was this page helpful?

Was this page helpful?