In high contrast to what's in this good article, the change in the Cardinality Estimator for the upgrade from 2012 to 2016 crushed performance on several rather complicated queries and we had to use the TF (forget the number offhand) to cause the CE to revert back to the old version because we don't have a month to identify, repair, and regression test the repair. The CE change also didn't help overall general performance.
The "It just runs faster" claim MS made for 2016 just isn't true for us and actually made things worse. To say the least, I'm more than mildly pissed at the whole thing. Thank goodness they had the foresight (if that's what it actually was) to have a Trace Flag to revert the CE back to the old version.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)