SQL Server caches execution plans based on the exact string that you’re executing. Comments, whitespace, line returns, it all has to be an absolute, precise, exact match. If there are any variances – even so much as a line return – then you might be troubleshooting a different query plan than the users are getting….
10 – How Plans Are Cached (10m)
SQL Server caches execution plans based on the exact string that you’re executing. Comments, whitespace, line returns, it all has to be an absolute, precise, exact match. If there are any variances – even so much as a line return – then you might be troubleshooting a different query plan than the users are getting….
To access this incredible, amazing content, you gotta get Recorded Class Season Pass, or log in if you already shelled out the cash.
- 01 – How NOLOCK Can Show Incorrect Results (10m)
- 02 – Locking and Blocking (29m)
- 03 – Deadlocks (18m)
- 04 – Trivial Plans (17m)
- 05 – Picking Index Key Order (34m)
- 06 – Missing Index Column Order (21m)
- 07 – Execution Plans are Lying Liars (24m)
- 08 – Estimates vs Actuals (48m)
- 09 – Table Variables vs Temp Tables: The 2019 Rematch (10m)
- 11 – Parameter Sniffing (19m)
- 12 – The Problem with Multi-Parameter Stored Procedures (21m)
- 13 – Dynamic SQL Pro Tips (34m)
- 14 – Parallelism (38m)
- 15 – Simplification (14m)
- 16 – Filtered Indexes (23m)
- 17 – Indexed Views (22m)
- 18 – Computed Columns (14m)
- 19 – Heaps of Sadness (11m)
- 20 – Index Usage DMVs are Lying Liars (26m)
- 21 – Resource Semaphore (37m)
- 22 – Questions (17m)
- Bonus – Building a Fork Bomb in T-SQL (11m)
- Bonus – Managed Instance DTUs (4m)
- Bonus – Memory Usage by Different Operators (15m)
- Bonus: Numbers Tables (18m)