If storage space is not the issue you could create an
indexed view (which physically stores te data) but can
greatly improve performance
this view and only>-----Original Message-----
>I'd like to know the following:
>If I define a view that JOINs several tables, then queryneeded, will the JOIN>select a few of the columns so that not all tables arealways the same>still be done with all the tables?
>The point is, sometimes I only need a few columns (notview that has it all,>ones), sometimes all. Is it ok just to create this oneview for each query I>or will performance be better if I create a tailored>have?