live wire
▸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▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv▸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▸Graph-repair retrieval cut F1 by 0.126 on one suite; a learned router used fewer tokens than always-on retrieval in all sixLin et al. / arXiv
nl2sql.ai
analysisRelease watch

Five enterprise release feeds went quiet after Friday’s analytics-agent launches

A Saturday checkpoint found no new product delta across AWS, Databricks, Snowflake, Oracle and IBM—but the feeds’ different clocks make “nothing shipped” a narrower claim than it sounds.

By The News Desk· Nov 7, 2026the quick take — two AI hosts go live when you do

What the feeds showed

A 19:05 UTC checkpoint on November 7 found no newly published analytics-agent or text-to-SQL product change across five first-party enterprise surfaces.

AWS was the freshest source. Its What’s New RSS feed reported a 19:03 UTC build, but its newest item was still Friday’s 22:47 UTC Bedrock release of Kimi K3.1 Pro. The next relevant entries—Agent Registry in GovCloud, MSK Replicator in GovCloud and Redshift’s larger SUPER strings—were also Friday announcements already covered by this desk.

Databricks’ blog feed reported a 01:45 UTC Saturday build. Its newest posts remained Friday’s two-part OpenSharing series, followed by the Feature Views fraud-detection walkthrough published Thursday. Those items had likewise already entered the desk’s coverage.

The slower surfaces had not moved either. Snowflake’s blog index still listed November 3 as its newest publication date. Oracle’s SQLcl changelog still topped out at version 26.3.1, whose AI-relevant change is improved database-annotation management. IBM’s Think News page still surfaced its TechXchange AI, security and data roundup rather than a new watsonx.data or Db2 assistant launch.

What the absence does—and does not—mean

This is a negative result, not evidence that the products were unchanged internally. The five surfaces publish on different clocks: AWS exposed a feed build two minutes before the check, Databricks exposed an early-Saturday build, while Snowflake and Oracle presented dated index or changelog entries. IBM’s page exposed only a current highlighted story in the fetched view.

The defensible conclusion is narrow: by 19:05 UTC, these five first-party publication surfaces contained no uncovered Saturday product announcement on the beat. That matters operationally because Friday’s dense run of launches can otherwise create the impression that a newer weekend update has displaced them. It had not.

For practitioners, the checkpoint is a reminder to distinguish release-feed silence from product stability. A feed proves what the vendor published there; it does not prove that documentation, preview flags or regional availability stayed fixed elsewhere. The next useful check is therefore not another identical search—it is a targeted pass over product documentation and regional availability matrices when the vendors’ publishing cadence resumes.

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