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
analysisNegative result

Five enterprise feeds show no Nov. 4 data-agent follow-up after Tuesday’s release burst

A 14:06 UTC check found no new data-agent or NL2SQL item across Snowflake, Databricks, AWS, Google Cloud analytics and Google Cloud customer announcements. The useful signal is the reporting boundary—not proof that development stopped.

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

What the feeds showed

As of 14:06 UTC on November 4, five first-party enterprise feeds had not posted a new data-agent or natural-language-to-SQL release dated November 4. This is a timestamped negative result, not a claim that no vendor work occurred.

Snowflake’s blog index still listed its November 3 group of posts as the newest entries: Frontier Engineering, governed agents and apps, AI governance, Business Ontology, CoWork and CoCo. The index showed no November 4 post at the time of checking.

Databricks’ RSS feed was built at 00:53 UTC on November 4, but its newest articles were still the November 3 posts about native OpenTelemetry observability for Claude in MLflow and UNIQUE constraints. Both had already entered this desk’s coverage before this check.

AWS’s What’s New feed was fresher: its build timestamp was 14:03 UTC. Its newest listing remained an Amazon Connect email-workflow update dated November 3. The recent on-beat entries—WorkSpaces for AI agents, AWS Config support for QuickSight Agent resources and AWS Transform’s mainframe requirements coverage—were also dated November 3 and had already been covered.

Google’s two surfaces were quieter. The Google Cloud Data Analytics RSS feed still reported an October 29 build, led by the Knowledge Catalog semantic-model expansion. Google Cloud Press Corner still showed a November 1 water-infrastructure announcement as its newest customer or partner release, with no newer enterprise data-agent deployment on the index.

What this does—and does not—mean

The finding is narrow: by the check time, these five observable first-party surfaces contained no new November 4 item on this beat. It does not establish that product code, private previews, documentation or regional rollouts were unchanged. RSS build times also differ sharply, so silence in one feed is not equivalent to silence in another.

That distinction matters operationally. Release feeds are evidence of what a vendor chose to disclose, not a complete changelog. Teams evaluating enterprise data agents should therefore record the feed timestamp alongside any “latest release” claim and separately monitor product documentation and contracts. Today’s negative result sets that boundary clearly: the public release burst remains dated November 3, while the November 4 enterprise record is still open.

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