Re: SQL optimize for only writes

at peak times I am doing "dozens" of writes at once.

to give the bigger picture...

writes are done via PHP(odbc) to system i table (no key on physical)

Every 30 seconds a RPGLE program wakes up, opens the logical (selects
"unprocessed" records.)



When we had 450,000 records in the file, at peek times, we see the writes queue up.

I have purged and reorged the file down to 25,000 records, and the process flows smoothly.



Walden H. Leverich wrote:

Also, if you're doing 400K inserts,

Would the OP please clarify... I didn't read that as doing 400K inserts,
rather the table had 400K rows in it. He's inserting "a lot" but I took
that as dozens to hundreds, not as something where the insert itself
needed to be optimized.

Regardless, we're in agreement, there's nothing on the insert that
should result in a table scan. Something else is going on.

-Walden