Re: Sever pulling a bazillion rows from IBMi via JDBC (I think)

Hello Jim,

Am 03.09.2025 um 13:45 schrieb Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>:

Again, that depends.

It always does. :-) Because the destination is unclear, I can only apply general advice.

First off, how many indexes are we discussing? Secondly are they designed correctly so the access paths can be shared, IE create the longest access path first then let the shorter ones use it.
[…]

The destination database is not IBM i, as far as I've understood. The source is.

Not sure how much of your further hints are still relevant in practice, considering the increasing ubiquity of solid state memory vs. true DASD (Disk Arm Shaking Devices). Please note the word "practice". :-)

Creating an index is quite expensive, updating it less so usually.

Uhm. The goal set by the OP was to minimize run-time, not system resource consumption. I know the term "expensive" as another word for "resource intensive". What's your definition?

:wq! PoC