Lessons Learned from the Trenches: Connectivity and Performance Tips&Tricks

on YouTube ↗59m

" summary

Live debugging uses Visual Studio profiler plus Stopwatch and SQLConnection.Statistics to prove whether slow spots are app code or DB. Azure portal metrics, Query Store and Application Insights pin the offending SQL: an implicit nvarchar→varchar conversion causes a full scan of ~400,000 rows and drops a 900ms average to single-digit ms after fixing the datatype. Connectivity failures are often exhausted pools (default max 100; seen up to 600 concurrent attempts) fixed with proper connection pooling, retry/backoff and clearing pools.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 1:28Why this session?
3. 6:03Scenario 1: Why my Application is running slow? . Based on performance issues caused by data type mismatches • Tools Query Store, Portal and Aur Diagnostics Integration
4. 39:23Scenario 2: Why my Application times out?

" related talks

• 49mPerformance Features in SQL Server and Azure SQLJavier Villegas · SQL Server Virtual Conference 2021
• 58mFixing poor performance patterns in Azure SQL Database applicationsMartin Cairney · NDC Sydney 2020
• 51mPerformance Tuning Azure SQL DatabaseMonica Rathbun · SQLBits 2023
• 50mDeveloper Best Practices for Azure SQL : Avoiding common pitfalls when using the Cloud DatabaseDavide Mauri · SQL Server Virtual Conference 2021
• 58mAzure SQL Database - Lessons learned from the trenchesJose Manuel Jurado Diaz, Vitor Pombeiro · Global Summer 2020 Azure Data Fest 2020
• 01h 06mGet Better App Performance with this One Weird TrickNik Karpinsky · Visual Studio Live! at Microsoft HQ 2024
• 50mSQL Server to Azure SQL: Performance and AvailabilityBob Ward, Anna Hoffman · SQLBits 2020
• 58mTroubleshooting CPU Performance Issue for SQL DevelopersPinal Dave · Great Indian Developer Summit 2015