Dear DataWorks users,
To better meet your task scheduling needs and improve the utilization efficiency of scheduling resources, DataWorks will switch SQL nodes of certain database types from compute tasks to scheduling tasks.
1. After SQL nodes are switched to scheduling tasks, only scheduling fees are charged. Compute fees are no longer charged, which significantly reduces your costs.
2. The switch is seamless and does not affect any task nodes that are running.
The database types of SQL nodes added in this switch are: MySQL, SQL Server, Oracle, DRDS, PolarDB for MySQL, PolarDB for PostgreSQL, MariaDB, Redshift, SAP HANA, Vertica, DM, KingbaseES, OceanBase, DB2, and GBase 8a.
The switch will be carried out from June 1, 2026 to June 12, 2026 (UTC+8). After the switch is complete, the above node types will no longer incur compute fees in all regions, and only scheduling instance fees will be charged.
During the switch period from today to June 12, 2026, regions that have already been switched will no longer incur compute fees, and only scheduling instance fees will be charged.
When SQL statements are executed by using a data source or compute resource, the billing of the engine product is charged by the corresponding cloud product. The fees are reflected in the bills of the corresponding engine products (such as MaxCompute and Hologres) and are not included in the DataWorks platform service fees. For details, see Billing overview.
After nodes are switched to scheduling tasks, we recommend that you adjust the scheduling concurrency configuration based on your task volume. If you have a large number of SQL node tasks, we recommend that you increase the scheduling concurrency to achieve a better scheduling experience. The specific rules are as follows:
Pay-as-you-go resource groups:
The default scheduling concurrency remains at 50.
The maximum scheduling concurrency can be adjusted to 200.
If this still cannot meet your needs, we recommend that you switch to a subscription resource group.
Subscription resource groups:
The default scheduling concurrency remains at 50.
Submit a ticket to contact technical support for adjustment: the maximum scheduling concurrency can be adjusted to 200 + (CU - 50) × 4, with an upper limit of 500.
If you have any questions about scheduling concurrency adjustment or fee changes, submit a ticket to contact technical support.
Thank you for your support and understanding of DataWorks.