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: Opinion on table structure and accessibility

Re: Opinion on table structure and accessibility

From: sybrandb <sybrandb_at_gmail.com>
Date: 16 Mar 2007 08:11:37 -0700
Message-ID: <1174057897.042455.151660@o5g2000hsb.googlegroups.com>


On Mar 16, 3:45 pm, "gl" <stin..._at_pd.jaring.my> wrote:
> Hey guys, need expect opinion on table design and access. For a loan
> record which going to store 300 months of principal outstanding and
> interest outstanding. Which is a better choice?
>
> 1) Create a table with data structure as
> loan_no, month_no, prin_os, int_os
>
> 2) create a table with
> loan_no, p_mth1, p_mth2, p_mth3 ... p_mth300.
>
> The first method will have million of records which cause I/O
> contention, the second method will have issue on selecting data
> randomly. Is there any other way for this design? Thank you.

Solution 2 is horrible, because denormalized. Also 'million of records' does not necessarily cause I/O contention when there is proper physical database design.
If you are really concerned about the number of records, implement the repeating group as a nested table.

--
Sybrand Bakker
Senior Oracle DBA
Received on Fri Mar 16 2007 - 10:11:37 CDT

Original text of this message

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