How Eager Index Spools Cause Performance Problems
Going Further
If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that, and need to solve database performance problems quickly. You can also get a quick, low cost health check with no phone time required.
Related Posts
- Indexing SQL Server Queries For Performance: Equality vs. Inequality Searches
- Why Read Committed Queries Can Still Return Bad Results In SQL Server
- Join Me And Kendra Little At PASS For Two Days Of SQL Server Performance Tuning Precons
- Updates To sp_QuickieStore, sp_HumanEventsBlockViewer, and sp_PressureDetector
I followed along and took it one step further, indexing the Users table as you mentioned:
CREATE index ix_users_rep on dbo.users (reputation, id) include (displayname) with (maxdop=8, sort_in_tempdb = on);
That further reduced my query time from 12 ms to effectively 0 ms. This has been a great series, thanks for publishing it.
Very good! Thanks for watching, and for the kind words.