Basic Training
In yesterday’s post, we covered some of the basics of designing nonslustered indexes to make queries go faster, but sometimes those aren’t quite enough.
In today’s post, I’m going to give you more of my paid training about filtered indexes and indexed views.
What I cover here is how to use them correctly, and some of the things they just don’t work well with. Again, if you like what you see, hit the link at the end of the post for 75% off.
Filtered Indexes
Here’s the intro to filtered indexes
Here are the demos:
Indexed Views
Here’s the intro to indexed views:
Here are the demos for indexed views:
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 performance problems quickly.
Oh man, you are so right. I’m trying to remember if I’ve ever seen filtered indexes or even indexed views in a third-party application. The most common comment then later on: “Didn’t work for us!” And as bonus information: “Our SQL expert advised us to use partitions!”
Heh, why is it always partitioning?
I guess that in some manager book from the 80’s it was said that partitions are the key to database performance.
Hey I like the 80s. Blame those on the 90s.
Which, of course, makes much more sense right away!
I thought I was going to need an indexed view the other day but soon figured out they were only running on Azure with 10 DTUs.
Game Boy emulator!