live wire
▸Databricks makes Genie Code CLI GA, but disabling its web search does not stop shell-based internet accessDatabricks▸OpenData Agent finds 3B single-agent and router-specialist designs nearly tied on 120 French RAG+SQL questionsOpenData Agent repository▸Databricks says ai_decide is 33% more accurate, while its beta contract permits the underlying model to changeDatabricks▸Adaptive-Elbow reaches 97% table recall at 36.9% precision on merged BIRD Mini-Dev, but does not test SQL executionAdaptive-Elbow paper▸Databricks Genie One scheduled tasks can now email other users, including visualizations and a PDF of each runDatabricks▸ThoughtSpot Data Cache is GA for Snowflake and Databricks models, but cached answers can differ from live resultsThoughtSpot▸Tableau raises Cloud Manager ceiling to 200 sites, but Cloud+/Tableau+ base capacity still supports 50Tableau▸Databricks adds daily per-user Genie spending controls, but blocking remains approximate and uses list pricesDatabricks▸Databricks brings governed-tag propagation to Runtime 19+ classic compute, but ABAC can lag derived data by minutesDatabricks▸Snowflake adds Pegasus 1.5 video analysis to AI_COMPLETE at GA, while video processing remains public previewSnowflake▸Living Context Graph raises held-out BIRD transfer accuracy from 13.7% to 36.3%, but needs verified SQL outcomesLiving Context Graph paper▸Google previews Apache Iceberg views in BigQuery’s Lakehouse catalog, but query-time access still reaches every base tableGoogle Cloud▸Oracle makes OCI Agent Sandbox GA with managed Linux execution, project-scoped egress and 48-hour initial lifetimesOracle OCI▸IBM Cognos Analytics 12.2.0 makes Query Agent GA and expands its MCP server to 104 toolsIBM Cognos Analytics▸Databricks makes Genie Code CLI GA, but disabling its web search does not stop shell-based internet accessDatabricks▸OpenData Agent finds 3B single-agent and router-specialist designs nearly tied on 120 French RAG+SQL questionsOpenData Agent repository▸Databricks says ai_decide is 33% more accurate, while its beta contract permits the underlying model to changeDatabricks▸Adaptive-Elbow reaches 97% table recall at 36.9% precision on merged BIRD Mini-Dev, but does not test SQL executionAdaptive-Elbow paper▸Databricks Genie One scheduled tasks can now email other users, including visualizations and a PDF of each runDatabricks▸ThoughtSpot Data Cache is GA for Snowflake and Databricks models, but cached answers can differ from live resultsThoughtSpot▸Tableau raises Cloud Manager ceiling to 200 sites, but Cloud+/Tableau+ base capacity still supports 50Tableau▸Databricks adds daily per-user Genie spending controls, but blocking remains approximate and uses list pricesDatabricks▸Databricks brings governed-tag propagation to Runtime 19+ classic compute, but ABAC can lag derived data by minutesDatabricks▸Snowflake adds Pegasus 1.5 video analysis to AI_COMPLETE at GA, while video processing remains public previewSnowflake▸Living Context Graph raises held-out BIRD transfer accuracy from 13.7% to 36.3%, but needs verified SQL outcomesLiving Context Graph paper▸Google previews Apache Iceberg views in BigQuery’s Lakehouse catalog, but query-time access still reaches every base tableGoogle Cloud▸Oracle makes OCI Agent Sandbox GA with managed Linux execution, project-scoped egress and 48-hour initial lifetimesOracle OCI▸IBM Cognos Analytics 12.2.0 makes Query Agent GA and expands its MCP server to 104 toolsIBM Cognos Analytics
nl2sql.ai
guideROLLOUT GUIDE

Databricks made ai_decide more accurate—but the model behind the SQL function can change again

The beta function now carries a 33% internal accuracy claim. Teams using it for routing or prioritization still need their own fixed regression set because Databricks reserves the right to replace the underlying model.

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

Databricks says its beta ai_decide() SQL function now answers questions 33% more accurately while keeping its previous low-latency profile. That is useful progress for teams using SQL to classify support tickets, score urgency, or route records—but it is not a stable-model guarantee.

The product contract explicitly says Databricks may change the model behind ai_decide() when another model performs better in its internal benchmarks. The function exposes a metadata.version field, but the current documented option is only version 1.0; the documentation does not promise that pinning that function version pins a specific underlying model.

What operators should treat as the contract

ai_decide() accepts text or structured data and can answer several rubric questions in one call. It supports three output forms: a probability for a true/false-style question, one selected label with probabilities, or a probability-weighted score across an ordered scale. Generated answers can vary between calls.

Databricks says input parameters are processed within its security perimeter and are not stored, although run metadata such as the Databricks Runtime version is retained. The beta is available only in supported regions, does not run on Databricks SQL Classic, and requires Runtime 15.4 LTS or later today; Databricks recommends Runtime 18.2 or later and has separately announced a future 17.3 LTS minimum for affected AI Functions.

The rollout gate

Do not promote this change solely because the vendor reports a 33% improvement. That figure comes from Databricks’ internal benchmark, not a workload-specific evaluation disclosed on the function page.

Before using the function in a consequential routing or prioritization path:

  1. Keep a versioned set of representative inputs and expected rubric outcomes.
  2. Record the full response, including probabilities, confidence, metadata.version, runtime version and error field.
  3. Compare both decision accuracy and threshold behavior; an unchanged top label can still hide a material probability shift.
  4. Put human review around low-confidence cases and any decision that changes customer access, spending or incident severity.
  5. Re-run the set after runtime upgrades or unexplained output drift, because the underlying model can change without a new SQL function name.

The practical reading is straightforward: Databricks has improved a useful decision primitive, but adopters own the regression boundary. A stable SQL signature is not the same thing as a stable decision model.

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.