Table partitioning makes execution plans a bit more confusing
How much work did that query really have to do? It can be tricky to tell!
I have a new online course which walks you through decoding execution plans, including whether or not partition elimination occurred. In this first 10 minute video, I go over concepts for table partitioning and partitioned columnstore indexes:
Next up: partitioning demos
Get a real-live look at partition elimination in actual execution plans, cached execution plans, and Query Store in this 20 minute video:
Enroll in the course for free to get more videos and a desktop wallpaper
Enrollment is free for a limited time. You get access to all the videos and the course quiz through the end of the year, and you can download the course PDFs, desktop wallpaper, and demo scripts to keep learning and experimenting on your own.
Free course: Troubleshooting Blocking and Deadlocks for Beginners
Free online course: Query Tuning with Hints & Optimizer Hotfixes
Hi “Dear SQL DBA”
I loved your above video. But somehow I was expecting to see the columnstore index being used. Am I missing something?
I show both rowstore and columnstore partition elimination in the full course. The next demo in the series shows that with columnstore you may get rowgroup elimination even if you don’t get partition elimination (and later on in the course you’ll see that you can get both).
The course is still free to enroll in: https://sqlworkbooks.com/course/the-weird-wonderful-world-of-execution-plans-partitioned-tables-columnstore-indexes/