SQL Server builds an execution plan tuned (kinda) for the first set of parameters it sees, and then reuses that same execution plan for all kinds of other parameters. That’s usually a good thing, but if the plan gets freed out of memory for some reason, then you’re very, very susceptible to whatever parameters happen...
To access this incredible, amazing content, you gotta get Live Class Season Pass, The Team Membership, Mastering Query Tuning, 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
- 0.4 The BE CREEPY Method (14m)
- 1.1 How SQL Server Builds Query Plans (56m)
- 1.2 Cardinality Estimation (38m)
- 1.3 CTEs, Temp Tables, and APPLY (31m)
- 1.4 Lab 1: Improving Estimates (56m)
- 1.5 Using sp_BlitzCache to Find the Right (Wrong) Queries (46m)
- 1.6 Lab 2: Analyzing a Running Workload (74m)
- 2.1 Tuning Columns & Rows in Result Sets (42m)
- 2.2 User-Defined Functions (29m)
- 2.3 Lab 3: Changing Results and Parameters (108m)
- 2.4 Dynamic SQL Pro Tips (53m)
- 2.5 Lab 4: Advanced Rewrites (62m)
- 3.2 Lab 5: Parameter Sniffing (89m)
- 3.3 Avoiding Deadlocks (23m)
- 3.4 SQL Server 2017 & 2019’s New Robots (17m)
- 4.1 Lab 6: The Final Setup (7m)
- 4.2 Lab 6: Index Tuning (33m)
- 4.3a Lab 6: usp_Q6627 (29m)
- 4.3b Lab 6: Logging sp_BlitzCache to a Table (5m)
- 4.3c Lab 6: usp_Q7521 (25m)
- 4.3d Lab 6: usp_Report3 (15m)
- 4.3e Lab 6: usp_FindRelatedPosts (24m)
- 4.3f Lab 6: usp_Q6627, Take 2 (34m)