Help: Tuning "temporary" tables

From: Gerard M. Averill <gaverill_at_chsra.wisc.edu>
Date: 1997/12/03
Message-ID: <664hjj$1ffs$1@news.doit.wisc.edu>#1/1

I've got a table which serves as a sort of stack in that it is used by a generic calculation process to store "temporary" intermediate calculations of complex "derived fields" (whose values are eventually stored elsewhere). Subsequently it experiences a lot of insert and delete activity against it; however, because of the nature of the data being stored in it (i.e. incomplete calculations), there's a fair amount of overhead (transactions, redo logging) which serves no real purpose (in the event of a server error this data is of no use; rather the calculation process itself would be restarted).

If there are others out there who have encountered this situation and have advice on the best way to "tune" such a table, I'd love to hear it. (Ideally, there would be a CREATE TABLE option for turning off logging or something similar; kind of like the UNRECOVERABLE option.)

Any suggestions are appreciated.
TIA,
Gerard

---

Gerard M. Averill, Associate Researcher
CHSRA, University of Wisconsin - Madison GAverill_at_chsra.wisc.edu Received on Wed Dec 03 1997 - 00:00:00 CST