Re: Bypass generating redo and/or rollback information?

oratune, Is it still true, if table was created with logging and altered with nologging later on.
thnx ted chyn
In article <8lsos3$1er$1_at_nnrp1.deja.com>,   oratune_at_aol.com wrote:
> In article <8lscej$n3l$1_at_nnrp1.deja.com>,
> ryanedley_at_my-deja.com wrote:
> > Hello, I was wondering if anyone knows of a way
> > to bypass redo logging and generating rollback
> > for regular insert and update statements.
> >
> > I know the NOLOGGING clause can be used for
> > CREATE statements, but I would like to do this
> > for DML statements.
> >
> > Thanks,
> > Ryan
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
> >
>
> If the table being inserted into, updated or deleted from was created
> NOLOGGING then all transactions against that table will not be written
> to the redo logs. This does not eliminate rollback generation, which
 is
> providing a different functionality, but it will reduce time for the
> DML since no redo log information is being written for the
 transaction.
> This only applies to tables created NOLOGGING.
>
> --
> David Fitzjarrell
> Oracle Certified DBA
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Mon Jul 31 2000 - 00:00:00 CDT