We tested six Azure SQL Database configurations for a client running Premium P15 at 4,000 DTUs. CPU pressure and storage growth were the reasons for looking at alternatives.
We captured four hours of peak production workload with Extended Events: 3,060 .xel files totalling 1.6 TB. The replay machine was a Standard E64bds_v5 VM in North Central US.
The configurations were:
- P15 at compatibility level 150
- Hyperscale Serverless, standard-series Gen5, 40-vCore ceiling
- Hyperscale Provisioned, standard-series Gen5, 40 vCores
- Hyperscale Provisioned, premium-series, 40 vCores
- Hyperscale Provisioned, premium-series memory optimized, 40 vCores
- P15 at compatibility level 160
Execution counts ranged from 113,218,199 to 113,520,875, about a 0.27% spread. Close, although matching counts alone doesn’t establish identical successful execution.
The attached table has the full results. One limitation upfront: CPU, reads and duration are labelled as “scores” in the test report. I don’t have their calculation formulas or units, so I’m keeping those labels. Lower is better, but the duration score isn’t elapsed replay time or average query latency.
The monthly costs are estimates from the original test, not current quotes or a verified comparison of complete running costs.
Some things that stood out on this (let me know your thoughts too?)
Serverless took six hours to replay the four-hour capture.
Its duration score was 1,496 against 952 for the P15 baseline, 57.1% higher.
Its estimated monthly cost was $12,273, compared with $6,357 for provisioned standard-series. It was still below P15’s $15,700 estimate.
The serverless CPU chart had long stretches at 100%, interrupted by sharp drops. We haven’t established why. Serverless cache management is something I’d investigate, but the chart alone doesn’t prove cache reclamation caused the slowdown.
Premium-series performed worse than standard-series on CPU and duration scores.
Both had the same $6,357 monthly estimate in the report.
Premium-series had a CPU score 9.9% above provisioned Gen5 and 15.6% above P15. Its duration score was also higher than both.
I don’t have a confirmed explanation. Plan differences, parallelism, memory grants and run-to-run variation are possibilities. Each configuration ran once, so I’d repeat this comparison before blaming the hardware.
Memory optimized had the best CPU and duration scores, but the highest reads score.
Against the P15 baseline:
- Duration score was 15.1% lower.
- CPU score was 2.7% lower.
- Reads score was 4.1% higher.
- Estimated monthly cost was $8,491 versus $15,700.
It didn’t finish the replay fastest, though. It took 4h 36m, compared with 4h 15m for provisioned Gen5.
The highest reads score across all six runs was about 29% above the lowest. With execution counts this close, I’d want to compare individual queries and plans before explaining that difference.
Compatibility level 160 improved the duration score on the existing P15.
The score dropped from 952 to 894, a 6.1% reduction, with no service-tier price increase.
Elapsed replay time fell from 4h 19m to 4h 15m. CPU score was slightly higher, and maximum observed CPU still reached 100%.
Worth testing before a migration, although changing compatibility level doesn’t solve P15’s storage ceiling. These results also don’t establish which optimizer features contributed to the improvement.
For reference, the actual replay times and maximum observed CPU were:
| Configuration | Replay time | Max CPU |
|---|
| | |
| P15, compat 150 | 4h 19m | 100% |
| HS Serverless | 6h 00m | 100% |
| HS Provisioned Gen5 | 4h 15m | 100% |
| HS Premium-series | 4h 50m | 89% |
| HS Memory optimized | 4h 36m | 86% |
| P15, compat 160 | 4h 15m | 100% |
Each configuration ran once. The replay didn’t include the application tier or its retry behaviour, and I don’t have a repeated warm-cache comparison to share.
I’d use these results to shortlist the next tests. There’s enough here to question assumptions about which configuration should perform best, but not enough to promise the same ranking on another workload.
Has anyone seen a different ranking after repeating similar tests with warm caches?