Jeff Moden (6/25/2014)
dwain.c (6/25/2014)
Even though I haven't had much time of late to devote to SQL stuff, I did find time to go back and re-read this article.Excellent new information in there Jeff! Thanks for the update.
I'm glad to hear that you're OK, Dwain. Rumor has it that there was a wee bit of "political excitement" in you part of the world.
The reports you're hearing in the press of a "repressive junta quashing dissent" are greatly overblown. <rant>Removed due to concerns expressed by a good friend and not cowardice!</rant>
Now that I could finally find a suitably covert place to say that, I feel much better.
I went to PNG last month and came back with a shed-load of project work. Coincidentally, the coup occurred while I was abroad, resulting in my only worry over the whole affair. That being that the imposed curfew might impact my return to Thailand.
They want us to build a Customs clearing module for the application we implemented for them last year. So most of my work at this time is business analysis. I also managed to land an Android mobile application from them. These projects have kept me pretty busy to the exclusion of all else.
Glad to hear someone was thinking of me when they read the news about Thailand.
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