Nice work on the query mod. Like I said, I figured that info must be somewhere in those tables I SELECTed against.
On your second point, I guess it depends on what your requirements are. If the query plan always chooses one over the other, it would make sense to at least mark these some way so they can be identified and analyzed later. I can't confirm whether that is always the case.
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