DataArtsFabric SQL Billing Overview
This document describes the billing mode and billing items of DataArtsFabric SQL.
Billing Mode
DataArtsFabric SQL offers two serverless pay-per-use billing modes: Pay By Resource and Pay By Query.
- Pay By Resource: You are billed for the number of warm-up resources created for SQL endpoints, multiplied by their running duration. You can enable and disable the service at any time. Billing is precise to the second and settled hourly. A bill is generated every calendar hour, and fees are deducted from your account balance. This billing mode provides dedicated resources and a high SLA.
- Pay By Query: You are billed based on the SQL computing unit hours consumed by SQL statements running on public endpoints. Billing is precise to the second and settled hourly. A bill is generated every calendar hour, with fees deducted from your account balance. This billing mode uses shared resources and has a medium SLA.
For details about the billing differences, see Table 1 Billing modes of DataArtsFabric SQL.
Billing Mode |
Payment Method |
Billing Cycle |
Applicable Billing Item |
---|---|---|---|
Pay By Resource |
Postpaid. Billed hourly, based on the running duration of purchased warm-up resources. |
A CDR (Charge Detail Record) is generated every hour. |
SQL warm-up resources |
Pay By Query |
Postpaid. Billed hourly, based on the SQL computing unit hours consumed by statements running on public endpoints. |
A CDR is generated every hour. |
SQL computing unit hours |
Billing Items
DataArtsFabric SQL is billed based on the resources used in actual service scenarios. For details about the billing items, see Table 2.
Billing Item |
Billing Description |
---|---|
SQL warm-up resources |
Billed on a pay-per-use basis, this item charges for the running duration of warm-up resources created for SQL endpoints. Usage is calculated by multiplying the actual number of warm-up resources by their running duration, with usage reported per second. |
SQL computing unit hours |
Billed on a pay-per-use basis, this item charges for the number of SQL computing unit resources consumed by SQL statements running on public endpoints, multiplied by their usage duration. Usage is reported per second and aggregated every calendar hour. |
Bills
On the top navigation bar of the console, click Billing. In the left navigation pane of the Billing Center console, choose Bills.
to view bill details. For details, seeArrears
For details, see Expiration and Renewal.
Stopping Billing
If you no longer need to use your cloud services, you can unsubscribe from or delete them to stop the billing. For details, see Stopping Billing.
Billing Examples

The following prices are for reference only. For the actual prices, see pricing details for each service.
- SQL warm-up resources
SQL warm-up resources are billed per second in pay-per-use mode. The hourly price is available in the DataArtsFabric product price details; divide this by 3600 to obtain the per-second rate.
Example: Consider a fabric.sql.dcu.std flavor instance priced at 0.155 USD/core/hour. If you provision fifty warm-up resources, the cost is calculated by multiplying the number of resources by the actual running duration (billed to the second).
- For 30 minutes of runtime: (0.155/3600)*50*30*60=3.875 USD.
- For 1 hour of runtime: (0.155/3600)*50*60*60=7.75 USD.
- SQL Computing Unit (CU) hours
SQL computing unit hours are billed per second in pay-per-use mode. The hourly price is listed in the DataArtsFabric product price details; divide this by 3600 to obtain the per-second rate.
Example: For a fabric.sql.query flavor instance priced at 0.597 USD/core/hour, the fee is calculated based on the DPU (Data Processing Unit) duration (core-seconds) consumed by running SQL statements, billed per second.
- From 9:00 to 10:00, three SQL statements are executed: Statement 1 (2.4 seconds), Statement 2 (3.5 seconds), and Statement 3 (6.3 seconds). The total DPU duration for this hour is 12.2 seconds. The fee is:(0.2015/3600)*12 =0.00067 USD.
- From 10:00 to 11:00, Statement 1 is executed but canceled mid-execution, consuming 18 seconds of DPU duration. Canceled SQL statements are also charged. The fee is: (0.2015/3600)*18=0.0010075 USD.
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