Re: The Admin's point of view on DB users best practices

"Ana C. Dent" <anacedent_at_hotmail.com> wrote in message news:<v_qXb.40806$P17.33929_at_fed1read03>...
> Rick Denoire wrote:
> [...snip...]
> > 6) Always do an "insert /*+ APPEND */ " into an empty table, perhaps
> > in nologging mode.
>
> TRADE-OFFS
>
> Do you realize that after NOLOGGING is used, you've just rendered the
> previous hotback useless past this point in time? Since the data
> being inserted is NOT written to the redo logfiles, any recovery of
> this instance can only be made valid to the time of when NOLOGGING
> is used.
>
> Our inhouse Best Practices Manual explicitly states that developer
> should NEVER use NOLOGGING, because we desire to maintain a continous
> recovery DB for failover capability.

I see no problem with having a disposable tablespace that is NOLOGGING for non-critical segments, that would be offline dropped during recovery. Provided that everyone understands that the segments in the tablespace would be trashed, the payoff in terms of reduced generation of redo may be worthwhile, YMMV.

in 9.2 the dba can specify that logging be forced at the tablespace level, which will override the operation being executed as NOLOGGING (unrecoverable).

big differences between whether this is in the developer's own schema, an app-owner schema, etc.

Pd Received on Sat Feb 14 2004 - 15:37:30 CST