What causes SQL_WAREHOUSE_NOT_FOUND?

A BI tool or downstream connector has a hard-coded SQL Warehouse ID that was deleted during workspace cleanup or migration. The SQL Warehouse was created in a different Databricks workspace than the one the connection is pointing to. An auto-stop SQL Warehouse was permanently deleted rather than simply stopped, but the external tool retains the old warehouse ID

How do I fix SQL_WAREHOUSE_NOT_FOUND?

Step 1: List available SQL Warehouses via the Databricks UI (SQL > SQL Warehouses) or the REST API (GET /api/2.0/sql/warehouses) and locate the correct warehouse ID.. Step 2: Update all connection strings, BI tool configurations, and job parameters to reference the valid warehouse ID.. Step 3: If the warehouse was deleted intentionally, create a new one of the appropriate size and update all references.. Step 4: For automated pipelines, store the warehouse ID as an environment variable or Databricks secret so it can be updated without code changes.

High severityconfiguration

Power BI Refresh Error:
SQL_WAREHOUSE_NOT_FOUND

What does this error mean?

A DBSQL query or API call referenced a SQL Warehouse by ID or name that does not exist in the workspace, typically because it was deleted, renamed, or belongs to a different workspace.

Common causes

1A BI tool or downstream connector has a hard-coded SQL Warehouse ID that was deleted during workspace cleanup or migration
2The SQL Warehouse was created in a different Databricks workspace than the one the connection is pointing to
3An auto-stop SQL Warehouse was permanently deleted rather than simply stopped, but the external tool retains the old warehouse ID

How to fix it

1Step 1: List available SQL Warehouses via the Databricks UI (SQL > SQL Warehouses) or the REST API (GET /api/2.0/sql/warehouses) and locate the correct warehouse ID.
2Step 2: Update all connection strings, BI tool configurations, and job parameters to reference the valid warehouse ID.
3Step 3: If the warehouse was deleted intentionally, create a new one of the appropriate size and update all references.
4Step 4: For automated pipelines, store the warehouse ID as an environment variable or Databricks secret so it can be updated without code changes.

Frequently asked questions

Can a SQL Warehouse be stopped vs. deleted?

Yes. Stopped warehouses still appear in the API and can be restarted. SQL_WAREHOUSE_NOT_FOUND means the warehouse is fully deleted, not just stopped or scaling down.

How do I find the correct warehouse ID?

Run GET /api/2.0/sql/warehouses via the Databricks REST API, or navigate to SQL > SQL Warehouses in the workspace UI and copy the ID from the warehouse's URL.