live wire
▸Open Spider 2.0 patch adds an 8-row counterexample to expose opposite SQL joins that currently score the sameSpider 2.0 GitHub▸Keller Schroeder says its deployed Copilot Studio NL2SQL agent uses curated views, read-only Azure SQL and Power BI answer checksKeller Schroeder▸Colrows warns one agent question can fan out into many billable metric, query or capacity eventsColrows▸Colrows says most production analytics agents remain at autonomy levels 2–3, not exception-handling level 4Colrows▸dbt proposes three-stage agent autonomy: read-only, reviewed drafts, then bounded write-backdbt▸Strategy says direct text-to-SQL hit 0% on complex queries in a 28-table insurance testStrategy▸Hex adds point-and-click edits to AI-generated charts to avoid another prompt and token spendHex▸Domo says AI apps should inherit warehouse permissions instead of recreating access rulesDomo▸ThoughtSpot fellow to argue production agents need governed semantic tools, not generated SQLAICamp / ThoughtSpot▸Trackunit says IrisX surfaced $2M in missed invoices across a 5,000-unit rental fleetDatabricks / Trackunit▸SAP says HANA Cloud can retain agent context across sessions; RPT-1 integration remains plannedSAP▸Self-sizing IBLT beats tuned Merkle localization 1.55× on a 600M-row replay at 10 Mbps; ties it at 100 MbpsarXiv / China Mobile + NineData▸Google warns Data Agent Kit agents can mistake BigQuery or Cloud Storage data for instructionsGoogle Cloud▸AtScale says agent skills cannot enforce metric definitions, access rules or query-cost controlsAtScale▸Open Spider 2.0 patch adds an 8-row counterexample to expose opposite SQL joins that currently score the sameSpider 2.0 GitHub▸Keller Schroeder says its deployed Copilot Studio NL2SQL agent uses curated views, read-only Azure SQL and Power BI answer checksKeller Schroeder▸Colrows warns one agent question can fan out into many billable metric, query or capacity eventsColrows▸Colrows says most production analytics agents remain at autonomy levels 2–3, not exception-handling level 4Colrows▸dbt proposes three-stage agent autonomy: read-only, reviewed drafts, then bounded write-backdbt▸Strategy says direct text-to-SQL hit 0% on complex queries in a 28-table insurance testStrategy▸Hex adds point-and-click edits to AI-generated charts to avoid another prompt and token spendHex▸Domo says AI apps should inherit warehouse permissions instead of recreating access rulesDomo▸ThoughtSpot fellow to argue production agents need governed semantic tools, not generated SQLAICamp / ThoughtSpot▸Trackunit says IrisX surfaced $2M in missed invoices across a 5,000-unit rental fleetDatabricks / Trackunit▸SAP says HANA Cloud can retain agent context across sessions; RPT-1 integration remains plannedSAP▸Self-sizing IBLT beats tuned Merkle localization 1.55× on a 600M-row replay at 10 Mbps; ties it at 100 MbpsarXiv / China Mobile + NineData▸Google warns Data Agent Kit agents can mistake BigQuery or Cloud Storage data for instructionsGoogle Cloud▸AtScale says agent skills cannot enforce metric definitions, access rules or query-cost controlsAtScale
nl2sql.ai
newsENTERPRISE AI

Databricks puts Genie inside a new account-level Governance Hub

The beta gives platform teams one place to inspect data coverage, AI usage and cost — while keeping policy-changing actions on the roadmap.

Before-and-after Databricks governance view with scattered records versus one unified hub.
Side by side: what changed
By The News Desk· Aug 26, 2026

Databricks has launched Governance Hub in beta, adding an account-level control surface for data governance, AI activity and platform cost across AWS, Azure and Google Cloud. The company says the new hub is designed for teams overseeing hundreds of workspaces, where the evidence needed for an audit or cost investigation is otherwise spread across system tables, workspace views and third-party tools. Databricks announced the beta on August 26.

What administrators get now

Governance Hub is split into Data, AI and Cost views. The Data view highlights missing tags, ownership, descriptions and classification coverage; its Access Insights view lets administrators inspect direct and inherited access for a user, group or service principal. The AI view reports token consumption, model activity, per-user spending and guardrail coverage from Unity AI Gateway, while Cost surfaces spend trends and resources missing allocation tags. The product documentation describes these as account-level views with drill-downs.

The practical change is consolidation rather than a new permission model. Databricks says the hub respects existing Unity Catalog permissions and introduces no new access controls. Account administrators receive the broadest view; workspace administrators see cost information for their assigned workspaces, and metastore administrators see data information for their metastores. The documentation also warns that data can take up to a day to appear after an administrator enables the preview. Those role boundaries and the loading delay are documented here.

Genie moves from analysis to governance questions

The release’s text-to-SQL angle is the integration with Genie. Administrators can ask natural-language questions such as why costs spiked or which sensitive tables lack masking policies, with answers grounded in the hub’s governance data rather than a separately maintained dashboard. Databricks says Genie understands the context of the Data, AI and Cost views, so users can investigate token usage or unclassified assets without writing queries. The launch post gives those examples explicitly.

For practitioners, that makes metadata quality part of the query interface itself: if ownership, tags or classifications are incomplete, the hub is intended to expose the gaps before teams rely on an agent’s answer. It also gives operators a common place to watch who is using models and what that traffic costs, rather than treating conversational analytics as an isolated front-end feature.

There is an important boundary in the beta. Genie can answer questions and recommend next steps today, but Databricks describes policy configuration, alert creation and implementation of recommendations as capabilities coming later. Governance teams should therefore evaluate the preview as an observability and investigation layer, not yet as an autonomous remediation system. Databricks places those actions on its roadmap.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk