How to be a Ninja Troubleshooting SQL performance...
summary
Clear, actionable rules: use DS3 or higher for Enterprise (DS2 for Standard), put data and logs on separate disks and prefer P30 premium disks with read cache for data and caching off for logs, use storage spaces/striping and 64 KB allocation units, enable instant file initialization (Perform volume maintenance task) — demos use PowerShell, backups to Azure blob run much faster than to data disks, and a restore without IFI takes ~10× longer.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:25Questions
- 2:10Sponsors
- 2:50Passim
- 4:19Data Professional
- 7:26Agenda
- 11:10Capital Expenditure vs Operational Expenditure
- 20:40Cheat Sheet
- 22:13Storage Tips
- 32:13Best Practices
- 35:48Results
- 38:43Backups
- 43:33Instant File initialization
- 51:43Block pages in memory
- 52:00Summary
related talks
58mTroubleshooting CPU Performance Issue for SQL Developers
49mSQL Server on Azure VM - Configuring for Price-Performance
43mPerformance Tuning, Getting the Biggest Bang for Your Buck
47mArchitecting for High Performance SQL Server on Virtual Machines
54mAzure Best Practices for Lift and Shift
57mYour Performance Tuning Check List
54mYour Performance Tuning Check List
42mSQL Server on Azure VM - Configuring for price-performance
