Is there any problem if we use commit repeatedly after each
dml statement in a plsq procedure ? (eg. there are 10 update
stmt and using 10 commit stmt after each update stmt)

Answer Posted / kiran iyer

Commiting a record frequently will effect the performance as
oracle internally would wait for the transaction to get
commited and then flush the RBS and then would go ahead and
read the Next Record. Hence it is not a good Practice to
commit records frequently. Records should be commited in a
batch.

Is This Answer Correct ?    4 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

what's the difference between a primary key and a unique key? : Sql dba

500


Can we use rowid as primary key?

535


Why is nosql good?

585


How do I save the results of sql query in a file?

529


What is the primary use of normalization?

519






What are some predefined exceptions in pl/sql?

544


does sql support programming? : Sql dba

603


What is the difference between rollback and rollback to statements?

573


Why do we need sharding?

519


Why should I use postgresql?

557


Does varchar need length?

514


Is coalesce faster than isnull?

498


Explian rowid, rownum? What are the psoducolumns we have?

556


Does truncate table reset auto increment?

520


How can you view the errors encountered in a trigger?

539