RE: SQL Views worth it?

Thomas:

Are you confusing a View as opposed to an index? Remember a logical file is
really a hybrid object that contains a view and an index together.

A DB2 view is simply that, a view of the data that has selection criteria
built in.

An index provides the optimizer a way to eliminate rows from your query to
present you with only the rows you are interested in. A view would use an
index to be fast.

You'll need both views and indexes.

They are both imperative objects for modern development to make DB2 do the
work. I think you're on the right track.....


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas
Garvey
Sent: Friday, August 24, 2018 1: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?