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 audit

ThoughtSpot’s 82.8% BIRD result comes with an unfinished audit trail

The vendor’s difficulty breakdown is more useful than a headline score, but anonymous rivals and unresolved judge-validation placeholders keep it off the official-comparison track.

Benchmark chart of ThoughtSpot beating unnamed rivals on BIRD difficulty bands.
AI-generated illustration
By The News Desk· Sep 22, 2026the quick take — two AI hosts go live when you do

ThoughtSpot has published an unusually detailed vendor benchmark for its Spotter AI analyst: 82.8% accuracy on 1,533 questions across 11 databases from a BIRD development split, with one attempt per question. The post says a frontier LLM reached 78.4% and a coding agent 72.5% under the same setup. Those are useful measurements—but they are not yet independently reproducible results. (ThoughtSpot)

The valuable part is the slope

ThoughtSpot breaks the result out by BIRD’s simple, moderate and challenging bands rather than stopping at one aggregate. Spotter reached 70.6% on 231 challenging questions, versus 66.7% for an unnamed warehouse assistant, 58.4% for an unnamed lakehouse agent, 56.7% for an unnamed frontier model and 46.8% for an unnamed coding agent. The company also reports that Spotter fell 16.4 points from simple to challenging, while the coding-agent category fell 33.5 points. (ThoughtSpot)

That framing is genuinely useful for buyers. Averages can conceal systems that perform well on straightforward questions and deteriorate on multi-join or nested queries. A difficulty curve gives teams a better hypothesis to test against their own workload than a single percentage.

ThoughtSpot also describes a controlled model swap: moving its harness from Claude Opus 4.8 to Claude Opus 5 raised overall accuracy from 79.4% to 82.8% and challenging-question accuracy from 65.8% to 70.6%, while tool calls stayed around 2.1 per question. Those are vendor-reported measurements, not an independent reproduction. (ThoughtSpot)

The audit trail is not finished

The appendix says BIRD’s official execution scorer could not run end to end because the compared products did not all emit portable SQLite SQL. ThoughtSpot instead used an exact-match pre-pass followed by a rubric judge that saw the question, expected output and returned data. But the live page still describes that judge as “[model]” and its human validation as “[N] questions ([X]% agreement)”. It also contains a bracketed conditional note for a possible re-score. (ThoughtSpot)

The four competitors remain category labels, and the post says exact products, versions, configurations, per-question outputs and judge transcripts are available only on request. The company further says the 3.9-point lead over the nearest rival on the challenging band has not cleared a paired per-question significance test. (ThoughtSpot)

That makes the result a vendor evaluation built on a public dataset—not an entry readers should compare directly with the systems on the official BIRD leaderboard. The distinction matters because the scoring path, product identities and validation details determine what the percentage means.

The practical takeaway is two-sided: copy ThoughtSpot’s single-attempt protocol and difficulty-band reporting for internal evaluations, but withhold comparative conclusions until the judge identity, audit sample, agreement rate and named configurations are published. The post has the shape of a transparent benchmark; its remaining placeholders show exactly what must be filled in before it becomes one.

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.