When you first learn about table partitioning, it sounds like puppies, unicorns, and Slip n’ Slides
As of SQL Server 2016 SP1, you can now use partitioning in Standard, Web, and even Express Edition of SQL Server.
Everything’s gonna be fast! Right?
Well, not quite. When you partition your tables, there’s a good chance that some of your queries are going to slow down. Your partitioned indexes look different to the optimizer, and it won’t always pick the fastest plan.
Learn to identify regressed queries against partitioned tables
My new course shows you patterns that slow down when you partition your tables, and gives you options to speed up your queries using index and TSQL changes.
You’ll also learn to use query execution plans to troubleshoot regressed queries using partitioned tables. You will learn what “non-aligned” indexes are, how to tell how many partitions a query is really using, and why the optimizer sees partitioned indexes differently.
You’ll also see a lot of dinosaur drawings.
Bonus: there’s a little columnstore in there, too
Partitioning can pair delightfully with columnstore indexes, so the demos in the course feature a nonclustered columnstore index as our guest star. You’ll get a peek at performance comparisons for this index between Enterprise and Standard Edition, too.
This course is currently free, so dive in!
Enroll in the course now, and you get… Sorry, this free giveaway has ended.