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
Explain about cursor stability?
What are host variables in db2?
Is db2 a mainframe database?
What is table space in db2?
What is a db2 schema?
Which component is used to execute the sql statements?
What is the physical storage length of timestamp data type?
can any one provide me the link for the db2 v7 & db2 v8 manual for Z/os? i need to know about the syntax of REORG in both versions & need to know the difference as well
Which component is responsible for db2 startup and shutdown?
Mention the downsides of page level lock.
What is commit in db2?
What is copy pending and check pending in db2?
What is precompiler in db2?
How to restart a DB2 program?
Which are the db2 tools to protect integrity of the database?