@ I cover many ways to improve estimates in my videos. Whether I cover the specific way you need to improve estimates is unknown. You could probably find worse ways to spend your time and money, but then again you’re already here 😃
The easiest way to answer that question is for you to open the plan XML and search for your parameter names. You might be surprised by what is there (or not there) in different scenarios.
cool, didn't know this
It’s a mad world.
You never got me a Dark Mode T Shirt, even though I bought you a drink - and now I have subscribed!! Keep being mean 😂😂
I could only get one. If you’re a size medium, I’ll send it to you.
@ as I said, YFB size for me buddy -only joshing with you 😉😂
What is that? Youth Furry Bottom?
Thanks for interesting stuff!
7:43 I wonder what’s the best approach to fix such terrible underestimation?
Don’t use the query pattern I used.
@@ErikDarlingData yeah, in this case it’s clear, but in general - that’s the question. Is it covered in your training videos? I would buy it then )
@ I cover many ways to improve estimates in my videos. Whether I cover the specific way you need to improve estimates is unknown. You could probably find worse ways to spend your time and money, but then again you’re already here 😃
Now to find a video on fixing these query patterns...
There should be a few.
Great video, is there a good way to extract - format the compiled params out of the plan XML for easy use when testing the modified query in TSQL?
The easiest way to answer that question is for you to open the plan XML and search for your parameter names. You might be surprised by what is there (or not there) in different scenarios.
Is there a new plan for each "optimise for" value in plan cache? What about pspo?
No, just one plan. PSPO doesn’t work when optimize for hints are supplied.
nice kitchen sink
Don’t pee in it.
@@ErikDarlingData what else is the kitchen sink for then?
@@douglascoats7081 Cigarettes