RE: Best way to access DB2 from a Windows .asp and Java application -- MIDRANGE-L

Hi, Dave

ODBC is not inherently a poor performer - that's a myth. The problem usually lies elsewhere - using JET from VB will be awful - 2-3 orders of magnitude increase in ODBC calls over the better methods. Also, indexes are needed to make direct statements work better. OTOH, often the fastest access, even for reads, is to use stored procedures that use native IO in the RPG program.

Let me suggest a couple resources:

1. "Client Access Express for Windows ODBC User's Guide V4" at
<http://publib.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/QB3AU900/CCONTENTS>
is the latest version of the 95/NT guide that was so good.

2. "Got Those Query Blues?" at
<http://www-1.ibm.com/servers/eserver/iseries/db2/queryblues.htm>

3. "Diagnosing Client-Server Performance Problems" at
<http://www-919.ibm.com/developer/client/performance/csperd.html>

Something here should help.
Vern

At 06:28 PM 5/7/2004, you wrote:

Walden,

Thanks for your information.   I thought I'd create stored procs for
the programmer.   The programmer wants to only use stored procs for
other then reads.   For reads he wants to go direct.   Personally, as I
understand generating stored procedures generates static SQL, I thought
that would be better than direct statements which creates dynamic SQL;
performance consideration plus more secure.    I wonder if ODBC is a bad
performer?   But in this case there won't be much use so performance
should not to bad in any case.

I want the programmer to modify the application "whatever it
takes(since it is not too extensive an application)" to use DB2 and get
away from Mickysoft Access.

Yep, some of the program is in .asp and some in Javascript.

Any recommendations would be welcome.

Thanks again,

Dave Odom
Tucson, AZ


from: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
subject: RE: Best way to access DB2 from a Windows .asp and
        Javaapplication

Dave,

Good choice to get away from Access, hell, even I don't like it.

You can use ODBC and _still_ use stored procs. ODBC is a transport
layer, not much more. You can issue direct statements (update this,
select that) or call stored procs and handle result sets.

There are several other ways you can talk to the iSeries (OLE/DB,
sockets, .NET, JDBC, etc.) but they all will take changes to the
application. The least number of changes would be to replace the
Access
ODBC driver with the iSeries ODBC driver. How much do you want to
rewrite the application to replace the database?

-Walden

PS. ASP _and_ Java?? Strange mix.