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


Please Help Members By Posting Answers For Below Questions

List down the types of triggers in the db2 database?

600


What is the advantage in De-normalizing tables in DB2?

758


What is image copy in db2?

580


what is the sqlcode -501

11338


What is meant by union and union all?

597






How is deadlock resolved?

658


How to check last update on table in db2?

636


How would the varchar column remarks defined?

647


My sql statement select avg(salary) from emp yields inaccurate results. Why?

653


What is database manager in db2?

559


If the cursor is kept open followed the issuing of commit, what is the procedure to leave the cursor that way?

711


How to test SQL -911 error while developing COB-DB2 program

6732


What is db2 stogroup?

685


Explain about cursor stability?

631


Explain the benefits you can get from mainframe connect?

526