RE: SQL optimize for only writes

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

> at peak times I am doing "dozens" of writes at once.
> ...When we had 450,000 records in the file, at peek times, we see the 
> writes queue up.

Insert speed should be independent of the number of rows in a table,
you're just dropping data on the end of a heap. Do you have a capture of
the actual SQL statement that ran to do the inserts? Also, how did you
see the writes "queue up"? If there is a table scan occurring during an
insert then I'd say it's reportable to IBM as a (severe) bug. But I
don't think that's the case, something else is going on. Perhaps you're
trying to get the next# to use as a max(#) or something like that? 

-Walden