Architecting for High Performance SQL Server on Virtual Machines
summary
Default VM and OS settings often throttle SQL Server: the default balanced power plan can cut I/O throughput by about 30% IO drop, and over‑allocating vCPUs causes high CPU ready (one customer fixes perceived slowness by dropping a VM from dozens of vCPUs to eight cores). Memory ballooning or locked pages leads to swapped guests and massive latency. Use PV SCSI adapters (multiple adapters up to four) for parallel I/O, collect DMVs, perfmon and vSphere metrics into Grafana/Telegraf, and codify configs with PowerShell + Pester templates.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:56Let's talk about your VMware environment...
- 9:30So, you wanna go fast?
- 27:43Let's talk about your VM configuration - Memory
- 36:36Let's talk about your VM configuration - Disks
- 43:53But what about SQL Server's config?
- 45:45Resources
related talks
47mArchitecting for High Performance SQL Server on Virtual Machines
49mSQL Server on Azure VM - Configuring for Price-Performance
42mSQL Server on Azure VM - Configuring for price-performance
54mYour Performance Tuning Check List
57mYour Performance Tuning Check List
43mPerformance Tuning, Getting the Biggest Bang for Your Buck
57mSQL Server hates you(?) - what the DBAs never told the developers
54mAzure Best Practices for Lift and Shift