× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Srikanth, 

<snip>
3. I tried commiting every 2nd record, this saved me about 2 to 3 minutes. I
then tried commit after every 5th transaction, this saved me about 8
minutes. This is a big time saver, I have requested for a signoff to
implement this idea.
</snip>

One of the things you may want to include in option 3 is a savepoint. After
every transaction has processed, where you would normally have had a commit,
create a savepoint. Like this:

C/exec sql
C+ savepoint nameOfSavePoint on rollback retain cursors
C/end-exec 

This prevents you from having to roll back all of the transactions sence the
last commit, it stops at the last savepoint at which point you can commit
the previous transactions.

You should invistigate the savepoint capabilities further in the sql manuals
for the options you need.

Psudo-code of savepoint processing. This code should be placed where your
commit would normally occur. 

if transaction valid
if count > commit transaction count
commit

else
savepoint
count += 1
endif

else
roll back to last savepoint
commit 
count = 0
endif

Duane Christen



NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named.  Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.