Parameter Sniffing, Predicate Selectivity, And Index Key Column Order In SQL Server

[@holidasa]

Well, Mr. Erik Darling, I am very happy to see that you survived your last video’s jump out the window. I hope it’s only a couple of feet (less than a meter) from the ground because “this” is the sort of SQL Server content that I think is fascinating! Your content is very inspiring and always gets me thinking.

[@ErikDarlingData]

Aw, thank you! I'm glad you find it compelling.

[@mortezasafaee6981]

I wish you achieve everything you want in your career path thanks youre good man erik 17:44

[@ErikDarlingData]

Someday I will open a bar on the beach on Bora Bora!

[@douglascoats7081]

idk why youtube was set to 2x speed by default but listening to the chipmunk version of you was entertaining lol

[@ErikDarlingData]

Wrap It Up Mode™️

[@FlaggedStar]

People often say that selectivity isn't the first thing you should look for when ordering index key columns, but they rarely say what the first thing should be.

[@ErikDarlingData]

The thing that makes the query fastest.

[@TorgeirFredriksen]

What is the mystery behind "AND 1 = (SELECT 1)"?

[@ErikDarlingData]

If you had typed that into a search engine instead of the comment box, you would have come across my New York Times best selling blog post, What’s The Point of 1 = (SELECT 1) In SQL Server Queries?: erikdarling.com/whats-the-point-of-1-select-1/

[@TorgeirFredriksen]

@@ErikDarlingData Haha, sorry bout that and thanks for the clarification. I guess it's not the first time you answered this question. A nice trick to prevent trivial plan.

[@ErikDarlingData]

It is funny you asked, because I was going to record a video version of this post today.

[@TorgeirFredriksen]

@@ErikDarlingData Looking forward to it!