kzhen (8/22/2014)
Sean Lange had this to say while the forum didn't allow him to reply:...you should check out this article. http://sqlinthewild.co.za/index.php/2009/03/19/catch-all-queries/
There are some serious performance issues for this type of query if you don't handle it correctly and Gail does an excellent job explaining how to deal with this.
-----
Thanks Sean, I'll check it out.
For an in-depth example along those lines:
How to Design, Build and Test a Dynamic Search Stored Procedure [/url]
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