Fixing poor performance patterns in Azure SQL Database applications

on YouTube ↗58m

" summary

Shows that switching Azure SQL from proxy to redirect (11000–11999) cuts round‑trip latency (example start 250 ms) when firewall and NSG ports are opened; fixes include collapsing N+1 selects with eager loads or single SQL queries, and parameterizing SQL to turn 10 separate ad‑hoc plans into one reused plan (demo: execution_count 10). Enables row/page compression to reduce logical reads and DB size (≈20% saving) with small CPU cost, and notes the hard 96 MB/s I/O limit per vCore.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 1:00Onpremises vs Cloud
3. 3:24Overview
4. 3:36Firewall Access
5. 5:22Considerations
6. 7:18Simple Client Demo
7. 13:39Over fetching
8. 19:11Memory optimization
9. 31:34Memory consumption comparison
10. 33:21Compression
11. 40:24Estimates
12. 48:09Resource Limits
13. 52:27Performance Analysis

" related talks

• 53mOptimizing your Azure SQL Database workloadsSanjay Mishra, Denzil Ribeiro, Dimitri Furman · SQLBits 2020
• 51mPerformance Tuning Azure SQL DatabaseMonica Rathbun · SQLBits 2023
• 50mSQL Server to Azure SQL: Performance and AvailabilityBob Ward, Anna Hoffman · SQLBits 2020
• 49mSQL Server on Azure VM - Configuring for Price-PerformanceDavid Pless · SQLBits 2024
• 49mPerformance Features in SQL Server and Azure SQLJavier Villegas · SQL Server Virtual Conference 2021
• 59mLessons Learned from the Trenches: Connectivity and Performance Tips&TricksJose Manuel Jurado Diaz · NDC London 2021
• 18mHow to reduce your SQL Database costs on AzureSulamita Dantas, Leonardo Fonseca · Data Con LA 2021
• 50mBuilt-in Intelligence with Azure SQL and SQL Server 2022David Pless · SQLBits 2023