We have some situations where some large SQL and SQL Join statements can
take up 95%+ of System I CPU which affects everyone else on the system.
I understand we can optimize the SQL and will be doing so but for AD HOC
scenarios where users are creating their OWN queries we need a way to
basically say:
“Don’t let this JDBC job take more than 15% of CPU”. We have looked at the
QAQQINI performance file but that doesn’t seem to solve the problem. Any
insight or advice?
Thanks, Paul Holm
Develop Web Applications in Minutes!
www.planetJavaInc.com
760-432-0600
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.21/1454 - Release Date: 5/19/2008
7:44 AM
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
