Sean Lange (10/15/2013)
If you got your quote correct that person is moron.
Well now Sean, there was no reason to hold back because we're all friends here. Why don't you tell us what you really think? 😛
I 100% agree with this and what Jeff said above also.
If I were to offer a pet-peeve, using TRY-CATCH needs to be done properly. That is, checking for XACT_STATE() and then rolling back the TRANSACTION in a properly prescribed fashion. It is particularly useful in SQL Agent run SPs that need to report when things go awry because there's no front end to handle the resulting failure.
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