what happend with out using Commit,when closing cursor and
program?
- 5 Answers
- 13013 Views
- CSC, I also Faced
- E-Mail Answers
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
How to resolve deadlock issue
What are foreign keys in db2?
What is a db2 cursor?
What os does db2 run on?
What are the benefits of using the db2 database?
How can you quickly find out the # of rows updated after an update statement?
Why do we bind in db2?
What is the syntax for seeing the columns and data types of a table in the db2 database?
What is copy pending and check pending in db2?
Following a db2 update statement, what is the quickest way to compute the total number of updated rows?
How do we specify index to include or not during bind process.
what is diffrence b/w file-aid tool and file-aid utility???
How would you find out the total number of rows in a db2 table?
What is dbrm library?
What is sqlca’s maximum length?
