Re: Reducing REDO log churing

Graeme,

Thanks, I was looking at some old documentation. But, what of the index? I have one primary key constraint index, two unique constraint index, and two foreign key index; should all five have the NOLOGGING parameter? Or does it matter since the table is NOLOGGING (I would think the index would log in the redo log even if the data is not)?

Graeme Farmer wrote:

> Gregory,
> You shouldn't need to put the table in a separate tablespace. NOLOGGING
> 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>
>
> If you are using Oracle 7.x.x you can use (this also works in ORACLE8 for
> 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.

--
Regards,
Greg Lechkun
gpl :-)

DTE Energy====================================================================
DTE     ////// ////////////       Gregory Lechkun - EM&D/PDO-PT
DTE    //   //  //   //           Power Application Software Engineer
DTE   //   //  //   ////          lechkung_at_detroitedison.com
DTE  //   //  //   //             g.p.lechkun_at_ieee.org (personal)
DTE //////   //   //////          (313)235-9445 Office   (313)940-3306 Pgr.
                                  (313)235-8597 FAX