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 / 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 |
What are sql built in functions?
Explain raise_application_error.
what is log shipping? : Sql dba
What is case function?
Is left join inner or outer?
What is the fastest way of accessing a row in a table?
What is the purpose of the partition table?
what happens if null values are involved in expressions? : Sql dba
what is a database transaction? : Sql dba
how can we find the select statement is indexed or not?
Write the order of precedence for validation of a column in a table? I. Done using database triggers. Ii. Done using integarity constraints
What is integrity in sql?
Oracle (3259)
SQL Server (4518)
MS Access (429)
MySQL (1402)
Postgre (483)
Sybase (267)
DB Architecture (141)
DB Administration (291)
DB Development (113)
SQL PLSQL (3330)
MongoDB (502)
IBM Informix (50)
Neo4j (82)
InfluxDB (0)
Apache CouchDB (44)
Firebird (5)
Database Management (1411)
Databases AllOther (288)