Tuning tips (some good practices and DOs and Don'ts)

Tuning tips (some good practices and DOs and Don'ts)

 

  


***********************
Your mail has been scanned by InterScan.
***********-***********


Dear DB2 gurus,



As they say in every DBA Tuning forum: 'Prevention is better
than cure', hence tune the application first.



So in similar lines, Can we have a common platform to share
our suggestions (Dos and Don'ts) or may be some of our tuning
experiences which we might have encountered and might have been
benefited with.



Also, can we have some method or an standard operating
procedure to debug problems like: slow processing, High CPU utilization
etc.



One such tuning experience which I would like to share with
you all is as follows:-



A java application program was supposed to insert or update
data, record by record from the file into a database base (based on some
logic which decides that whether it shall be an insert operation or an
update operation). The speed with which it was happening was around 20
thousand records per hour. The tuning was obtained by using a LOAD
command which loaded the data into temporary table in less than a
minute. And later on logic was built in stored procedure which used to
fetch data from temporary table and actually inserted or updated the
data in main table. In this way I got the improvement in processing
time.



Regards

Dharmesh Bajpai




***********************************************************************************
This message is for the named addressees' use only. It may contain NSDL

confidential, proprietary or legally privileged information. If you receive

this message in error, please immediately delete it. You must not, directly

or indirectly, use, disclose, distribute, print, or copy any part of this message

if you are not the intended recipient.Unless otherwise stated, any commercial

information given in this message does not constitute an offer to deal on

any terms quoted. Any reference to the terms of executed transactions

should be treated as preliminary only and subject to our formal written

confirmation.
***********************************************************************************

DB2 & UDB email list listserv db2-l LazyDBA home page