SQL Server Execution Plan Basics

[@USA_to_Asia_in_2024]

This is Pure Gold (as Manosphere Highlights Daily channel would say).

[@Kevin3NF]

Hope it helps you :)

[@steveabba8463]

Thanks Kevin for the simplicity and examples!!!

[@Kevin3NF]

You're very welcome!

[@shenidan2023]

Many thanks for posting. Surprised the likes and views are so low but for me it's been very useful .

[@shilk4301]

This is the best video I have seen . Easy to understand . Just started to learn and was lost . This helped me a lot . Thank you 🙏

[@Kevin3NF]

You're very welcome!

[@ManishChopra]

Right to left and from top to bottom. Thanks kevin!

[@isaguclu941]

The best explanation I have seen! I can't thank you enough for it.

[@brunovecchietti]

Finally I understood execution plans. Thanks!

[@Kevin3NF]

Great to hear! That barely scratched the surface...this is everything: www.red-gate.com/simple-talk/books/sql-server-execution-plans-third-edition-by-grant-fritchey/

[@jatindersingh2241]

wow, you explained everything i was looking for a while , Thanks a lot

[@Kevin3NF]

Glad it was helpful!

[@user-uf9fj9or6w]

omg you saved my energy and everything thanks alot

[@Kevin3NF]

Glad it helped!

[@simusprime]

This is exactly what I have been working on the last 2 weeks! Nice breakdown!

[@Kevin3NF]

Working on such a video, or learning to read Plans?

[@simusprime]

@@Kevin3NF Im going through our software and optimizing queries. Especially missing indexes.

[@Kevin3NF]

@@simusprime Awesome! Good luck...and don't over-index! Run an "Unused Index" query as well to look for possible dead weight.

[@menasheaharonian9183]

Very clearly put, thanks. Looking for more of your examples and explanations

[@JaswantSingh-di8nu]

Very well explained with examples. Thank you, Kevin!

[@Kevin3NF]

Very welcome!

[@Surianiaziz]

Great example with clear explanation. Definitely a subscribe!

[@selvamkumar1982]

Thanks Kevin... Can u post performance tuning in wild card searches....

[@Jerry-zf3cn]

Would have been more helpful to put that link to your other video in your summary where it could have been clickable...

[@Kevin3NF]

Thanks Jerry...I have added the link to the description of this one

[@sridhartn83]

Very nicely explained, thanks.

[@avinashsahu4853]

You are awesome!!! looking for this from a long time.. Simple and Great explanation

[@oleksandrbondarenko1129]

Thank you for the good explanation and the examples!

[@tobytr]

Well done, very clear explanation

[@tonycovarrubias5931]

This is exactly what I was looking for.

[@Kevin3NF]

Awesome! You should get Grant Fritchey's newest edition of his query plan book...

[@DavidGilden]

Well done, I actually learned something!

[@krishnakanthlenka2323]

Excellent Explanation. What if there is no clustered index or Primary column. Will it cost more to search another column which is LastAccessDate which is not included in the non clustered index and also query uses non clustered index and is it look for look up column by that time ?

[@Kevin3NF]

No Clustered Index makes the table a HEAP, which will almost always be harder to search for extra columns that are not in the NC index it is using now. www.brentozar.com/blitz/heaps-tables-without-primary-key-clustered-index/

[@krishnakanthlenka2323]

Thank you Kevin for your valuable time.

[@hank91918]

great stuff, thanks Kev!

[@abdulkhadershaik4738]

Good explanation..thanks

[@Kevin3NF]

Glad you liked it

[@MasterBeastieshow]

Kevin Good job. Please upload more videos

[@tabs5375]

Brilliant video :) Quick question, what would be the best way to optimise a query that uses wildcards? E.g. select * from table where name like 'Kevin%'; Would you have to reevaluate the query to see if bringing back all the Kevins is the right approach?

[@Kevin3NF]

Thanks Ryan! You would want a non-clustered index on [name] for a 'Kevin%'...and you might see an index scan instead of a seek, depending on how many variations of Kevin there are. If you try '%Kevin%', your index will no be used. That leading wildcard changes everything. Always test and evaluate periodically. Missing and Unused index queries are my favorite ways to evaluate my index strategy

[@Monty6874]

Awesome video.

[@kusalrathnayake2264]

Thank you. Good Job.

[@Akshay-Raut]

Are the cost of each operation accumulated from right to left or are they independent ?

[@Kevin3NF]

Each operator has its own cost, and the entire query is shown as a cost in the query stats DMVs: www.scarydba.com/2017/02/20/estimated-costs-queries/

[@ashwinghorpade5917]

best explanation

[@KumarAnalytic]

Thanks sir, I'm from India

[@TheNanamimijojo]

if cost =20% for stored proedure this good or not

[@Kevin3NF]

There is no way to tell...it totally depends on what the procedure is doing, and how the Query Optimizer decide it is going to execute the code in the proc, get the data, allocate memory, etc.

[@TheNanamimijojo]

@@Kevin3NF i mean excution plan the estimaton cost is 20%

[@AAA-pt7ix]

hi

[@aangfahar4704]

10:27

[@ankitabillore]

This is very helpful, Thank you.