RE: SQL temp space usage,what about V4R5

Ron,

Sounds like your SQL statements required creation of temporary files in
QTEMP, and you got a large number of large records in them.  If that's the
case, then this is not a phenomenon that's likely to be affected much by the
release level.  The way that the temp files are built hasn't changed
significantly since the query engine was introduced on the /38.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
---
If you would like to subscribe to the MAPICS-L mailing list send email to
MAPICS-L-SUB@midrange.com or go to www.midrange.com and follow the
instructions.

-----Original Message-----
From: Klein Ron [mailto:ron.klein@brctsg.com]

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
+---