Re: Speeding up ODBC -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Speeding up ODBC
From: "Diego Kesselman (GMAIL)" <diegokesselman@xxxxxxxxx>
Date: Thu, 9 Jul 2015 11:52:45 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Rob,

have you tried changing block size to something between 256 mb and 512 mb?
Can you share QZDASOINIT prestart jobs priority?
Have you tweaked the QZDASOINIT PJ or related jobs/subsystems/Shared Pools?

El 09/07/2015 a las 10:30 a.m., rob@xxxxxxxxx escribió:

I know this comes up on the list a lot, and forgive me for not searching,
but the dilemma is something like this:
You run this sql statement that does a select with ordering, where's,
grouping, etc and it takes forever in ODBC but runs pretty fast from
STRSQL.
How do I tell ODBC to do a bulk of the processing on the IBM i?

Rob Berendt

Diego Kesselman

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.