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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hello,

Am 02.09.2025 um 18:06 schrieb smith5646midrange@xxxxxxxxx:

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).

You name two possible bottlenecks.
- Transferring
- Inserting

To find solutions, a firm understanding of which part is the real bottleneck is important. Identify the problem.

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.

I don't think that "order by" makes a difference. From my limited experience, I assert the real brake shoe is the database insert.

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.

Which might be even worse, because creating the delta might take longer and add way more load on the i and the destination database.

The only sane approach is have one database with authoritative data, and not two. I understand this sometimes isn't easy to achieve.

:wq! PoC

This mailing list archive is Copyright 1997-2025 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.