Help Center/ DataArts Fabric/ Billing/ Overview/ SQL Billing Overview
Updated on 2025-12-19 GMT+08:00
View PDF
Share

SQL Billing Overview

This section provides a quick overview of Fabric SQL's billing modes, key billing items, and other essential information.

Billing Modes

Fabric SQL offers two serverless, pay-per-use billing modes: Pay By Resource and Pay By Query.

  • Pay By Resource: You are billed based on the number of warm-up resources allocated to your SQL endpoints multiplied by its runtime. This mode allows you to enable or disable resources with per-second billing and hourly settlement. Bills are generated at the end of each hour and deducted from your account balance. It ensures dedicated resource usage and high SLA guarantees.
  • Pay By Query: You are billed based on the SQL compute unit hours consumed when running queries on shared public endpoints. Similar to Pay By Resource, it features per-second billing and hourly settlement. Bills are issued at the end of each hour and deducted from your account balance. This mode involves shared resource usage with moderate SLA levels.

For details about the billing differences, see Table 1.

Table 1 Billing modes of DataArts Fabric SQL

Billing Mode

Payment Method

Billing Cycle

Applicable Billing Item

Pay By Resource

Postpaid. Billed based on the runtime of warm-up resources purchased.

Hourly billing based on the runtime of warm-up resources. A charge detail record (CDR) is generated hourly.

SQL warm-up resources

Pay By Query

Postpaid. Billed based on the SQL compute unit hours consumed during query execution at public endpoints.

Hourly billing based on SQL compute unit hours used. A CDR is generated hourly.

SQL compute unit hours

Billing Items

DataArts Fabric SQL is billed based on the resources used in actual service scenarios. For detailed billing items and descriptions, refer to Table 2.

Table 2 Billing items

Billing Item

Description

SQL warm-up resources

Charges are calculated based on the runtime of warm-up resources created for your SQL endpoint. Usage is measured as (number of warm-up resources × runtime) and reported per second.

SQL compute unit hours

Charges are calculated based on the number of SQL compute units consumed during query execution at public endpoints multiplied by the duration. Usage is reported per second every hour.

Bills

On the top navigation bar of the console, click Billing. In the left navigation pane of the Billing Center console, choose Billing > Transaction and Detailed Bills to view bill details. For details, see Bills.

Arrears

See Expiration and Renewal for details.

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 Example

The following prices are for reference only. For the actual prices, see pricing details for each service.

  1. SQL warm-up resources

    SQL warm-up resources are billed per second in pay-per-use mode. The hourly price is available on the DataArts Fabric product pricing details page. You can divide this by 3600 to obtain the per-second rate.

    Example: Consider a fabric.sql.dcu.std instance priced at USD 0.155 per core-hour. If you buy 50 DCU warm-up resources with per-per-use billing, 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) x 50 x 30 x 60 = USD 3.875.
    • For 1 hour of runtime: (0.155/3600) x 50 x 60 x 60 = USD 7.75.
  2. SQL CU hours

    SQL compute unit hours are billed per second in pay-per-use mode. The hourly price is listed on the DataArts Fabric product pricing details page. You can divide this by 3600 to obtain the per-second rate.

    Example: For a fabric.sql.query flavor instance priced at USD 0.2015 per core-hour, the fee is calculated based on the DCU duration (core-second) 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 DCU duration for this hour is 12.2 seconds (2.4 + 3.5 + 6.3). The fee is: (0.2015/3600) x 12 = USD 0.00067.
    • From 10:00 to 11:00, Statement 1 is executed but canceled mid-execution, consuming 18 seconds of the DCU duration. Canceled SQL statements are also charged. The fee is: (0.2015/3600) x 18 = USD 0.0010075.
Parent topic: Overview