One nice option might be exporting to CSV and bulk loading to the remote.
Lack of order by should make things faster I would think.
But a large record inserted and committed individually will also be slow.
Would still need to know more info about the code being run to know how efficient the inserts are.
Maybe put sometimings in the query and the remote inserts.
Is it a local or remote server ? That will also have a great performance impact.
So many questions.........
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Tue, 2 Sep 2025 12:06:54 -0400
from: smith5646midrange@xxxxxxxxx
subject: RE: Sever pulling a bazillion rows from IBMi via JDBC (I
think)
The bottleneck is that it is transferring 22,064,447,488 bytes of data and inserting it into a windows server database (not sure which one).
Their SQL currently does not have an order by clause. I was actually wondering if having "order by RRN" would give better blocking for the SQL read portion.
It looks like they are going to have to suffer through it until they change the process to build a delta version of the file to pull.
midrange.com
