On Mar 16, 11:11 am, "sybrandb" <sybra..._at_gmail.com> wrote:
> 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
Another option, should size and contention be worrisome, is to look
into partitioning the table.
Received on Fri Mar 16 2007 - 10:22:53 CDT
