sql vs. pl/sql: speed issue

hello all,

I am trying to do a batch update (on a single table) on perhaps 5-10% data out of a 30 mill. rec. table and I am comparing two methods:

1. doing a straight update sql statement (the 'where' clause is a bit complex) therefore a full table scan is performed; entire operation takes less then 5 minutes;
2. taking the same operation under a 'cursor c ... select rowid ....for update of ...' pl/sql statement and then updating the records in the body of the procedure. This operation took around 7 minutes.
3. Does that mean that one should, if at all possible, use pl/sql only when absolutely necessary!?
4. Is there any way to do a large sql update and commit every x records (and not use a huge rollback segment) or is that possible only in pl/sql!?

thanks much,

Cosmin

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Sat Feb 12 2000 - 14:35:57 CST