|
???????????????? Are you saying you want to purchase this product? -----Original Message----- From: Graziano, Marie [mailto:mgraziano@badgermeter.com] Sent: Monday, September 27, 1999 10:00 AM To: 'BPCS-L@midrange.com' Subject: RE: Batch Billing Performance. FYI: There is a Cost$ to this -----Original Message----- From: Ata510@aol.com [mailto:Ata510@aol.com] Sent: Monday, September 27, 1999 9:48 AM To: BPCS-L@midrange.com Subject: Re: Batch Billing Performance. In a message dated 9/22/99 4:06:54 PM Central Daylight Time, dstiehl@SSASOUTHEAST.COM writes: > Good afternoon Geoff, > We don't have a list of BMR numbers for billing performance, but we have > created > a list of access paths, that when created and applied permanently, can > reduce > the billing job run significantly (one client went from 45 minutes to 9 > minutes). > > Please contact me at Falk Integrated Technologies, Inc. for additional > information at 336.315.1005 Using generic lists of access paths developed for someone else's system (and possibly release?) is not necessarily the best way to approach improving performance. You should look for real BMRs, to see first of all if SSA has found or changed anything, and then use something like DBMON or Centerfield Technologies tool to find and build access paths on a regular basis (such as after applying a cume or new set of BMRs). If it the program still doesn't work quickly enough, call it in to SSA as a performance problem because there are SQL constructions that can not be helped via an access path. Also, be aware that such lists of access paths can become outdated, as BMRs may change or remove the SQL that made the access path useful in the first place. Be sure to test the paths one by one and if they do not seem to improve anything, or if you can not tell which statement they were built for - don't use them, since they do add some overhead to interactive processing of the files they are built over. Some people have put on lists of access paths that were designed for another customer or release, and had their systems run slower afterwards, so be careful when doing this! +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
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.