RE: SQL Views worth it?

Views are great but stacking them (view within a view) will have negative performance on SQL rom my experience. It's far better to simply add the code you are nesting into one view. The more you "stack" the worse the performance

Thanks,
Tommy Holden

Superior Services, Lasting Relationships, Stronger Communities

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Friday, August 24, 2018 2:04 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: RE: SQL Views worth it?

My limited experience with SQL views (and views within views) for reporting is that they are invaluable. You also have tools (index advisor) that can improve performance dramatically. Running tools like DB2 WebQuery and others would have been nearly impossible with our legacy database, without using SQL views.

Personally, I would not be thinking about DDS described logical files. Just my humble opinion.

Greg

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Friday, August 24, 2018 2:11 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: SQL Views worth it?

Hi,

I'm developing a new application and trying to have the DB do as much of the work as possible.
So, I'm incorporating SQL Views but finding the throughput underwhelming.
Granted that some of the views are based on other views (in keeping with the attempt to have the DB do some work for me) but it appears that every time a view is queried the views are rebuilt by the OS.

I read somewhere that Views can be considered somewhat like logical files, but at least logicals can be set to have immediate updates as underlying physicals change.
Views have no such attribute settings.

So, what's considered best practices for SQL Views?
Should I just rewrite these things as logicals?