Re: ole db/400 performance large file

[Alan Campin <alan0307d@xxxxxxxxx>]

That does not answer question but for that many records why not write as
text to IFS file and then read in via RPG to do update? No access to IFS
folder on box?

Use either regular scheduled job to do update or create a stored procedure
you call to update your database.

On Wed, Jan 13, 2010 at 3:29 PM, Jim Franz <franz400@xxxxxxxxxxxx> wrote:

> I've search the archives for this & not found a good answer.
> One of the network programmers is using the iSeries Access V5R4
> OLE DB connection to move 500,000 records from a network server
> to the System i (v5r4). The native file has no logicals, and no key.
> It is taking many minutes to load the first 10,000 and hours to load
> 500,000.
> Local lan connection. Cannot see why so slow.
> File not in use on either end. Not a huge record layout.
> How can we speed this up. It needs to run on a regular basis (weekly or
> even daily).
> We have considered ftp, but that server is off on the production server.
> Same OLE connection used for many applications, but those are generally
> random access, and no problems. Only the large file is a problem.
> Verified the network side is accumulating the records very fast.
> Jim Franz
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.