- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Function Overview
- Kernel Version Notes
- Permissions Management
-
Instance Management
- Instance Statuses
- Buying a DDM instance
- Splitting Read-only and Read-Write Services
- Changing Node Class
- Scaling Out a DDM Instance
- Scaling In a DDM Instance
- Restarting a DDM Instance or an Instance Node
- Deleting Pay-per-Use Instances
- Reloading Table Data
- Changing a Parameter Template
- Modifying Parameters of a DDM Instance
- Rolling Back the Version of a DDM Instance
- Upgrading the Version of a DDM Instance
- Upgrading the DDM Engine and OS
- Connection Management
- Schema Management
- Shard Configuration
- Data Nodes
-
Parameter Template Management
- Instance Parameters
- Creating a Parameter Template
- Modifying a Custom Parameter Template
- Comparing Two Parameter Templates
- Viewing Parameter Change History
- Replicating a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Account Management
- Backups and Restorations
-
Data Migration
- Overview
- Migration Evaluation
- Scenario 1: Migrating Data from an On-Premises MySQL Instance to DDM
- Scenario 2: Migrating Data from a Third-Party Cloud MySQL Instance to DDM
- Scenario 3: Migrating Data from an ECS-hosted MySQL Instance on Huawei Cloud to DDM
- Scenario 4: Exporting Data from a DDM Instance
- Scenario 5: Migrating Data from Heterogeneous Databases to DDM
- Scenario 6: Migrating Data from Huawei Cloud RDS for MySQL to DDM
- Session Management
- Slow Queries
- Monitoring and Alarm Reporting
- Task Center
- Tags
- Auditing
-
SQL Syntax
- Introduction
- DDL
- DML
- Online DDL
- Functions
- Unsupported Objects and Use Constraints
- Supported SQL Statements
- Global Sequence
- Database Management Syntax
- Advanced SQL Functions
- Quotas
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs (Recommended)
-
DDM Instances
- Buying a DDM instance
- Querying DDM Instances
- Querying Details of a DDM Instance
- Modifying the Name of a DDM Instance
- Changing the Security Group of a DDM Instance
- Deleting a DDM Instance
- Restarting a DDM Instance
- Reloading Table Data
- Scaling Out a DDM Instance
- Scaling in a DDM instance
- Modifying the Read Policy of the Associated DB Instance
- Synchronizing Data Node Information
- Querying Nodes of a DDM Instance
- Querying Details of a DDM Instance Node
- Querying Parameters of a Specified DDM Instance
- Modifying Parameters of a DDM Instance
- Querying DDM Engine Information
- Querying DDM Node Classes Available in an AZ
- Changing the Node Class of a DDM Instance
- Obtaining the Instance Group Information
- Creating an Instance Group
- Schemas
- Accounts
- Monitoring
- Session Management
- Application Examples
-
DDM Instances
- Permissions Policies and Supported Actions
- Appendix
- SDK Reference
-
Best Practices
- Overview
- Formulating Sharding Rules
- Determining the Number of Shards in a Schema
- Using Broadcast and Unsharded Tables
- Transaction Models
- SQL Standards
- Migrating an Entire RDS Database to DDM
- Migrating an Entire MyCat Database to DDM
- Accessing DDM Using a JDBC Connection Pool
- Logging In to a DDM Instance Using Navicat
- Migrating Data from RDS for MySQL to DDM Using DRS
- Sharding Database and Table Data of an RDS for MySQL Instance
- Performance White Paper
-
FAQs
- General Questions
-
DDM Usage
- How Does DDM Perform Sharding?
- What Do I Do If I Fail to Connect to a DDM Instance Using the JDBC Driver?
- Why It Takes So Long Time to Export Data from MySQL Using mysqldump?
- What Do I Do If a Duplicate Primary Key Error Occurs When Data Is Imported into DDM?
- What Should I Do If an Error Message Is Returned When I Specify an Auto-Increment Primary Key During Migration?
- What Do I Do If an Error Is Reported When Parameter Configuration Does Not Time Out?
- Which Should I Delete First, a Schema or its Associated RDS Instances?
- Can I Manually Delete Databases and Accounts Remained in Data Nodes After a Schema Is Deleted?
- SQL Syntax
-
RDS-related Questions
- Is the Name of a Database Table Case-Sensitive?
- What Risky Operations on RDS for MySQL Will Affect DDM?
- How Do I Handle Data with Duplicate Primary Keys in a Table?
- How Can I Query RDS for MySQL Information by Running Command show full innodb status?
- What Should I Pay Attention to When Selecting RDS for MySQL Instance Specifications?
- Connection Management
- Resource Freezing, Release, Deletion, and Unsubscription
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Function Overview
- Instance Management
-
Parameter Template Management
- Creating a Parameter Template
- Editing a Parameter Template
- Comparing Two Parameter Templates
- Viewing Parameter Change History
- Replicating a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Task Center
- Schema Management
- Account Management
- Backup Management
- Monitoring Management
- Auditing
-
SQL Syntax
- Introduction
- DDL
- DML
- Functions
- Unsupported Items
- Supported SQL Statements
- Global Sequence
- Database Management Syntax
- Advanced SQL Functions
-
FAQs
- General Questions
-
DDM Usage
- How Can I Rectify a Fault in Accessing DDM by Using the JDBC Driver?
- What Version and Parameters Should I Select?
- Why It Takes So Long Time to Export Data from MySQL Using mysqldump?
- How Should I Handle the Duplicate Primary Key Error Occurring After Data Is Imported into DDM?
- What Should I Do If an Error Message Is Returned After I Specify an Auto-Increment Primary Key?
- How Do I Handle the Error Reported When Parameter Configuration Does Not Time Out?
- Which Should I Delete First, Schema or Associated RDS DB Instances?
- Should I Manually Delete Databases and Accounts Remained in the Associated RDS DB Instances After a Schema Is Deleted?
- SQL Syntax
- RDS-related Questions
- Connection Management
-
User Guide (Kuala Lumpur Region)
- Service Overview
- Getting Started
- Function Overview
- Instance Management
-
Parameter Template Management
- Creating a Parameter Template
- Editing a Parameter Template
- Comparing Two Parameter Templates
- Viewing Parameter Change History
- Replicating a Parameter Template
- Applying a Parameter Template
- Viewing Application Records of a Parameter Template
- Modifying the Description of a Parameter Template
- Deleting a Parameter Template
- Task Center
- Schema Management
- Account Management
- Backup Management
- Monitoring Management
- Auditing
-
SQL Syntax
- Introduction
- DDL
- DML
- Functions
- Unsupported Items
- Supported SQL Statements
- Global Sequence
- Database Management Syntax
- Advanced SQL Functions
-
FAQs
- General Questions
-
DDM Usage
- How Can I Rectify a Fault in Accessing DDM by Using the JDBC Driver?
- What Version and Parameters Should I Select?
- Why It Takes So Long Time to Export Data from MySQL Using mysqldump?
- How Should I Handle the Duplicate Primary Key Error Occurring After Data Is Imported into DDM?
- What Should I Do If an Error Message Is Returned After I Specify an Auto-Increment Primary Key?
- How Do I Handle the Error Reported When Parameter Configuration Does Not Time Out?
- Which Should I Delete First, Schema or Associated RDS DB Instances?
- Should I Manually Delete Databases and Accounts Remained in the Associated RDS DB Instances After a Schema Is Deleted?
- SQL Syntax
- RDS-related Questions
- Connection Management
-
API Reference (Kuala Lumpur Region)
- Before You Start
- API Overview
- Calling APIs
-
DDM Instance Management
- Querying DDM Engine
- Querying the Quota of Classes Available in Each AZ
- Creating a DDM Instance
- Querying DDM Instances
- Viewing Details of a DDM Instance
- Modifying the Name of a DDM Instance
- Modifying the Security Group of a DDM Instance
- Deleting a DDM Instance
- Restarting a DDM Instance
- Reloading Table Data
- Scaling Out a DDM instance
- Scaling In a DDM instance
- Modifying the Read Policy of the Associated DB Instance
- Synchronizing DB Instance Data
- Querying Nodes of a DDM Instance
- Querying Details of a DDM Instance Node
- Querying Parameters of a Specified DDM Instance
- Modifying Parameters of a DDM Instance
- Schema Management
- Account Management
- Monitoring Management
- Permissions Policies and Supported Actions
- Appendix
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Pay-per-Use Billing
Pay-per-use billing means you pay nothing up front and are not tied into any contract or commitment.
This section describes the per-pay-use billing rules of DDM.
Application Scenarios
Pay-per-use billing is good for short-term, bursty, or unpredictable workloads that cannot tolerate any interruptions, such as applications for e-commerce flash sales, temporary testing, and scientific computing.
Billing Items
The following table lists billing items of pay-per-use DDM instances.
Billing Item |
Description |
Billing Factor |
Billing Formula |
---|---|---|---|
(Mandatory) DB instance |
Instance specifications include vCPUs, memory, and the number of nodes. |
vCPUs, memory, and number of nodes Instance types of different specifications provide different compute and storage. |
Specifications unit price x Required duration x Number of nodes See Specifications in DDM Pricing Details. |
(Optional) EIP bandwidth |
|
EIPs are required if your resources need to access a public network. Billing items: bandwidth fee, traffic fee, and IP address retention fee. EIP for a pay-per-use DDM instance: billed by bandwidth, traffic, or shared bandwidth. You are also charged for IP reservation if you do not bind the EIP to any instance. |
Billed by fixed bandwidth For details about the unit price, see EIP Pricing Details. |
Assume that you want to purchase a general-enhanced DDM instance with 8 vCPUs and 16 GB of memory in the CN-Hong Kong region. The DDM instance contains two nodes and is available for one month. At the bottom of the Buy DDM Instance page, you can view price details.

The prices in the figure are just examples. The actual prices are those displayed on DDM Price Calculator.
Billed Usage Period
Pay-per-use DDM instance usage is calculated by the second and billed every hour. The billing starts when the DDM instance is launched and ends when the DDM instance is deleted.
It takes a certain time to create a DDM instance. The billing starts from the Completed time on the Instant Tasks page in the task center.
For example, if you purchased a pay-per-use DDM instance at 8:45:30 and deleted it at 8:55:30, you were billed for the 600 seconds from 8:45:30 to 8:55:30.
Billing Examples
Assume that you purchased a pay-per-use DDM instance (instance specifications: 8 vCPUs, 16 GB of memory, and 2 nodes) at 10:00:30 on April 18, 2023 and then deleted it at 10:45:46 on April 18, 2023. The following usage period will be billed:
Usage of 2,716 seconds from 10:00:30 to 10:45:46 (between 10:00:00 and 11:00:00)
The prices displayed in the pricing details are per hour, so you need to divide it by 3,600 to obtain the price for each second and then multiple the per-second price by the total number of seconds.
Resource Type |
Billing Formula |
Unit Price |
---|---|---|
Instance specifications (vCPUs and memory) |
Specifications unit price x Required duration x Number of nodes |
For details, see DDM Pricing Details. |
EIP bandwidth |
Billed by fixed bandwidth If your pay-per-use EIP has no instance bound, you will be billed for the EIP reservation price. |
See EIP Pricing Details. |
shows the billing calculation.
The price in the figure is for reference only. The actual prices are subject to DDM Pricing Details.

Price Change After Specification Change
If you change the instance specifications of a pay-per-use DDM instance, the original order will become invalid and a new order will be placed. You will be billed based on the new instance specifications.
If you change the instance specifications within a given hour, multiple records will be generated. Different records record the billing for different instance specifications.
Assume that you purchased a pay-per-use DDM instance (8 vCPUs | 16 GB) at 9:00:00 and changed the instance specifications to 16 vCPUs | 32 GB at 9:30:00. Two billing records were generated from 9:00:00 to 10:00:00.
- DDM instance (8 vCPUs | 16 GB) usage from 9:00:00 to 9:30:00
- DDM instance (16 vCPUs | 32 GB) usage from 9:30:00 to 10:00:00
Impacts of Arrears
Figure 3 shows the statuses a pay-per-use DDM instance can have throughout its lifecycle. After a DDM instance is purchased, it enters the valid period and runs normally during this period. If your account goes into arrears, the DDM instance enters a grace period and then a retention period.
Arrears Reminder
The system will bill you for pay-per-use DDM instances after each billing cycle ends. If your account goes into arrears, we will notify you by email, SMS, or in-app message.
Impacts of Arrears
If there is no top-up account with sufficient balance and no other payment method configured to pay for the resources used, your account goes into arrears, and the pay-per-use DDM instance enters the grace period. You are still responsible for expenditures generated during the grace period. You can view the charges on the Billing Center > Overview page and pay any past due balance as needed.
If you do not bring your account balance current before the grace period expires, the DDM instance status turns to Frozen and it enters a retention period. You cannot perform any operations on a pay-per-use DDM instance in the Frozen status.
If you do not bring your account balance current before the retention period ends, your instance will be released, and data cannot be restored.
- During the retention period, you cannot access and use your DDM instance but data in the instance will be retained. The retention period for Huawei Cloud International website is 15 days.
- During the grace period, you can access and use only some resources of your DDM instance. The grace period for Huawei Cloud International website is 15 days.
- For details about top-up, see Topping Up an Account.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot