Configure SQL warehouses

This article explains how to configure and manage SQL warehouses using the Databricks SQL UI. This includes how to create, edit, and monitor existing SQL warehouses. You will also learn how to convert existing classic warehouses into serverless warehouses. You can also create SQL warehouses using the SQL warehouse API, or Terraform.

What is a SQL warehouse?

A SQL warehouse is a compute resource that lets you run SQL commands on data objects within Databricks SQL. Compute resources are infrastructure resources that provide processing capabilities in the cloud.

To navigate to the SQL warehouse dashboard, click Endpoints Icon SQL Warehouses in the sidebar. By default, warehouses are sorted by state (running warehouses first), then in alphabetical order.

To help you get started quickly, Azure Databricks creates a small SQL warehouse called Starter Warehouse automatically. You can edit or delete this SQL warehouse.


SQL warehouses have the following requirements:

  • To create a SQL warehouse you must be a workspace admin or a user with unrestricted cluster creation permissions.

  • To manage a SQL warehouse you must be a workspace admin or have the Can Manage permission on the SQL warehouse.

  • For classic or pro SQL warehouses, your Azure account must have adequate vCPU quota. The default vCPU quota is usually adequate to create a serverless SQL warehouse but might not be enough to scale the SQL warehouse or to create additional warehouses. See _. You can request additional vCPU quota. Your Azure account may have limitations on how much vCPU quota you can request. Contact your Azure account representative for more information.

  • Before you can create a serverless SQL warehouse in a region that supports the feature, there may be required steps:

    • If you use an Azure Storage firewall, you may need to add the serverless IP ranges for your region.
    • For serverless SQL warehouses, you must not exceed your account’s serverless quota for each region. Serverless quotas are a safety measure for serverless compute. See Serverless quotas.

Create a SQL warehouse

You can create warehouses using the SQL Warehouses page in the web UI, using the SQL Warehouse API, or Terraform. The default warehouse settings create an efficient and high-performing SQL warehouse, but you can edit some of the settings to fit your workload needs.

To create a SQL warehouse using the web UI:

  1. Click SQL Warehouses in the sidebar.
  2. Click Create SQL Warehouse.
  3. Enter a Name for the warehouse.
  4. Accept the default warehouse settings or edit them. See warehouse settings.
  5. (Optional) Configure advanced options. See Advanced options.
  6. Click Create.
  7. You can then configure warehouse permissions if you’d like.

Your SQL warehouse is now created and started.

Warehouse settings

Creating a SQL warehouse in the UI allows you to update the following settings:

  • Cluster Size represents the size of the driver node and number of worker nodes associated with the cluster. The default is X-Large. To reduce query latency, increase the size.

  • Auto Stop determines whether the warehouse stops if it’s idle for the specified number of minutes. Idle SQL warehouses continue to accumulate DBU and cloud instance charges until they are stopped.

    • Pro and classic SQL warehouses: The default is 45 minutes, which is recommended for typical use. The minimum is 10 minutes.
    • Serverless SQL warehouses: The default is 10 minutes, which is recommended for typical use. The minimum is 5 minutes when you use the UI. Note that you can create a serverless SQL warehouse using the SQL warehouses API, in which case you can set the Auto Stop value as low as 1 minute.
  • Scaling sets the minimum and maximum number of clusters that will be used for a query. The default is a minimum and a maximum of one cluster. You can increase the maximum clusters if you want to handle more concurrent users for a given query. Azure Databricks recommends a cluster for every 10 concurrent queries. For more information, see _.

    In order to maintain optimal performance, Databricks periodically recycles clusters. During a recycle period, you may temporarily see a cluster count that exceeds the maximum as Databricks transitions new workloads to the new cluster and waits to recycle the old cluster until all open workloads have completed.

  • Type determines the type of warehouse. If serverless is enabled in your account, it will be the default. See What are the available warehouse types? for the list.

Advanced options

You can configure the following advanced options by expanding the Advanced options area when you create a new SQL warehouse or edit an existing SQL warehouse. You can also configure these options using the SQL Warehouse API.

  • Tags: Tags allow you to easily monitor the cost of cloud resources used by users and groups in your organization. You specify tags as key-value pairs.

  • Unity Catalog: If Unity Catalog is enabled for the workspace, it is the default for all new warehouses in the workspace. If Unity Catalog is not enabled for your workspace, you do not see this option. For more information about Unity Catalog, see Unity Catalog.

  • Channel: Use the Preview channel to test upcoming features. The preview version lets you try out functionality before it becomes the Databricks SQL standard. You can use it to test your queries and dashboards against upcoming changes.

    Use the release notes to learn what’s in the latest preview version.


Databricks recommends against using a preview version for production workloads. Because only admins can view a warehouse’s properties, including its channel, consider indicating that an SQL warehouse uses a preview version in the warehouse’s name so that users do not inadvertently use it for production workloads.

Start a warehouse

To manually start a stopped SQL warehouse, click Endpoints Icon SQL Warehouses in the sidebar then click the start icon next to the warehouse.

If a SQL warehouse is stopped and you attempt to run a job or query that uses it, Azure Databricks starts the warehouse automatically. A warehouse also restarts automatically if you open a query in the SQL editor that is saved to a stopped warehouse or if you open a dashboard that is saved with a dashboard-level warehouse assigned to it. Auto-restart works for all types of SQL warehouses, including serverless SQL warehouses, which start very quickly.

Manage SQL warehouses

You can choose to manage SQL warehouses using the web UI or the SQL Warehouse API.

  • To stop a running warehouse, click the stop icon next to the warehouse.
  • To start a stopped warehouse, click the start icon next to the warehouse.
  • To delete a warehouse, click the kebab menu Vertical Ellipsis, then click Delete.
  • To edit a warehouse, click the kebab menu Vertical Ellipsis then click Edit.
  • To add and edit permissions, click the kebab menu Vertical Ellipsis then click Permissions. To learn about permission levels, see SQL warehouse access control.

Upgrade a pro or classic SQL warehouse to serverless

To learn about serverless SQL warehouse, see Serverless compute.

  1. Click SQL Warehouses in the sidebar.
  2. In the Actions column, click the vertical ellipsis Vertical Ellipsis then click Upgrade to Serverless.

Monitor a SQL warehouse

To monitor a SQL warehouse, click the name of a SQL warehouse and then the Monitoring tab. On the Monitoring tab, you see the following monitoring elements:

  • Live statistics: Live statistics show the currently running and queued queries, active SQL sessions, the warehouse status, and the current cluster count.
  • Time scale filter: The monitoring time scale filter sets the time range for the query count chart, running cluster chart, and the query history and event log table. The default time range is 8 hours, but you can specify 24 hours, 7 days, or 14 days. You can also click and drag on the bar chart to change the time range.
  • Query count chart: The query count chart shows the number of queries running or queued on the warehouse during the selected time frame.
  • Running clusters chart: The running clusters chart shows the number of clusters allocated to the warehouse during the selected time frame. During a cluster recycle, this count may temporarily exceed configured maximum.
  • Query history table: The query history table shows all of the queries active during the selected time frame, their start time and duration, and the user that executed the query. You can filter the queries by user, query duration, query status, and query type.


The cluster count can be greater than one only if scaling is enabled and configured.

Warehouse sizing and autoscaling behavior

For information on how classic and pro SQL warehouses are sized and how autoscaling works, see SQL warehouse sizing, scaling, and queuing behavior.