>Caching will happen because the second set of joins and the where clause is the same as the first. SQL Server does the same thing via "Simple Parameterization"

We're not talking about doing the SQL two times in a row. It is slow the first time if I don't have the inclusion of additional fields. So, this shows there is something going on somewhere. If I only include the field such as Member.Numero,Item.Numero, it is slow. But, if I include the field such as Member.Numero,Item.Numero,Status.*, then the result is immediate. So, I cannot understand what you mean by Caching. Maybe I missed something?