Do coding agents recommend Azure SQL Database?
Azure SQL Database was chosen in 8% of 496 judged databases sessions, ranking third. Measured with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code.
Azure SQL Database was chosen in 8% of 496 judged databases sessions, ranking third. It was also raised as a candidate in 22 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in databases inside a realistic codebase. Not what a chat assistant says about Azure SQL Database. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about databases in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Databases |
| Sessions in the category | 496 |
| Sessions where Azure SQL Database was chosen | 41 |
| Install share | 8% |
| Rank in category | 3 of 15 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 22 |
| Chosen when considered | 65% |
| Site | azure.microsoft.com |
By agent
Claude Code, Codex, Cursor and Muse Code land within 7 points of each other on Azure SQL Database, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Azure SQL Database | Share |
|---|---|---|---|
| Claude Code | 147 | 9 | 6% |
| Codex | 139 | 15 | 11% |
| Cursor | 142 | 15 | 11% |
| Grok Build CLI | 18 | 0 | 0% |
| Muse Code | 50 | 2 | 4% |
By who was asking
Azure SQL Database does much better with one kind of buyer than another. It won 16% of sessions asked as senior engineer and 0% of those asked as junior developer.
| Who is asking | Sessions | Chose Azure SQL Database | Share |
|---|---|---|---|
| Vibe coder | 83 | 0 | 0% |
| Junior developer | 153 | 0 | 0% |
| Senior engineer | 260 | 41 | 16% |
What Azure SQL Database was up against
The full ranking in databases, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Neon | 316 | 64% |
| 2 | Azure Database for PostgreSQL Flexible Server | 45 | 9% |
| 3 | Azure SQL Database (this page) | 41 | 8% |
| 4 | Amazon RDS for PostgreSQL | 29 | 6% |
| 5 | Supabase | 17 | 3% |
| 6 | Scaleway Managed Database for PostgreSQL | 13 | 3% |
| 7 | MotherDuck | 11 | 2% |
| 8 | DigitalOcean Managed PostgreSQL | 7 | 1% |
What this means
Agents almost never raise Azure SQL Database without choosing it: 22 sessions raised against 41 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 496 sessions in databases are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every databases run can be replayed on the board.
If you work on Azure SQL Database: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Azure SQL Database?
Yes. Azure SQL Database was chosen in 41 of the 496 judged sessions in databases, a 8% install share, ranking third in its category.
Does Claude Code recommend Azure SQL Database?
In 9 of the 147 sessions in databases run with Claude Code, which is 6%.
Do different coding agents treat Azure SQL Database differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 4% and 11% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Azure SQL Database considered but not chosen?
It was raised as a candidate in 22 sessions without being chosen, and chosen in 41. That is a 65% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.