Does SQL Server propagate WHERE conditions in complex views?

Question

I\'ve followed this question with a full example in case it isn\'t clear what I mean from the question.

I\'ve made a view which joins data from about five tables. The t

Answer 1

Generally, the optimizer will handle this with aplomb, but as the query and implied subqueries become increasingly complex, the chances that the optimizer will choose the proper execution path diminishes accordingly. This can be aggravated by having more indexes on the tables, or very similar indexes on the tables it will be examining.

As a general rule, I try to discourage joining to views, and I strongly discourage creating views that are comprised of other views.