Re: Reducing REDO log churing
From: Graeme Farmer <g_farmer_at_halas.com.au>
Date: Mon, 14 Feb 2000 15:11:19 +1100
Message-ID: <L8Lp4.12834$VJ1.24388_at_newsfeeds.bigpond.com>
Date: Mon, 14 Feb 2000 15:11:19 +1100
Message-ID: <L8Lp4.12834$VJ1.24388_at_newsfeeds.bigpond.com>
Gregory,
[Quoted] [Quoted] You shouldn't need to put the table in a separate tablespace. NOLOGGING [Quoted] in Oracle 8 can be enabled at the table level. alter table <table_name> nologging;
If you are dropping and recreating the table from another table then you can use:
create table <new_table>
nologging
as select * from <old_table>
[Quoted] If you are using Oracle 7.x.x you can use (this also works in ORACLE8 for [Quoted] backwards compatability)
create table <new_table>
unrecoverable
as select * from <old_table>
This will greatly increase the performance of your data copy and reduce the hits on your redo logs.
Graeme. Received on Mon Feb 14 2000 - 05:11:19 CET