what happend with out using Commit,when closing cursor and
program?
Answer Posted / vish
True that we should Explicitly COMMIT the data instead of
depending on auto comit. But COMMITing after every
insert/update of data is not a very good option. Explicit
COMMIT incurs an overhead and makes the processing slow. So
if we are inserting/updating a large number of data into
table, COMMIT after every such update will make the Job
very slow, which in most of the cases, is not preferrable
for production Jobs. In fact, the COMMIT frequency should
be chosen very carefully for every program (please note we
should not have a common COMMIT frequncy for all the
programs as the data being proceesed by different programs
will be different and hence their importance & time to re-
process them also differs) keeping in mind that neither the
performance should be degraded nor the data should be lost.
Suggesstions are Welcome!!
| Is This Answer Correct ? | 1 Yes | 0 No |
Post New Answer View All Answers
What is difference between rollback and commit?
How do I connect my db2 database to ibm?
What is buffer pool and list some of them?
What is copy pending and check pending in db2?
List down the types of triggers in the db2 database?
What is release/acquire in bind?
what is a corelated subquerry?
What is cloudant database?
Can you tell me how can you find out the # of rows updated after an update statement?
How to create db2 table in mainframe?
Are view updateable?
Explain packages.
What is db2 purescale?
What is declare cursor?
What are the contents of a dclmgen?