Re: NOLOGGING Option on Create Table

I'll throw my hat into the ring on this one. About six or seven years ago I was at Boeing and lobbied Oracle heavily to do something for data warehouse applications. I was running Oracle 7.3.x on Amdahl mainframes and had to truncate every table on Friday night and have hundreds of gigabytes of data loaded on an all-or-nothing basis by Monday morning. That anything might slow it down or cause a failure ... be it rollback or logging, or whatever was a constant source of pain.

I'd have gladly suffered the slings and arrows of unhappy management once or twice a year when hardware failed rather than the weekly grind of being stoned because the data load wasn't completed on time.

What would be nice ... would be a feature in PL/SQL that duplicates the functionality of DIRECT LOAD in SQL*Loader. Something like a BULK COLLECT followed by writing blocks directly bypassing the SQL engine.

How about it Tom?

Daniel Morgan

Marc Blum wrote:

> On 6 Apr 2002 11:17:49 -0800, Thomas Kyte <tkyte_at_oracle.com> wrote:
>
> >I see people say things like "and *I* will never need to recover them". That is
> >wrong. You will need to recover that many times in your lifecycle.
> >
>
> Hi Tom,
>
> I would be interested in your opinion concerning data warehousing /
> DSS / Analytic Databases which are used for querying only and say
> completely rebuild each night. I that case I tend to avoid archiving,
> logging etc. If the database crashes, well, users will be unhappy for
> not being able to work on it today, but 'til tomorrow it's fixed and
> NO data is lost.
>
> regards
> Marc Blum
> mailto:marc_at_marcblum.de
> http://www.marcblum.de
Received on Mon Apr 08 2002 - 11:04:32 CDT