Editorial illustration for ESQ-Bench: A New NL2SQL Benchmark Tests Dialect Generalization and Silent Failures
ESQ-Bench Reveals NL2SQL Model Weaknesses
ESQ-Bench: A New NL2SQL Benchmark Tests Dialect Generalization and Silent Failures
Spider and BIRD, the two benchmarks most NL2SQL papers lean on for bragging rights, let top models clear 89 percent execution accuracy. That number looks reassuring until you ask what the benchmarks actually contain: academic schemas, open-source SQL dialects, and query patterns far simpler than anything running inside a bank or an insurance company. A new benchmark called ESQ-Bench takes aim at that gap directly, building its test set from enterprise Oracle schemas rather than textbook databases, and it structures queries into difficulty tiers meant to mimic how real analysts escalate from simple lookups to convoluted joins.
The design choice that matters most is what ESQ-Bench measures alongside execution success. A query can run without errors and still return the wrong answer, a failure mode invisible to benchmarks that only check whether SQL executes. ESQ-Bench tracks exact-match accuracy separately from execution accuracy, and it flags cases where a model's output passes execution but diverges semantically from the correct result. That distinction, largely absent from Spider and BIRD, is where the benchmark's findings start to diverge sharply from the polished numbers vendors publish.
ESQ-Bench: A Multi-Tier Enterprise Oracle Benchmark for Evaluating NL2SQL Dialect Generalization and Silent Semantic Divergence State-of-the-art Natural Language to SQL (NL2SQL) models report execution accuracy exceeding 89 percent on established benchmarks such as Spider and BIRD. However, these benchmarks rely on simplified academic schemas and open-source SQL dialects that do not reflect the complexity of enterprise database environments.
Why this matters
An 89 percent execution accuracy score on Spider or BIRD tells you almost nothing about whether a model can survive contact with a real Oracle warehouse, and ESQ-Bench's authors built six schemas with 465 tables and 164,682 rows specifically to prove that gap. For teams shipping NL2SQL into finance, logistics, or any enterprise stack running Oracle, the benchmarks everyone cites have been measuring the wrong thing: clean academic schemas that don't reward dialect fluency or punish quiet semantic drift. The "silent-divergence" framing is the part worth sitting with.
A query that returns a plausible, wrong answer is worse than one that errors out, because nobody flags it. If you're building or buying NL2SQL tools right now, treat any accuracy claim from Spider or BIRD as a floor, not a ceiling, and ask vendors directly whether they've been tested against multi-tier Oracle schemas with zero empty tables. Founders in this space should see ESQ-Bench as a preview of the harder evaluation standard enterprise buyers will start demanding before they let a model near production data.
Common Questions Answered
Why do Spider and BIRD benchmarks fail to accurately measure NL2SQL model performance in enterprise environments?
Spider and BIRD rely on simplified academic schemas and open-source SQL dialects that do not reflect the complexity of real enterprise database environments. While models achieve 89 percent execution accuracy on these benchmarks, this score tells you almost nothing about whether a model can actually work with real Oracle warehouses used in finance, logistics, and other enterprise stacks.
What makes ESQ-Bench different from existing NL2SQL benchmarks like Spider and BIRD?
ESQ-Bench is built from enterprise Oracle schemas rather than textbook academic databases, making it a more realistic test of NL2SQL capabilities. The benchmark includes six schemas with 465 tables and 164,682 rows specifically designed to expose gaps in dialect fluency and reveal silent semantic divergence that simpler benchmarks miss.
What is silent semantic divergence in the context of NL2SQL models?
Silent semantic divergence refers to cases where NL2SQL models produce SQL queries that execute without errors but return incorrect results or miss critical semantic requirements. ESQ-Bench specifically tests for these failures, which are particularly dangerous in enterprise environments where undetected errors can have significant business consequences.
How large is the ESQ-Bench dataset compared to traditional NL2SQL benchmarks?
ESQ-Bench contains six enterprise Oracle schemas with 465 tables and 164,682 rows of data. This scale is significantly larger and more complex than the academic schemas used in Spider and BIRD, providing a more rigorous test of model capabilities in real-world enterprise settings.
Further Reading
- ESQ-Bench: A Multi-Tier Enterprise Oracle Benchmark for Evaluating NL2SQL Dialect Generalization and Silent Semantic Divergence - arXiv
- A Modular Benchmarking Framework for LLM-Enabled NL2SQL Approaches - arXiv
- SPENCE: A Syntactic Probe for Detecting Contamination in NL2SQL Models - arXiv
- NL2SQL-BUGs: A Benchmark for Detecting Semantic Errors in NL2SQL - NL2SQL-BUGs
- Natural Language to SQL: State of the Art and Open Problems - PVLDB