I would drop the primary key and recreate it after the load. If the data is
sorted in primary key order, then you can use the NOSORT option when
building the index.
Another option might be to disable the primary key constraint. After the
load, enable it again. This gives you nice control for dealing with
duplicate keys.
--
Terry Dykstra
Canadian Forest Oil Ltd.
Check out Sybase Developer's Network: http://www.sybase.com/sdn
<drona_rom_at_my-deja.com> wrote in message news:85iklr$fm1$1_at_nnrp1.deja.com...
> Hello,
> Can someone give me ideas on different method of loading large amount of
> data to a table inOracle database. My company prefers loading directly
> from memory instead of writing to file and then use SQL*Loader. The
> entire data has to be loaded to single table. I have created table such
> that data will not span more than 3 extents. During loading time only
> primary key (id) will be on. This key is generated by sequence
> generator. Currently we use Roguwave interface, which is very slow since
> it does not re-use bind variables.
> Any suggestion will be of great help.
> Thanks
> Drona
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Thu Jan 13 2000 - 10:48:31 CST
