Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Advantages of loading sorted data into large oracle tables

Re: Advantages of loading sorted data into large oracle tables

From: Niall Litchfield <niall.litchfield_at_dial.pipex.com>
Date: Mon, 10 Jun 2002 22:19:22 +0100
Message-ID: <3d0517d8$0$233$cc9e4d1f@news.dial.pipex.com>


"Daniel Morgan" <damorgan_at_exesolutions.com> wrote in message news:3D0356E8.8F5D4957_at_exesolutions.com...
>
>
> Amit Ghosh wrote:
>
> > It is generally recommended that data be sorted on the primary key
before
> > loading into large tables ( partitions). At a minimum the advantage of
this
> > would be the ability to create indexes fast ( using the nosort option).
> > Since external sort programs such as syncsort are considerable more
> > effiecient than the sorting algorithms used by Oracle this would lead to
a
> > more efficient load process.
> >
>
> I keep hearing this about syncsort and it leads me to ask a question that
has
> been on my mind for awhile.
>
> Is this true? And if so, why doesn't Oracle just incorporate the syncsort
> algorithms into the engine?

It wouldn't need to - it could do what it did with intermedia and create an extensible index type.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
Received on Mon Jun 10 2002 - 16:19:22 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US