live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
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, 2026the quick take — two AI hosts go live when you do

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