@sp_BlitzErik I had a bit of a revelation yesterday. It suddenly struck me that there's also no documentation for showplan elements. Think how long we had a single number for memory grant without even a unit of measure. I guess I'm being unfair; they're just following tradition.
@sp_BlitzErik It's not even valid xml is it? But yes, good point.
There's also this change where the width of arrows now seems to follow pre-residual filter rows read rather than actual rows read. I can see why that would be useful, but it's confusing at first. Also an undocumented change, AFAICT.
I have an strange behaviour in my queries, probably I'm missing something...
I have a customer with very long queries that are being pre-builded by the Analysis Tool they are using... I was trying to optimize these queries creating new indexes. I managed to do that but some of the queries starte...
@PaulWhite Yes, that's it -- Plan Explorer is multiplying the numbers of EstimateIO, EstimateCPU, EstimatedRowsRead on the inner table etc by the number of EstimateRows on the outer table to get these figures.
Insofar as terminology, what exactly is "microcode" and if it can be updated, how does it differ from firmware?
This question is not a duplicate of this question (as far as I can tell) which I've also asked about modifying microcode. Here I'm strictly wanting to know how to use these terms prope...
@sp_BlitzErik How about this quote: "The applications or services that hold your registry file may not function properly afterwards. No user action is required."
You know, @JoeObbish, if you spent half as much time causing query issue and twice as much time making delicious jerky... you'd have 10 times as much jerky and 1/4 the performance issue ;)
"All 1000 rows will be returned to the client, so one billion rows will be read from the BIG_HEAP table. This is indeed what happens and the query takes around 2 minutes to complete on my machine."
that one might be good
they can take as long as you want though
just need to change the number of rows in the outer table
the only gotcha that comes to mind is that sometimes you can get a spool that ruins the demo
because i'd have to pull the database, table, and schema out of the query for whichever ones are involved in the row goal and then dynamically query net new dmvs to get page or row counts