Troubleshooting CPU Performance Issue for SQL Developers
summary
Argues CPU matters but disk I/O usually decides real-world slowness and shows concrete fixes: a demo inserts 100k rows in 0.2s when log and data sit on fast media but 23s or 1m19s when the log or files are on slow drives or autogrowth triggers. Immediate wins are move log to SSD, separate MDF and LDF onto appropriate disks, and pre-size data files and set sensible autogrowth — changes that the demos show produce instant measurable speedups.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 6:36Basics of SQL Server resources
- 19:14Demo one: Single vs multi-disk storage
- 35:37Demo two: Log file performance impact
- 48:07Demo three: Database file optimization
- 57:36Summary and resources
related talks
59mHow to be a Ninja Troubleshooting SQL performance...
43mPerformance Tuning, Getting the Biggest Bang for Your Buck
49mHidden Gems in SQL Server 2022 Database Engine
47mLoad Testing Storage Performance for SQL Server
54mYour Performance Tuning Check List
49mHidden Gems in SQL Server 2022 Database Engine
53mOptimizing your Azure SQL Database workloads
29mMySQL Performance for DevOps
