Re: Performance, logging with large daily reporting tables

From: Daniel Roy <danielroy10_at_hotmail.com>
Date: 13 May 2003 13:15:55 -0700
Message-ID: <1b061893.0305131215.7081c6f3_at_posting.google.com>


When you create a new table in Oracle, you can include the NOLOGGING option, which reduces the amount of redo logging generated when DML (and DDL???) operations affect this table. A temporary table can also survive for the transaction or the session, at your choice (look up "ON COMMIT PRESERVE/DELETE ROWS" clause). Maybe that would be OK for you. Especially if you are on 9i, you might want to explore the PL/SQL options (table of records, record of tables, collections, ...), which can often give very good performance.

Daniel

wattsk1_at_midas-kapiti.com (Ken Watts) wrote in message news:<147fb29b.0305130522.44019c33_at_posting.google.com>...
> Hi all,
> Would like to be able to suppress logging on a handfull of tables used
> as extracts to support daily reports. They are cleared before end of
> day and then repopulated, I suppose they are really global
> temporary/transient tables. On DB2 we use the create and alter
> statement clause "ACTIVATE NOT LOGGED INITIALLY" which allows them to
> be deleted without being logged. Could drop and recreate the table
> rather than just deleting the records, but would appreciate advice on
> alternative solutions, and/or which method would be most efficient
> with oracle.
>
> Cheers
> Ken Watts
Received on Tue May 13 2003 - 22:15:55 CEST

Original text of this message