Re: Need Help on Views

Hi Scott,

My point of view is you should use views where is it possible. They don't damage performance in any way. They provide additional security level and additional independence level between your application and data. Your application should always use SQL statements like select * from <view name>
or
select * from <view name> where <some condition> where condition is generated dynamically in application. You can always change view definition without changing client side code using this approach. This is very flexible.

             Andrew Protasov

Scott Fletcher wrote in message <35505803.0_at_newsprime.tidalwave.net>...
>I am trying to learn more about views...when to use them and when not to.
I
>know views can simplify dealing with a complex query, but I more interested
>in the performance issues. I have been told views will significantly
>enhance performance on table joins or when retrieving lookup values, but
>I've also read that too many views could hurt performance, but I can't find
>out why. Are there any "rules of thumb" to go by? Are there any sources
of
>information to refer to (books, sites, white papers)? Thanks in advance.
>
>-Scott
>
>
Received on Thu May 07 1998 - 08:49:58 CDT