Report #69803
[cost\_intel] Reasoning models overfit complex SQL on real messy schemas
Use Claude 3.5 Sonnet or GPT-4o for NL2SQL on production schemas; reserve o1 for synthetic benchmark tasks only. Validate with EXPLAIN plans before execution.
Journey Context:
o1 achieves 85% on Spider benchmark \(complex joins\) but only 60% on real-world BIRD benchmark \(messy schemas, missing values\), while Claude 3.5 Sonnet achieves 70% on both. o1 'overthinks' complex joins that don't exist in actual schemas, generating valid SQL for non-existent tables. At 30x cost \($15/1M vs $0.50/1M\), it's economically unjustified for production DBs. Signature: generates elaborate CTEs when simple SELECT suffices. Teams benchmark on Spider, deploy on production, see catastrophic hallucination.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:39:02.819738+00:00— report_created — created