Because it’s so easy to create & use temp tables, some applications grow to depend on ’em. If your workload creates, loads, and drops thousands of temp tables per second, you can hit a SQL Server bottleneck involving how SQL Server tracks where objects live in TempDB. It’s called latch contention, also known as PFS/GAM/SGAM…
4 – Temp Tables and Table Variables at Scale: PFS/GAM/SGAM Contention
Because it’s so easy to create & use temp tables, some applications grow to depend on ’em. If your workload creates, loads, and drops thousands of temp tables per second, you can hit a SQL Server bottleneck involving how SQL Server tracks where objects live in TempDB. It’s called latch contention, also known as PFS/GAM/SGAM…
To access this incredible, amazing content, you gotta get Recorded Class Season Pass or Fundamentals of TempDB, or log in if you already shelled out the cash.
- 0 – Prerequisites Before the Class
- 1 – How the Version Store Affects TempDB
- 2 – How Temp Tables Affect TempDB
- 3 – How Table Variables Affect TempDB
- 5 – Memory-Optimized Table Variables
- 6 – How Execution Plans Use TempDB
- 7 – Other TempDB Consumers: Cursors, Index Builds, AG Stats
- 8 – How to Provision and Monitor TempDB