Re: Performance Impact of SQL Views (was: SQL Statement length)

On Fri, May 13, 2016 at 11:09 AM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

Now, we may still be lacking in our understanding of what is going
on under the covers of SQL, however we are now shying away from creating
views willy-nilly as the spirit moves us. The reason is because we now
understand that a view has to be rendered at the time it is opened and
such rendering can have (and has had, in our case) a major performance
impact on the system.

​I think the idea is that if you need a given SQL statement, the
performance hit is there regardless of rather or not it's in a view.

​Setting up a well tuned view that can be reused is a better idea than
having basically the same logic in different places that might return the
same results but be written different enough to perform differently.

Charles