Skip to content
brickster.aibrickster.ai
ServerlessChangelog · September 2026

Practitioners weighed serverless compute limitations as system query history reached general availability.

Databricks marked general availability for the system.query.history table, expanding observability across SQL warehouses and cluster workloads [1]. Developer workflows also emphasized serverless integration, such as guides configuring SSH tunnels to run code from local IDEs like VS Code on serverless runtimes [12]. Operational setup guides addressed automated permission management via the Databricks SDK [15] and quick workspace provisioning on Azure [9].

Community discussions shifted toward the practical criteria for adopting serverless compute over classic clusters or SQL warehouses [8]. Practitioners shared migration checklists, arguing that job compatibility limitations mattered more than reduced startup latency when moving production jobs [4, 5]. Teams also evaluated cost-performance trade-offs for rapid sync jobs [11] and explored SQL serverless warehouse integration via remote query functions [7].

Engineers surfaced specific networking and access boundaries in serverless environments. Users reported DNS failures where serverless compute resolved certain public domains but failed on others [13], as well as 403 permission errors when accessing AWS S3 buckets within account-regional namespaces [6]. Additionally, community members documented startup failures and workload errors when testing serverless compute within the Databricks Free Edition tier [10, 16].

Everything cited

  1. [1]system.query.history is now Generally Available in Databricks community · 2026-09-30
  2. [2]Laya off the benchmark: can a zero-shot decision model route real SQL traffic? community · 2026-09-24
  3. [3]Which Came First For You... Spark or Databricks? community · 2026-09-22
  4. [4]How I explain classic vs serverless compute, and the limitation list I check before migrating a job community · 2026-09-21
  5. [5]Before you move a job to serverless: the limitation list is the real decision, not the startup time community · 2026-09-21
  6. [6]Serverless compute returns 403 on S3 buckets in the account-regional namespace community · 2026-09-20
  7. [7]using remote_query with SQL Serverless Warehouse community · 2026-09-17
  8. [8]Databricks Serverless Compute: Practical Recommendations, Cost-Performance Guidance, and When to Use Serverless Instead of SQL Serverless Warehouses or Classic Clusters community · 2026-09-16
  9. [9]Deploy an Azure Databricks Serverless Workspace in Under 2 Minutes | Step-by-Step Tutorial video · 2026-09-11
  10. [10]Unable to Start Serverless Compute in Databricks Free Edition community · 2026-09-11
  11. [11]Cost-optimized way to reflect source DB changes in Silver in <1 minute? community · 2026-09-09
  12. [12]Connect VS Code to Databricks: The SSH Tunnel Guide video · 2026-09-09
  13. [13]Serverless compute resolves some public domains but not others community · 2026-09-08
  14. [14]What’s new in Databricks - August 2026 community · 2026-09-07
  15. [15]Clarification on Automating Serverless Compute Permissions via SDK/API community · 2026-09-04
  16. [16]Error While Running Workloads on Databricks Free Edition – Serverless Compute community · 2026-09-04

A frozen monthly snapshot, generated from the brickster.ai archive and never rewritten. For the live view of this topic, see the Serverless hub. brickster.ai is an independent community project, not affiliated with Databricks, Inc.