Re: Loader

Direct path loads are safe.
When loading into your production table, the load will complete and leave your primary key index on the production table in DIRECT LOAD state if any of the composite keys conflict with pk's in the production table. You would need to rebuild the primary key index.
(do ya gotta use the [slow] COMPOSITE keys?)

What about loading it into a temporary table, do any needed cleansing and primary key checking, then append to your production table?

(direct sql load is way cool, you can't get me to stop using it)

Connor McDonald <connor_mcdonald_at_yahoo.com> wrote in message news:380AF0CC.63B2_at_yahoo.com...
> savula_at_my-deja.com wrote:
> >
> > I want to load sets of 20,000 records each from 4000 different flat
> > files into a table. I know conventional SQl load takes lot of time,
> > Also, I am told it is not safe to use Direct SQL Load to production
> > tables.
> >
> > So, could you please tell me what is the best way to get the data into
> > the tables.
> >
> > The table has a composite primary key which should be enforced when I
> > load.
> >
> > One way i tried was to load into a temporary table and then use:
> >
> > Insert into production_table select * from temp_table.
> >
> > Is this the best method or is there a faster approach.
> >
> > I want it to be as fast as possible.
> >
> > Pl reply to sudha_kar_at_hotmail.com
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
> Who told you direct load was unsafe...? Thats nonsense.
>
> One was of speeding things up may be to:
>
> - sort the data using the OS - this lets you check the primary key
> uniqueness at this stage as well
> - load the data with the direct / sorted indexes option
>
>
> alternatively drop the indexes and rebuild afterwards...
>
>
> --
> ===========================================
> Connor McDonald
> "These views mine, no-one elses etc etc"
> connor_mcdonald_at_yahoo.com
>
> "Some days you're the pigeon, and some days you're the statue."
Received on Thu Oct 21 1999 - 18:50:15 CDT