How do I tune a SQL statement with the wrong Join Type

[@vishvendradeepak1419]

Awesome 👏 explanation. Many thanks Maria.

[@aidangmccarthy]

Thanks Maria. Elegantly explained as always 👍

[@SQLMaria]

Thank you! 😃

[@7895sk]

Very interesting. Thank you. I think there is a misprint at 6.03 min. We should read "STALE_PERCENT" instead of "STALE_PRECENT"

[@abhimonu29june]

Thanks Maria ..for the detail explanation

[@shivamkr278]

Thanks Maria for detailed explanation 👍

[@SQLMaria]

My pleasure 😊

[@amfattah2011]

Many thanks Maria.

[@avreddy666]

Very nice explanation..

[@iftikhar8508]

How do you tune sql for OLTP systems?

[@Elfcheg]

Nice! Thanks for sharing!

[@SQLMaria]

Thanks for watching!

[@jamsher731]

Hi Maria, Can you please make video on Wrong Join Order,

[@HemantKChitale]

As the table grows larger over the months and years, the "10% staleness" translates to ever increasing absolute numbers.

[@SQLMaria]

Hi Hemant, you are correct. The large the table becomes, the longer it takes to reach the 10% staleness threshold. For many data sets, this works well, as the number of distinct values in each column doesn't change much as the data volume grows. For example, the NDV for product_id won't change as we make more sales as we only sell a fixed number of products. However, the NDV will continue to increase for some columns like sales date. If you have one of those situations, you have several options, as specified in the video.

[@albertogonzalez5114]

Thanks so much!

[@venkatv2973]

Could you please explain 10053 trace file ?

[@SQLMaria]

Honestly, Venkat, No one can fully explain every aspect of a 10053 trace. It's not meant to be read from top to bottom. But throughout this SQL Tuning series, I'll point out what keywords or phrases you should search for in the 10053 trace to help you determine the root cause of problems you may see.

[@vishvendradeepak1419]

Good question and good response from Maria .