Any time I see something like "Coding required as Subquery NOT as Join" it tells me for sure this is homework.
You'll find that few on this forum are willing to do your homework for you.
However if you make a fair attempt at solving the problem, we're likely to try to help you get it right.
Suggest you post some table DDL and sample test data in a consumable form, along with your first attempt.
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