Re: Mass data insert --- HELP

But how often is a COMMIT done? Remember that for every UPDATE, INSERT, or DELETE the rollback segments are hit trying to store data for a rollback of the transaction. Doing a COMMIT after each transaction CAN slow down an app. I typically keep a counter that watches how many UPDATEs, INSERTs, or DELETEs are done, and then a COMMIT is done usually after every 20 of these actions. Doing it this way appears to make the app run faster.

BobH wrote in message <6j89p4$mqk_at_bgtnsc03.worldnet.att.net>...
>> >I need to issue many (>30,000) insert statements into multiple tables
within
>> >an application, but performance is lousy. I believe this is due to the
>> >overhead of parsing of each statement, but I'm not certain of this.
>> >
>> >Just for a performance comparison, I've loaded 20000 records into a
table in
>> >8 seconds using sql-loader. The same data using insert statements in
>> >sql-plus took 9 minutes. The sql-loader conventional load still uses sql
>> >statements, so there has to be a way of achieving similer performance.
>> >
>> >If anyone has any insight here, I'd be greatly appreciative. If anyone
knows
>> >of code that works similer to sqlloader, this would be just as useful.
>> >
>> >Thanks
>
Received on Thu Aug 06 1998 - 22:31:23 CEST