davoscollective (11/5/2013)
Great article, thanks for sharing. I've used similar constructs for flexible SSRS reports. I learned a few nice tricks, I particularly like the @debug and the line numbers, very nice.Based on Celko's war on dynamic SQL, I wonder if you'll get a response here too. Surely that would be a mark of success 😉
And thank you sir for taking the time to read the article and I'm happy to hear you learned a couple of tricks. I also have to apologize for the SQL formatting issues. I've got an email in to the editor to correct that.
If Joe Celko were to chime in with his thoughts on dynamic SQL, I'd consider it a badge of honor. Dynamic SQL certainly has its place, and this is most certainly one of them. There are cases where it can be overused and/or abused, so a healthy and productive discussion of that (here if necessary) would be most welcome.
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