live wire
IBM makes watsonx Orchestrate AgentOps, custom LLM judging and Bedrock-agent discovery generally availableIBMSchemaGate 0.1.45 fixes broken Oracle ADB wallet connections and an OCI stack pinned 28 releases behindSchemaGatePDI’s Amazon Quick procurement agent grounds spend answers in vendor, category and contract contextAWS Business Intelligence BlogBigQuery’s ML.METRICS example returns 0.84 accuracy but 0.30 macro-F1 on the same 100-row classification queryGoogle Cloud BigQuery docsSchemaGate 0.1.44 auto-selects sentence embeddings, lifting bundled-schema retrieval from 90/98 to 93/98SchemaGateSchemaGate 0.1.43 adds read-only SQL execution with per-principal table checks—and documents unauthenticated client assertionsSchemaGateDatabox adds reusable AI Analyst Skills with personal/company scope, auto-matching and marketplace installsDataboxFabric previews an AI builder for data-agent instructions, source guidance and example queriesMicrosoft FabricDatabricks trains data-agent retriever to stop early or spend bounded extra search steps, reporting 5.8-second latencyDatabricksThoughtSpot adds SpotterCode coding agent to its Visual Embed PlaygroundThoughtSpotLongMemEval-S audit: 67–73% of restore-fixable 80k-budget errors came from evicted evidence under three policiesarXivSchemaGate 0.1.42 adds dimension-aware retrieval and fixes complex multi-table SQL promptsSchemaGateSnowflake agent toolsets can silently drop inherited tools when callers lack accessSnowflake DocumentationLooker’s VS Code extension reaches GA with MCP-assisted LookML generation, editing and validationGoogle Cloud Looker release docsIBM makes watsonx Orchestrate AgentOps, custom LLM judging and Bedrock-agent discovery generally availableIBMSchemaGate 0.1.45 fixes broken Oracle ADB wallet connections and an OCI stack pinned 28 releases behindSchemaGatePDI’s Amazon Quick procurement agent grounds spend answers in vendor, category and contract contextAWS Business Intelligence BlogBigQuery’s ML.METRICS example returns 0.84 accuracy but 0.30 macro-F1 on the same 100-row classification queryGoogle Cloud BigQuery docsSchemaGate 0.1.44 auto-selects sentence embeddings, lifting bundled-schema retrieval from 90/98 to 93/98SchemaGateSchemaGate 0.1.43 adds read-only SQL execution with per-principal table checks—and documents unauthenticated client assertionsSchemaGateDatabox adds reusable AI Analyst Skills with personal/company scope, auto-matching and marketplace installsDataboxFabric previews an AI builder for data-agent instructions, source guidance and example queriesMicrosoft FabricDatabricks trains data-agent retriever to stop early or spend bounded extra search steps, reporting 5.8-second latencyDatabricksThoughtSpot adds SpotterCode coding agent to its Visual Embed PlaygroundThoughtSpotLongMemEval-S audit: 67–73% of restore-fixable 80k-budget errors came from evicted evidence under three policiesarXivSchemaGate 0.1.42 adds dimension-aware retrieval and fixes complex multi-table SQL promptsSchemaGateSnowflake agent toolsets can silently drop inherited tools when callers lack accessSnowflake DocumentationLooker’s VS Code extension reaches GA with MCP-assisted LookML generation, editing and validationGoogle Cloud Looker release docs
nl2sql.ai
guideOPERATIONS

Oracle’s September 15 database-default flip is a provisioning change, not an automatic upgrade

Existing Autonomous AI Database Serverless instances stay put. The risk is in create and clone workflows that silently inherit a new version.

Oracle database provisioning before and after the default version change.
AI-generated illustration
By The News Desk· Sep 8, 2026the quick take — two AI hosts go live when you do

Oracle has put a date on a small-looking default change with a large automation consequence. Beginning September 15, new or cloned Autonomous AI Database Serverless instances will use Oracle AI Database 26ai when a database version is not explicitly supplied; today those same operations default to 19c. Existing instances are not changed by the switch. (Oracle announcement)

That distinction matters. This is not an automatic in-place upgrade of running databases. It is a change to the result of future provisioning. A console click, API request, SDK call, CLI command or Terraform plan that relies on the service default can start producing a different database version after the cutoff without the workflow itself changing. Oracle says the rule also applies to clones. (Oracle announcement)

Audit omission, not only intent

The practical pre-deadline check is therefore narrower than a migration project: find every create and clone path, then determine whether it states a version. Oracle tells customers that need 19c to set dbVersion in API or SDK requests, use --db-version 19c in OCI CLI commands, or set db_version = "19c" in Terraform. Console users can choose 19c under Choose database version. (Oracle announcement)

Even teams that want 26ai should consider pinning it explicitly. Oracle says no change is required when 26ai is the desired outcome, but an explicit version converts a mutable service default into reviewable infrastructure intent. It also makes a test environment, disaster-recovery clone and production deployment less likely to diverge because they ran on opposite sides of September 15. The recommendation to pin 26ai is an operational inference from Oracle’s documented default change, not an Oracle requirement. (Oracle announcement)

Oracle’s provisioning documentation currently presents 26ai and 19c as the available choices, while noting that availability varies by region and tier. In regions where 26ai is unavailable, 19c is the only option; paid 26ai is documented as available across commercial public-cloud regions, with exceptions listed for Always Free. (Oracle provisioning guide)

The safest reading is simple: do not treat a platform default as a version policy. Inventory creation and cloning paths, make the intended version explicit, and test the result before September 15. The deadline changes what omitted configuration means; it does not change existing databases for you. (Oracle announcement)

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.