# Underuse of serverless for short or interactive workloads Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/underuse-of-serverless-for-short-or-interactive-workloads Many organizations continue running short-lived or low-intensity SQL workloads - such as dashboards, exploratory queries, and BI tool integrations - on... By: Nicole Boyd Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Underuse of Serverless for Short or Interactive Workloads The short version Many organizations continue running short-lived or low-intensity SQL workloads - such as dashboards, exploratory queries, and BI tool integrations - on traditional clusters. [Nicole Boyd](https://www.linkedin.com/in/nicolecboyd/) Managing Consultant - FinOps @ Capgemini Invent Databricks service [Databricks SQL](https://www.pointfive.co/efficiency-hub/cloud-services/databricks-sql) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0225 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. This leads to idle compute, overprovisioning, and high baseline costs, especially when the clusters are always-on. Databricks SQL Serverless is optimized for bursty, interactive use cases with auto-scaling and pay-per-second pricing, making it better suited for this class of workloads. Failing to migrate to serverless for these patterns results in unnecessary cost without performance benefit. ## Billing model The pricing dimensions that drive this cost. Serverless SQL compute is billed in DBUs based on the size of the SQL warehouse, for as long as the warehouse is running rather than only while queries execute. Idle time is still billed until Auto Stop shuts the warehouse down, but serverless allows a short Auto Stop setting (default 10 minutes, as low as 5 minutes in the UI or 1 minute via the API) and scales automatically based on demand. Continuing to use traditional job or all-purpose clusters for low-throughput SQL workloads results in persistent infrastructure costs that serverless options are purpose-built to minimize. ## How to detect 4 checks to find it in your estate. - Identify SQL warehouses (classic or pro) or clusters supporting dashboard or ad-hoc workloads with long idle periods between executions - Review query duration and frequency - flag warehouses that are infrequently used or support low-throughput workloads - Check whether teams are using dedicated clusters for interactive BI tools (e.g., Power BI, Tableau) - Look for cost spikes associated with idle or underutilized SQL clusters versus expected user interaction volume ## How to fix 4 ways to remove the waste. - Migrate lightweight SQL workloads and dashboards to Databricks SQL Serverless - Enable serverless for high-concurrency, low-compute scenarios where persistent compute isn't needed - Set policies or guidelines to default to serverless for interactive workloads unless specific performance reasons require otherwise - Educate data teams on the appropriate use cases for serverless versus provisioned clusters ## Documentation Vendor references for pricing and configuration. - [SQL warehouse types docs.databricks.com](https://docs.databricks.com/aws/en/compute/sql-warehouse/warehouse-types) - [Databricks Lakehouse Pricing databricks.com](https://www.databricks.com/product/pricing/databricks-lakehouse) - [Create a SQL warehouse docs.databricks.com](https://docs.databricks.com/aws/en/compute/sql-warehouse/create) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Databricks SQL CER-0220 ### [Inefficient Query Design in Databricks SQL and Spark Jobs](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-query-design-in-databricks-sql-and-spark-jobs) Many Spark and SQL workloads in Databricks suffer from micro-optimization issues - such as unfiltered joins, unnecessary shuffles, missing broadcast joins, and repeated scans of uncached data. These problems increase compute time and... Compute - Databricks SQL CER-0522 ### [Long or Disabled Auto Stop on Databricks SQL Warehouses](https://www.pointfive.co/efficiency-hub/inefficiencies/long-or-disabled-auto-stop-on-databricks-sql-warehouses) A Databricks SQL warehouse keeps running after its last query until its Auto Stop timer expires, and Databricks states that idle SQL warehouses continue to accumulate DBU and cloud instance charges until they are stopped. For typical use... Compute - Databricks SQL CER-0521 ### [Oversized Databricks SQL Warehouses](https://www.pointfive.co/efficiency-hub/inefficiencies/oversized-databricks-sql-warehouses) A Databricks SQL warehouse's cluster size sets the driver instance and the number of workers in each of its clusters, from 2X-Small with one worker up to 5X-Large with 512, doubling at each step. The warehouse bills for that size for every... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.