|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Richard, nothing complicated, read a record insert a row! I sort of inherited this to speed it up, so I took most of it out of DB2 to avoid the journaling overhead. The last bit was to try to speed up the periodic rebuild process which still had DB2 processing. Because of the way things are set up around here, I could not drop and recreate the table with DDL, it would have needed to be part of the design plan, but because I am in the DB Admin group, I can get away with some things like dropping and recreating indexes and the like. It is surprising that ops didn't raise a fuss, but the way this is written, it is low overhead, averages about .8 thru 2.0 cpu depending on what else is in the mix. So I guess because I help them when they need it they decided to let it run? Hate to waste that get outa jail free card though! -----Original Message----- From: Richard B Baird [mailto:rbaird@esourceconsulting.com] Sent: Tuesday, July 02, 2002 11:57 AM To: midrange-l@midrange.com Subject: RE: CLRPFM and DB2 Tables
As an Amazon Associate we earn from qualifying purchases.
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.