RE: ODBC performance with UPS Worldship

Yes - With CA ODBC you can also play with two pieces of data to "adjust
performance"
on the ODBC setup Server tab

max field data returned box -  if you have fields larger than that setting
you may want to up this number to match.

Record Blocking size -  can up that is have large records being accessed and
will improve performance.

May have similar options with other ODBC connects.


JR
Lance, Inc.


-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@attbi.com]
Sent: Friday, March 15, 2002 12:59 AM
To: midrange-l@midrange.com
Subject: Re: ODBC performance with UPS Worldship


A key point with ODBC is having indexes that support your queries.

Also, what is the app using? VB? MS Jet? OLE-DB? Or can you know? Jet is
one of the worst nightmares, as it goes to the absolute lowest denominator.

I heartily recommend one of the Client Access ODBC manuals. The one from a
couple of releases back has some excellent chapters on making ODBC run
better.

At 07:54 PM 3/14/02 -0800, you wrote:
>Hi,
>
>I am working on connecting a PC with UPS Worldship software via ODBC to the
>AS/400 for a client.  The goal is to update the customer order freight
>charges when the UPS label is printed.  There are two UPS machines at this
>location and if this goes well, they will connect up 3 to 4 additional UPS
>machines at other locations.  I have the ODBC connection working and the
>database is being updated, but performance is slow in the test
>environment.  From the time the "Process Shipment" button is clicked, it
>takes 30+ seconds to complete a single shipping transaction.  If I edit an
>existing transaction, the entire process can take 45 seconds after the
>"Process Shipment" button is pressed.  I am not too excited about this type
>of response.
>
>I have a couple of links to check out from the archives, but was wondering
>if anyone might have some suggestions specific to the UPS application.  The
>client is using the default ODBC connections and I seem to recall that the
>defaults are not always the fastest way to go.  Any suggestions on where to
>look?  The client is on V5R1, but I do not know what version of client
>access they are using (they are using the client access ODBC driver).
>
>I will be trying a "live" test on Monday and would like to have some
>possible solutions in hand.
>
>Thanks
>
>Dave Murvin
>DRM Enterprises, Inc.
>davem@drme.com
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.

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