Lynn has pointed you at a catch-all query that will work as you have indicated. But you should also read this article SQL in the Wild - Catch All Queries[/url] by Gail Shaw in case this method causes you performance issues.
I use catch-all queries myself in the same way that Lynn recommended, so this post is by no means a slight on his suggestion.
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