× 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.


  • Subject: SQL temp space usage,what about V4R5
  • From: Klein Ron <ron.klein@xxxxxxxxxx>
  • Date: Thu, 25 Jan 2001 09:54:54 -0600

Hi All,

Yesterday we had an instance where 2 jobs that were running were using up 4%
or more of our system each.

Here are the specs.  We have a 620 on V4R2, running Sequel report writer.
We have 206 Gig of storage.  The two jobs that were running use very long
SQL statements and join quite a few files.  Each statement is generally in
the area of 3000 to 5000 bytes. Not that it matters except you can see than
they can be complicated statement with a lot of joined files.

Once these jobs were submitted our system ASP went from about 89% and each
15 minutes grew by about 1 to 1.5 percent until we were at 97%.  Then we
killed the jobs, which was not easy.

My biggest question or concern is if our clients go to V4R5 are they going
to be dead in the water.  I heard that SQL on V4R5 is a real hog when it
comes to system resources.

TIA
Ron
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.