live wire
▸Snowflake agent evals can pin judge versions; unpinned metrics may roll forward and shift scoresSnowflake▸ThoughtSpot makes Spotter 3 default for new instances; it requires download rights and always shares query data with an LLMThoughtSpot documentation▸MotherDuck adds image classification and object location to prompt_jev(), returning typed SQL outputs with confidence scoresMotherDuck▸BigQuery conversational analytics adds Montréal and Toronto; mixed-region agents still default to globalGoogle Cloud Documentation▸Fabric enables Azure OpenAI Copilot access by default, but OpenAI-subprocessor and cross-region processing/storage switches remain offMicrosoft Learn▸Snowflake Cortex Agents now continue by default when named tools are inaccessible, emitting warnings instead of failing the runSnowflake documentation▸Databricks Genie One can use group memberships to tailor answers, while Unity Catalog remains the access-control boundaryDatabricks documentation▸Fabric data agents can query Power BI models with Read alone; Build and workspace access are unnecessaryMicrosoft Learn▸Fabric data-agent Git configs expose column flags, but selecting a table still includes every columnMicrosoft Learn▸Google Data Agent Kit offers remote Spark kernels, but notebook exports can still move results into local Pandas or ArrowGoogle Cloud Documentation▸Cube says production analytics agents need explicit partial-result states, caller-filtered model search and durable artifactsCube▸Thinking Machines names Bridgewater behind ReViSQL-K2.6, citing 92.97% SC-16 accuracy at 15% of frontier-model costThinking Machines Lab▸AWS says a mismatched data/tool/prompt release cut its Field Sales agent pass rate from 78% to 38% in pre-productionAWS Artificial Intelligence Blog▸NL2SQL Multi-Agent ships evaluation artifacts across BIRD, CSpider, Archer and KDD DataSpace—but no software licenseGitHub▸Snowflake agent evals can pin judge versions; unpinned metrics may roll forward and shift scoresSnowflake▸ThoughtSpot makes Spotter 3 default for new instances; it requires download rights and always shares query data with an LLMThoughtSpot documentation▸MotherDuck adds image classification and object location to prompt_jev(), returning typed SQL outputs with confidence scoresMotherDuck▸BigQuery conversational analytics adds Montréal and Toronto; mixed-region agents still default to globalGoogle Cloud Documentation▸Fabric enables Azure OpenAI Copilot access by default, but OpenAI-subprocessor and cross-region processing/storage switches remain offMicrosoft Learn▸Snowflake Cortex Agents now continue by default when named tools are inaccessible, emitting warnings instead of failing the runSnowflake documentation▸Databricks Genie One can use group memberships to tailor answers, while Unity Catalog remains the access-control boundaryDatabricks documentation▸Fabric data agents can query Power BI models with Read alone; Build and workspace access are unnecessaryMicrosoft Learn▸Fabric data-agent Git configs expose column flags, but selecting a table still includes every columnMicrosoft Learn▸Google Data Agent Kit offers remote Spark kernels, but notebook exports can still move results into local Pandas or ArrowGoogle Cloud Documentation▸Cube says production analytics agents need explicit partial-result states, caller-filtered model search and durable artifactsCube▸Thinking Machines names Bridgewater behind ReViSQL-K2.6, citing 92.97% SC-16 accuracy at 15% of frontier-model costThinking Machines Lab▸AWS says a mismatched data/tool/prompt release cut its Field Sales agent pass rate from 78% to 38% in pre-productionAWS Artificial Intelligence Blog▸NL2SQL Multi-Agent ships evaluation artifacts across BIRD, CSpider, Archer and KDD DataSpace—but no software licenseGitHub
nl2sql.ai
benchmarkBenchmark

COAL-SQL gets 64.9% on BIRD dev by training on failures, not just more examples

The released framework uses SQL-structure coverage and targeted correction of all-wrong rollout groups, but its author-reported dev score is not a hidden-test leaderboard result.

Chart showing COAL-SQL’s 50.9% to 64.9% gain on BIRD dev.
Chart: figures from the story
By The Benchmark Desk· Sep 22, 2026the quick take — two AI hosts go live when you do

A smaller training set, chosen deliberately

COAL-SQL reports 64.9% execution accuracy on the BIRD development split after post-training Qwen2.5-Coder-7B-Instruct on 12,644 distinct examples. The paper says the same backbone scores 50.9% before this post-training, a 14.0-point gain. That is an author-reported development result, not the BIRD hidden-test score, and it should not be compared directly with test results on the live leaderboard. The paper states the split, backbone and data count explicitly.

The interesting result is less the absolute rank than the training allocation. COAL-SQL first converts queries into schema-independent skeletons, preserving operators, clause structure, joins, nesting and set operations while masking database-specific names and values. It then uses metric K-center selection to add examples whose structures complement the seed set rather than sampling more SQL indiscriminately. The released repository includes the augmentation, skeleton-retrieval and training modules.

Train on the places reinforcement learning stalls

The second half of the method targets what the authors call Solve-None examples: prompts for which none of eight sampled rollouts executes correctly. COAL-SQL keeps GRPO as its main objective, but adds supervised reasoning traces for newly observed failures and retrieves structurally related practice from failures accumulated across an epoch. In the paper’s initial policy, 15.1% of training examples were Solve-None, concentrated around nested queries, multi-table joins and aggregation combinations. Those definitions and measurements come from the evaluation and method sections.

The ablations support a modest but consistent contribution from that targeting. GRPO on the augmented set reaches 63.2% BIRD dev execution accuracy; adding step-level correction raises it to 63.8%, and adding epoch-level expansion reaches 64.9%. Replacing failure-aware epoch retrieval with random practice lowers BIRD dev to 64.3%. Replacing coverage-guided K-center selection with random augmentation lowers it to 64.4%. The paper reports all of these on the BIRD development split.

What the number does—and does not—show

Within the paper’s comparison, COAL-SQL exceeds OmniSQL’s 63.9% while using about 12.6K rather than 2.5 million training examples. It also reports 36.2% execution accuracy on EHRSQL and 53.9% on Science Benchmark, versus 24.3% and 45.2% for the untrained backbone. The authors audit all 12,644 training questions against 1,534 BIRD dev questions and report no exact duplicate, no shared 13-gram and no SQL pair with token containment of 0.5 or more. These are the paper’s own results and contamination checks.

That still leaves independent reproduction as the next test. The repository publishes runnable code and configuration scaffolding, but does not bundle the benchmark datasets; users must supply BIRD and the external SQL collection themselves. The repository documents those prerequisites. For now, 64.9% is evidence that carefully chosen structures and failure-driven supervision can improve data efficiency on BIRD dev—not a new BIRD test leader.

Filed by The Benchmark 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.