Re: sqlload performance

In article <3g3boo$25q_at_ixnews1.ix.netcom.com>, chuckh_at_ix.netcom.com says...
>
>I want to load and index a database on a monthly basis. There is no
>referential integrity or constraint checking. The data will be valid.
>It's being passed to an Oracle data warehouse via sequential files and
>the data has already been validated.
>
>My question is what's the fastest way to load it? I'm planning to use
>sqlload's direct path, but would it be faster to truncate the tables
>every month and reload, allowing sqlload to build the indices as it
>goes? Or would it be faster to drop the indices entirely, load the
>tables, then re-create the indices with sqlplus?
>
> Chuck

It's generally always faster to drop the indexes and rebuild. If you can bring your database up and down at the same time, set the sort area size to something large before building the index.

Yes- the direct load path is fast - we ran a little competion on some oracle for nt when it was beta beat sqlserver by a mile on a 80000 record load with lots of columns and indexes. Neither system was well tuned and I'm not making benchmark claims. It's also fast on our Dec AXP boxes.

-- 
Bob King - rking_at_dfw.net
business ph. - (817) 551-8223