Grant Fritchey (9/14/2012)
Yeah, if the question is a follow-up to a discussion in the thread, I tell them to post it to the thread and I answer it there. I won't mess up the conversation. If it's truly sensitive data (not one I've run into) I'm not sure what I'd do. I'm a little uncomfortable with private communication because it far too easily turns into free support, which ain't happening.
I've had a couple of people PM me when I was the only one who responded to their question. I also redirect them back to the thread. No sensitive data involved though.
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