While I agree that maintaining tons of views can be a pain, I've found performance differences to be negligible. One thing you need to be sure of is that you have the view's FetchSize set to -1. This ensures that all of the records are fetched at once. Before we did this we found that any view that returned more than 100 records (the default FetchSize) was much slower than SPT.

>We have, and SPT wins every time. In fact we're currently in the process of converting a massive data import application from using remote views to SPT for performance reasons. Maintaining 165 remote views is not fun!
>
>SPT has much less overhead, and you don't have to deal with the database container. Of course, this means you have to take care of all the housekeeping yourself in code, so if time is a factor, remote views will get you up and running faster. But if you have the time, I'd recommend the pass-through method.
>
>Just my 2¢!
>
>>Has anyone done any comparisons on SQL pass through and remote view as to which is better gives you better performance?