Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: one big tables vs. many smaller
On Fri, 5 Apr 2002 11:31:09 +0200, "Steffen Ramlow" <s.ramlow_at_gmx.de> wrote:
>"koert54" <koert54_at_nospam.com> wrote in message
>news:Rh3r8.52068$DE4.6492_at_afrodite.telenet-ops.be...
>> You might want to read up on clustered tables and see if this will work
>for
>> you ...
>> This way you'll have logically multiple tables that are physically stored
>in
>> the same datablocks...
>
>hm, hm...
>
>is this faster than placing the tables on different disks to that they can
>read in parallel?
>
>
Depending on the queries, it quite possible that they wouldn't be read in
parallel anyway. If Oracle has to read the parent table in order to get the
values on which to search the child table, then it can hardly be expected to run
a parallel process to get both at the same time. In the mean time, with
clustering, you already have a lot of what you need in the buffer and so avoid
the additional physical i/o.
Received on Fri Apr 05 2002 - 10:01:15 CST