Thanks for the advice. I will point out that I am
a complete novice to Oracle.
I have no idea how to setup a partition view.
I am in the learning process at the mo....
Mostly experimenting. Could you explain
why it's better to have smaller partitioned objects
rather than large ones?
I will point out that space is not a problem
but speed would be nice.
Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote in message
news:942263870.4994.1.nnrp-04.9e984b29_at_news.demon.co.uk...
> Rough estimate-
>
> (size of typical index entry + 10) x 2 x number of index entries
>
> Which for a fully used 40 byte index
> and 43 M rows is about 4.5 Gb.
>
> Have you considered partition views,
> allowing you to load (say) 20 tables,
> and maintaing objects of only 5%
> of the size ?
>
> --
>
> Jonathan Lewis
> Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
>
> Dave wrote in message <80btqk$anu$1_at_lure.pipex.net>...
> >I have a table setup in Oracle 7.3.3 on Sun.
> >The table will have about 43,000,000 recs in
> >it within the next few days. I am going to build
> >an index on some fields, ranging from 7 chars
> >to 40 chars. How much temp table space will
> >Oracle require to do this sort of thing?
> >
> >Would it have been better to create the index
> >before using SQL Loader to load the data?
> >
> >
> >Any help please
> >Dave
> >
> >
> >
>
>
Received on Wed Nov 10 1999 - 14:39:31 CST
