Re: Temp table space?

The best answer is to have a look at the article on partition views on my web-site.

Partition views take a bit of understanding, but can introduce significant performance benefits given the right circumstances.

In your case, though, one of the obvious advantages comes from greater ease of
space management - a reasonable number
of smaller objects is much easier to handle than a couple of very large objects.

For example, if you have to rebuild a 2.5Gb index, that's bad news; but if you can rebuild a 100Mb index today, and another one tomorrow, that's going to have less impact on your normal processing schedule.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Dave wrote in message <80cl9k$565$1_at_lure.pipex.net>...
>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 ?
>>
Received on Wed Nov 10 1999 - 15:57:25 CST