Eirikur Eiriksson (4/19/2015)
Grant Fritchey (4/19/2015)
Eirikur Eiriksson (4/19/2015)
spaghettidba (4/19/2015)
Has anyone seen the last comments for Friday's featured article? I'm sorry for provoking such a bad reaction, I didn't mean to do that.Did I say something wrong? Was my comment too harsh?
Nothing wrong with your comment, in fact I was about to post almost exactly the same comment when I saw yours.
😎
I looked but couldn't find the post. Link?
It's here.
😎
I saw it but didn't notice it was a republish. Didn't comment though because I expected the author wouldn't like what I had to say. I like what Jeff has added to the thread about the proof being in the performance test.
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