I had 135,000 sql statements to process against 5 different files. I had the jr. programmer write out sql statements (meaning write out of a program, not "write" with a pen), and then I copied like 45,000 into inav's sql interface to run.
Slow was an understatement. Took like 5 or more hours for those 45,000.
So for the 90,000 remaining I found runsqlstm and while it asks for a source file and member, it didn't like my flat file in qs36f, so I simply dumped them to the ifs and used the stream file option. Took maybe 10 minutes to do the rest.
While the inav feature is nice as it will show you an error, slow is the nature of the beast. Sure I use it alot when I have a dbfile that I need to reorganize some fields or such that inav (SQL/DDL) won't let you do, as I will simply click generate sql, take the sql make my changes and go delete the file and then run that window. But if you have alot of transactions, it is not the way to go.