Based on cursory review of the information surrounding the quote, I'm in a position of "initial reluctance to agree."
I'm thinking that part of that 97% he talks about should be addressed if it can be done without significant overhead to getting the code written and tested.
Need to take a deep dive to see if my initial position holds fast.
Then again, who am I to disagree with the distinguished Dr. Knuth! 😛
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St