Databricks releases, every cloud
- New SQL editor default enablement and legacy SQL editor retirement Coming soon
New SQL editor becomes default in May, legacy editor retires in July.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Databricks SQL version 2026.10 is now available in Preview
Fixes observation metric errors, optimizes Unity Catalog writes, and uses session timezone for timestamp partitions.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Search in metric views fix
Now returns correct results across paginated results and supports filtering by display name.
- Lakebase databases as Databricks Apps resources
Replaces manual database configuration, requires Lakebase setup.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - 5X-Large SQL warehouse size (Beta)
Available in all supported regions, controlled from Previews page.
AWS, read it on their docsAzure, read it on their docsGCP, read it on their docsSAP(not on this cloud) - Lakebase updates: OAuth role management and budget policies and tags
Creates OAuth roles via UI or REST API, and adds budget policies and custom tags to projects.
- Run the change, do not just read it. Hands-on labs in your own Databricks workspace, graded when you submit. Browse labs
- Lakebase updates: OAuth role management, budget policies and tags, and Lakehouse sync
Creates OAuth roles via UI or REST API, and replicates Postgres tables to Unity Catalog Delta tables.
- New Lakebase instances include autoscaling by default
Autoscaling is on by default for new instances, applies to UI, API, Terraform, and SDK creations.
- Serverless compute is enabled by default
Eligible Google Cloud workspaces are affected, account admins no longer need to manually enable it.
- Serverless compute now available for IRAP and Canada Protected B workloads on Azure Databricks
Requires environment version 5 to be enabled.
- Lakebase is now generally available with compliance security profile
Requires HIPAA, C5, TISAX, or None compliance standard.
AWS, read it on their docsAzure, read it on their docsGCP(not on this cloud)SAP, read it on their docs - Lakebase is now generally available on Azure
Adds autoscaling compute and scale-to-zero to 11 new Azure regions.
- Lakebase now available in three additional regions
Adds Canada Central, Europe London, and South America São Paulo regions.
- Lakebase now includes high availability
Pairs primary compute with 1-3 secondary instances across zones, automatically promoting a secondary if primary fails.
- Version 18.0
Upgrades Redshift JDBC driver to 2.1.0.28, adds SQL window functions to metric views.
- Serverless environment version 5 is now available
Includes CPU and GPU versions.
- Change to use_case field in VPC endpoint API responses Coming soon
Changes from WORKSPACE_ACCESS to GENERAL_ACCESS, see API docs for details.
- Databricks SQL version 2025.40 is rolling out in Current
Replaces version 2025.39, requires no setup changes.
- Get this table by email. One Monday mail covering the week, filtered to the clouds and products you run. Weekly digest
- Databricks SQL version 2025.40 is now available in Preview
Adds SQL scripting with procedural logic and expands parameter markers and IDENTIFIER clause support.
- Serverless compute now available for compliance standards
Adds HITRUST, PCI-DSS, TISAX, and UK Cyber Essentials Plus support.
- Lakebase now available on Azure (Beta)
Lakebase on Azure offers autoscaling compute and scale-to-zero. Supported regions include eastus2, westeurope, and westus.
- New GCP regions support serverless compute
Available in me-central1 and southamerica-east1 regions.
- Serverless workspaces are now generally available
Come pre-configured with serverless compute and default storage.
- Lakebase is now generally available
Includes autoscaling and point-in-time recovery.
- You can now use custom base environments for Python, Python Wheels, and notebook tasks in serverless jobs
Defined with YAML files, they support Python, Python wheel, and notebook tasks.
- Manage Lakebase from the Lakebase App
Replaces Compute tab navigation in Lakehouse UI, accessed via apps switcher.
- Connect to Lakebase from the SQL editor with read-write access
Supports full read-write access, see documentation for setup.
- Lakebase metrics dashboard
Monitors system and database health with metrics like RAM and CPU usage.
- Flexible node types are now generally available
Falls back to alternative instance types when specified type is unavailable, improving launch reliability.
- Lakebase ACL support
Grants CAN CREATE or CAN MANAGE permissions from project settings.
- Serverless compute is now available in Azure China North 3
Available for notebooks, jobs, pipelines, and SQL warehouses.
- Serverless workspaces are now available in new GCP regions
Available in most GCP regions, see documentation for list.
- Lakebase now in Public Preview
Introduces autoscaling compute and database branching on AWS. Free until January 2026.
- Serverless compute is now available in new regions
Added to Australia Southeast, Canada Central, Mexico Central, Norway East, and South Africa North regions.
- Databricks SQL version 2025.35 is rolling out in Current
Includes new features, see documentation for details.
- Databricks SQL alerts are now in Public Preview
Offers a new editing experience, replacing the previous version.
- Convert foreign tables to Unity Catalog managed or external tables (Public Preview)
Requires Databricks Runtime 17.0 LTS or above. Uses ALTER TABLE SET MANAGED or SET EXTERNAL.
- SQL Editor visualization fix
Tooltips now display in front of the legend.
- Serverless notebook tasks can now use jobs environment
Replaces inherited serverless environment with configurable job environment.
- Databricks SQL version 2025.35 is now available in Preview
Adds EXECUTE IMMEDIATE constant expressions and LIMIT ALL for recursive CTEs.
Headlines, dates and product areas are Databricks' own, and every item links to the note it came from. The one-line summaries are ours.