Re: Rein in QZDASOINIT

Brian,

Honestly, I've found that many windows developers don't really
understand RDBMS, especially the i.

Often times, the SQL statements they are using are dyamic, instead of
static and/or prepared statements. This is doubly bad since dynamic
SQL allows for SQL injection attacks.

My preferred method, is to have all SQL statements in stored
procedures on the i, and the web pages simply call those stored
procedures.

In any event, make sure you have the indexes needed to support the
statements being use. iNav in v5r4 offers some nice tools to see what
you may be missing.

Charles

On Fri, Jan 23, 2009 at 2:15 PM, Brian Piotrowski
<bpiotrowski@xxxxxxxxxxxxxxx> wrote:

Happy Friday, All!

With the increased amount of web pages we are using on our systems, I am noticing that the QZDASOINIT jobs appear to be chewing up more and more CPU cycle times. That being said, I am looking into moving the jobs to their own subsystem and changing the memory pool on them (as per a wiki document I found). However, I'm wondering if there's anything else I can do to curb the bad habits of these database queries?

One thing I think will make a difference is to move to a different strategy other than "select X for lib.member" used in virtually all of the web pages we host. However, I thought I'd hit the group up for some advice to see what everyone else is doing.

If it makes any difference, the i5 is being used to house the data and we have Windows Server 2003 Web edition hosting the web (ASP / ASPX) pages. It is these pages that access the i5 through an ODBC string.

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.