Re: ole db/400 performance large file

Two things to check

1) Make sure the file is _NOT_ journalled (fastest) or if it is
journaled that commitments are _NOT_ being done after every record but
after XXX number or records where XX is ideally = 128KB / (size of
record)

2) Do _NOT_ insert one record at a time. ODBC and JDBC both support a
batch/bulk/block insert mode. I think NET does but I don't believe
OLEDB does. At least I've never found out how to do bulk inserts with
OLEDB.

HTH,
Charles

On Wed, Jan 13, 2010 at 5: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.