Parameter Sensitive Plan optimization - SQL in Sixty Seconds 200

[@savananjaria9169]

“If you like what you see here…” - Always love to see such informative and creative content here. Congratulations on your 200th video gem 🎉

[@PinalDaveSQLAuthority]

Thank you so so much. You always motivate me. I found myself because of your mentorship.

[@tanvirrahmantech]

i have done probably 3 of your course in pluralsight.very good tutorial.helped me learn a lot

[@PinalDaveSQLAuthority]

Thanks

[@TheBrentOzar]

Welcome back! Tell the artist I said hi. 😆

[@PinalDaveSQLAuthority]

Thank you so much. I am very much motivated. The artist is also very happy to hear from you too - super happy!

[@MiningForPies]

Great to see you back Pinal.

[@PinalDaveSQLAuthority]

Thank you

[@moizsyed465]

Nice to see you after a long time

[@PinalDaveSQLAuthority]

Thanks!

[@stevefatland7704]

Van Gogh. Good video - thank-you, Pinal!

[@PinalDaveSQLAuthority]

Not the legend Van, but mere mortal my daughter.

[@oivvv9218]

a really good feature. but guessing it will take a while before SQL Server 2022 gets adopted in a few of our systems :)

[@PinalDaveSQLAuthority]

That is correct

[@avinashrauniyar3784]

Pinal dave, Which index have you created, is it clustered or non-clustered index? Requesting to clarify on it. Got it is the nonclustered index created on a heap as per the execution plan.

[@PinalDaveSQLAuthority]

Great

[@undergraduate6050]

Ty Dave Sir.
I want to learn sql server from you.
Do you provide any courses?

[@PinalDaveSQLAuthority]

All my learnings are available for free online.

[@undergraduate6050]

@@PinalDaveSQLAuthority
Ty sir.

[@TheANKUSHVIDEOYOUTUB]

Any plan on Synapse SQL?

[@PinalDaveSQLAuthority]

Not yet.

[@goodjuanma]

Table Scan in the second query execution plan?

[@PinalDaveSQLAuthority]

Yeah

[@goodjuanma]

@@PinalDaveSQLAuthority Wouldn't that be terrible for execution performance? This plan seems to get 40% of the total execution cos versus the previous, seemingly equal, 20%.

[@MiningForPies]

@@goodjuanma no.
In the second execution plan, using the index would have resulted in hundreds of thousands of key lookups, essentially a table scan in a loop. Scanning the table is far, far more efficient in this case.