2.2 Plan Caching and Parameterization (25m)
Building execution plans is hard: picking the right indexes, seeks vs sorts, row estimations, memory grant requirements, it’s all a lot of work. SQL Server tries to cache execution plans for reuse later, which should result in lower CPU, more memory, and easier troubleshooting. Unfortunately, sometimes it goes wrong. Let’s talk about how it goes...
To access this incredible, amazing content, you gotta get Live Class Season Pass, The Team Membership, Mastering Server Tuning with Wait Stats, Level 3 Bundle (Live Classes, Lab VM Included) or Level 2 Bundle (Live Classes, No VM Included), or log in if you already shelled out the cash.
- 0.1 Prerequisites Before the Class (59 min)
- 0.2 How to Set Up Your Own Lab Server
- 1.1 Introductions and Your Lab VM (16m)
- 1.2 How to Measure Your SQL Server (89m)
- 1.3 How to Fix PAGEIOLATCH Waits (51m)
- 1.4 Lab 1: Fixing PAGEIOLATCH Waits (55m)
- 1.5 CPU Waits: SOS_SCHEDULER_YIELD (39m)
- 1.6 CXPACKET and CXCONSUMER Waits (38m)
- 1.7 Lab 2: CPU-Intensive Workload (70m)
- 2.1 Solving Waits with Readable Replicas (44m)
- 2.3 Lab 3: Planning the Work (53m)
- 2.4 Trending Waits with the Power BI Dashboard (35m)
- 2.5 Lab 4: Mixed Workload (54m)
- 3.1 Poison Wait: THREADPOOL (26m)
- 3.2 Poison Wait: RESOURCE_SEMAPHORE (34m)
- 3.3 Hardware Waits: WRITELOG, HADR_SYNC_COMMIT, ASYNC_NETWORK_IO (16m)
- 3.4 Lab 5: Architecture Changes (51m)
- 3.5 How to Triage Performance Emergencies (49m)
- 3.6 Lab 6: Emergency Triage (37m)
- Bonus: Server Hardware Sizing (44m)