Efficient Views..

Hello,

I'm creating a view between two tables A and B. Is there overhead to defining this view with *all* the columns in A and B compared to *just* the columns the people accessing it will need. The join is straight forward (i.e. A.x = B.x).

The reason for the question is that, currently, I don't really (nor they me thinks) know what columns from A and B they need -- only that the join is necessary because some columns will be used from both tables.

Another thought, when is the query of a view optimized? At creation? After the additional search criteria has been added in? Any inherit optimization problems with views? Liked to know because I'm pushing views right know for common joins.

Thanks for any input ...

John Dennis Received on Sat Jun 04 1994 - 04:32:47 CEST