According to my experience (which was not confirmed by IBM), views perform
better (i.e. the optimization process is faster) than specifying and
executing complex SQL statements directly. ´
I suspect that at least a part or the access plan is stored within the view
object.
As I see it, your problem is not using views or typing the SQL statements
directly, you problem is missing access paths (indexes) and the subsequent
creation of temporary indexes. This is the corner where you have to start
your search.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Brian Piotrowski
Gesendet: Wednesday, 02. September 2009 15:24
An: Midrange Systems Technical Discussion
Betreff: Views vs. Direct SQL - Overhead Savings?
Hi All,
Can someone tell me if there are any obvious overhead savings by using a
view to access data on an AS400 as opposed to direct SQL requests? I know
there are obvious reasons for using a view (security, optimization, etc.),
but will this result in less CPU usage?
As you may recall, we have had issues in the past with our QZDASOINIT job
being an absolute pig and consuming a lot of resources on the systems. We
have combated this issue by reducing the priority on the QZDASOINIT jobs and
are looking to move it to it's own memory pool. Would the addition of
moving these SQL statements to a view help?
Thanks,
/b;
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Brian Piotrowski
Assistant Mgr. - I.T.
Simcoe Parts Service, Inc.
Ph: 705-435-7814 x343
Fx: 705-435-6746
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
http://www.simcoeparts.com
midrange.com
