Re: Most efficient large update?

"Howard J. Rogers" <howardjr_at_www.com> wrote in message news:<3b1398ca_at_news.iprimus.com.au>...

> SQL Loader will respect the nologging attribute. So will a direct load
> insert. So will a 'create index' statement. But 'insert into...' will
> generate redo, regardless.
>
> There is, however, one way to turn off *all* logging, database-wide, and
> that's by using the "_disable_logging" hidden parameter. But as I've posted
> elsewhere tonight, use of that parameter is totally unsupported, and renders
> your entire database vulnerable to non-recoverability in the event of an
> Instance crash.
>

Hmm. Thanks. I'm so used to dealing with direct path loads that I've never had to think about the 'insert into'. And even I won't touch the _disable_logging, since I accept the loss of a tablespace, but not the entire system. Received on Tue May 29 2001 - 15:14:05 CDT