Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2026 02:30 AM - edited 09-04-2026 02:32 AM
Hello, @gowri_databrick
Here is a quick example that makes it super clear.
Try creating a new notebook and changing the attached compute resource to Serverless SQL Warehouse.
You'll immediately get an error saying:
"SQL Warehouse only support SQL and Markdown cells. Cells of other language types will fail during execution."
In other words, it's an environment strictly configured to run only SQL! (and Markdown)
As others have mentioned in their replies, Databricks has different compute options depending on your purpose. It's easiest to think of it like this:
"I'm mostly going to use SQL!" -> Use SQL Warehouse.
"I want to work in notebooks using both Python and SQL!" -> Use All-purpose compute.
"I need to run scheduled jobs!" -> Use Job compute.
While we're on the topic, let me also explain how to create one.
You just go to "Workspace -> Compute -> SQL warehouses tab and click the [Create SQL warehouse]"
(Of course, not just anyone can do this—you need to have cluster creation permissions!)
Once you click it, the settings screen pops up. Here are the main options:
(Image source: Databricks Documentation : https://docs.databricks.com/aws/en/compute/sql-warehouse/create )
(1) Name: Just name your SQL warehouse.
(2) Cluster size: You can choose sizes from 2X-Small to 4X-Large, just like t-shirt sizes. The larger the size, the faster it processes heavy and complex queries. If it's just for development, starting with 2X-Small or Small is usually more than enough. ++ You'll see the term "DBU" on the screen. Think of it as a billing coin or metric Databricks uses to measure how much compute resource you've consumed. You can get a rough feel for it by checking the Databricks pricing page.
(3) Auto stop: A must-have setting that automatically turns off the warehouse (and stops the billing) if no one uses it for a specified time.
(4) Scaling: By setting Min-Max values, it will automatically scale out when the number of concurrent users increases.
(5) Type: There are 3 options—Serverless, Pro, and Classic.
- Serverless: Literally turns on super fast (in seconds). Databricks manages all the backend infrastructure, and it includes all the optimization features. It's the highly recommended "Best Practice" choice.
- Pro: The compute resources are created inside your own cloud account, so it takes a few minutes to start up. You might wonder, "Why use this then?" It's used when Serverless isn't supported in your region yet, or when your company's security policies require the compute to be spun up inside your own cloud network (VPC/VNet).
- Classic: You can think of this as an entry-level option that provides basic performance without the advanced optimization features.
+ Recently, they also introduced a new SQL warehouse type called "Lakehouse Real-Time," which is capable of sub-second latency. (Though this is still in Beta!)
+ If you're curious about the detailed optimization features I briefly skipped over (like Predictive IO or Intelligent Workload Management), please refer to the official docs below.
Hope this helps!