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 agents

IBM puts Dun & Bradstreet’s commercial graph behind an MCP server

The watsonx Orchestrate catalog listing is a useful example of enterprise data agents moving from bespoke connectors toward governed, reusable context services.

IBM-style commercial graph service piping verified company data into an orchestration layer.
AI-generated illustration
By The News Desk· Aug 26, 2026the quick take — two AI hosts go live when you do

IBM has added the Dun & Bradstreet Commercial Graph to the watsonx Orchestrate Agent Catalog through a Model Context Protocol server, giving enterprise agents a packaged route to verified company data. IBM’s Aug. 12 announcement says the connector is live now.

The immediate use cases are not generic chatbot demos. IBM points to finance, credit, procurement, compliance, sales and marketing workflows, with the D-U-N-S Number acting as a common company identifier across systems of record. The MCP server can retrieve and analyze D&B commercial data while operating inside D&B’s existing quality controls, permissions and audit trails, according to the announcement.

Why this matters for data-agent teams

For practitioners building natural-language interfaces to enterprise data, generating a plausible query is only one part of the system. The agent also needs authoritative entity context, current data and a controlled way to reach it. IBM’s catalog model packages that access as a reusable capability rather than asking each implementation team to build and maintain another proprietary connector.

That separation is important. A text-to-SQL layer can answer questions about tables already inside a warehouse, while a commercial-graph service supplies verified external context such as company identity, financial-health indicators and relationship mappings. An orchestration layer can combine the two without pretending they are the same data source or applying the same access policy to both.

IBM says watsonx Orchestrate provides centralized control for building, monitoring and scaling agents across cloud and on-premises systems. The company also says the D&B server can support near-real-time company research, supplier-risk checks, credit assessment and cross-system workflows.

What to verify before adoption

The announcement makes broad deployment claims, including that teams can reduce agent-to-data connection work from months to days, but it does not publish a benchmark or a detailed pricing model. Buyers should therefore treat that statement as vendor guidance, not a guaranteed implementation timeline.

A practical evaluation should test four things: which D&B fields the server exposes; how watsonx and D&B permissions combine; what audit records are available for each agent call; and whether the returned company identity can be joined reliably to internal customer, supplier and account records. Teams should also measure freshness and failure behavior for the exact jurisdictions and business entities they use.

The larger signal is architectural: enterprise agents are beginning to consume governed data products through standardized tool interfaces. For NL2SQL systems, that creates a cleaner boundary between query generation, business semantics and external enrichment—and a clearer checklist for deciding which layer is responsible when an answer is wrong.

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