Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.
on May 3, 2016
Learn why SQL Server’s table partitioning feature doesn’t make your queries faster– and may even make them slower.
In this 20 minute video, I’ll show you my favorite articles, bugs, and whitepapers online to explain where table partitioning shines and why you might want to implement it, even though it won’t solve your query performance problems.
Articles discussed are by Gail Shaw, Remus Rusanu, and the SQL Customer Advisory Team (SQLCAT). Scroll down below the video for direct links to each resource.
Ready to Dig In? Here are the Links Discussed in the Video
Gail Shaw’s SQL Server Howlers - “I Partitioned my Table, but My Queries Aren’t Faster.”
Remus Rusanu’s Stack Overflow answer - “Partitioning is Never Done for Query Performance.”
SQL CAT Team - Diagnosing and Resolving Latch Contention
Connect Bug - Partition Table Using Min/Max Functions and Top N - Index Selection and Performance
Kendra Little on the Brent Ozar Unlimited blog - “Why is this Partitioned Query Slower?”
Books Online - Using Clustered Columnstore Indexes