Re: using Views vs Table

One specific con...views involving aggregate columns can be murder on performance. Any query referencing the aggregate column triggers a "temp table for view" to be created at the outset. Before it does anything else it will create a temp table to be the view. If the table behind the view is large and the query doesn't have explicit criteria limiting it's scope, you can be in for a very long wait. I've had cases where this caused a 3 second query to take over 40 minutes. If you have control over it, never use an aggregate column on a view. "Wayne" <ngte4-gl@yahoo.com> wrote in message news:fe6569b.0405051544.14a5732a@posting.google.com... > Hi All, > > Just curious, is there pro/con write SQL query using "view" instead > the actual "table"? My programmer created many VIEW and he using those > VIEWs in his SQL query. I wonder if using VIEW, it may cause > performance to the system or overhead. Thanks for your input. > > --Wayne