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
analysisEnterprise AI

Snowflake on OCI is a procurement and data-gravity play—not a launch yet

Oracle and Snowflake are collapsing contracting, credits and data movement into one cloud boundary, but the announcement remains forward-looking and gives teams no availability date.

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

Oracle and Snowflake have announced a plan to make Snowflake’s AI Data Cloud a native, first-party service on Oracle Cloud Infrastructure. The important word is plan: Oracle’s release says customers “will be able” to buy and provision it through Oracle, while Snowflake calls the offering planned and explicitly says its future-product statements are not delivery commitments. Neither company gives an availability date or launch-region list. Oracle announcement · Snowflake announcement

What “first-party” is meant to change

This is more than a marketplace listing. Oracle says it would manage pricing, discounts and billing, let customers spend Oracle Universal Credits on Snowflake, and provide a single commercial relationship. Snowflake says customers would provision an account through the OCI control plane and then manage warehouses, databases, pipelines and access controls with familiar Snowflake capabilities. Oracle announcement · Snowflake announcement

For platform teams, that makes procurement architecture part of data architecture. Existing OCI commitments could fund the service, while Oracle—not a separate cloud vendor—would sit on the commercial path. Teams evaluating the offer should therefore compare the effective credit burn and discount structure, not only list-price compute.

The data-gravity case

The planned integrations cover Oracle Fusion applications, NetSuite, cloud-hosted Oracle Database, Autonomous Database, MySQL HeatWave and Oracle NoSQL Database. Both companies say keeping Snowflake workloads on OCI should reduce custom pipelines, cross-cloud movement and associated egress costs. Snowflake also says the service is intended to retain cross-cloud sharing, replication and failover with accounts on other supported clouds and regions, subject to validation and availability. Oracle announcement · Snowflake announcement

That combination matters for enterprise analytics agents: governed Oracle application data could sit closer to Snowflake analytics and AI workloads without forcing every query path across a cloud boundary. But the announcements do not publish latency tests, connector freshness guarantees, supported regions, service-level objectives or pricing. They also describe role-based controls and data policies at a high level rather than documenting how Oracle and Snowflake identities map across the proposed control plane. Snowflake announcement

What to ask before committing

A serious evaluation should wait for four contracts: exact GA regions and dates; connector modes and refresh behavior for each Oracle source; identity, audit and policy propagation across OCI and Snowflake; and a complete cost model covering credits, storage, transfer and cross-cloud continuity.

The announcement is strategically meaningful because it moves Snowflake inside Oracle’s infrastructure and commercial boundary. It is not yet an operational deployment guide. Until those contracts appear, architects should treat the service as a roadmap option—not an available shortcut to governed enterprise AI.

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