David McKinney (2/6/2014)
Damned if you do, damned if you don't!I find the criticism somewhat harsh. ...
Also, sorry but I find the allusion to plagiarism a little facile. This code is pretty much public domain by now, and while a heads up to Mr Moden would have been nice, I really don't feel that this is in the same ballpark as proper examples of the P word.
...
Well I did at least apologize for my harshness. Maybe I'm just having a bad day.
dwain.c (2/5/2014)
...My apologies for being a tough audience today.
I did say that I didn't consider it plagiarism also, although I understand how simply mentioning that harsh word may be interpreted as thinking it was.
I think the thing that fried my liver the most was that looping string splitter. Seeing that published again and again, when there are so much faster methods just rubs me the wrong way.
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