michael ham (3/9/2009)
Ok I found it. We added a few columns to the results and did a self join on a view 3 times to get the data. But that's just the entrance to the rabbit hole. The view is built on another view and the column joined in the self joins is in down in the other view (which is probably built on other views). Blech. Thanks everyone for your comments.
Urg .. one reason I hate views .. reminds of Microsoft Access .. I had to manage a application where they had built query on top of query of top of query. In some cases going down 10 levels; then they complained to me whey their application was slow grrr. Is there anyway in SQL Server to force it so Developers can't keep referecing view with in view with in view?
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN.
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing.
How to ask for help .. Read Best Practices here