Avoiding redo log for temporary data
From: Chris White <cwhite_at_ic.net>
Date: 1996/08/30
Message-ID: <32272AA2.4EA1_at_ic.net>#1/1
Date: 1996/08/30
Message-ID: <32272AA2.4EA1_at_ic.net>#1/1
Does anyone know if I can avoid populating the redo log for specific transactions? I have a transaction that creates a large amounts of temporary rows then deletes them. This is filling up the redo/archive logs at an alarming rate. Is there the concept of a temporary table (like Sybase)? Or is there a session variable I could toggle? Received on Fri Aug 30 1996 - 00:00:00 CEST