MetricSign
EN|NLRequest Access
Medium severityresource

Power BI Refresh Error:
SQL_ANALYTICS_WAREHOUSE_SUSPENDED

What does this error mean?

A Databricks SQL warehouse reached its auto-suspend timeout and stopped, causing subsequent connection attempts and queries to wait for cold start or fail with a suspended-state error.

Common causes

  • 1The warehouse idle timeout triggered auto-suspend during a scheduled pipeline window
  • 2The warehouse was manually stopped by an admin
  • 3A resource monitor suspended the warehouse to control costs
  • 4The query arrived before the warehouse finished its cold-start sequence

How to fix it

  1. 1Step 1: Check the warehouse state in Databricks SQL Warehouses — start it manually if needed.
  2. 2Step 2: Increase the auto-suspend timeout for the warehouse to reduce cold-start frequency during active periods.
  3. 3Step 3: For predictable load windows, configure a warehouse schedule to pre-start before the first query.
  4. 4Step 4: Consider using Serverless SQL Warehouses, which start significantly faster than Classic or Pro warehouses.
  5. 5Step 5: Add retry logic in orchestration tools to wait for the warehouse to start rather than failing immediately.

Frequently asked questions

What is the minimum auto-suspend setting for a Databricks SQL warehouse?

The minimum configurable idle timeout is 10 minutes. For frequently used warehouses, setting 30-60 minutes balances cost and availability.

Are Serverless warehouses faster to start than Pro or Classic?

Yes — Serverless SQL Warehouses typically start in under 5 seconds, compared to 1-3 minutes for Classic or Pro warehouses.

Other resource errors