Re: Design question : Normalize or Not to normalize ?

From: xtanto <krislioe_at_gmail.com>
Date: 17 Oct 2004 04:01:17 -0700
Message-ID: <e1c9bd55.0410170301.7af8f699@posting.google.com>

Hi,
Thanks for the response.
After normalization, the transaction table only has Emp_Code, while the Emp_Name is stored in the master table. Master table is indexed on Emp_Name and transaction table cannot be. The question is :
If I want to query on Emp_Name on Transaction table, will it scan table ? or can it utilize the Index on Emp_Name on master table ?

Thank you,
xtanto

wizofoz2k_at_yahoo.com.au (Noons) wrote in message news:<73e20c6c.0410140438.2ded77e6_at_posting.google.com>...
> Daniel Morgan <damorgan_at_x.washington.edu> wrote in message news:<1097720911.317026_at_yasure>...
>
> >
> > 3,8 million rows in a properly designed and indexed schema is
> > insignificant. Only denormalize if there is a compelling reason to
> > do so based on actual performance problems.
>
> Absolutely! Nowadays the number of rows is not as much
> a concern as the design. Correct normalization to start
> with is essential. DeNormalize only if needed and
> in small doses!
Received on Sun Oct 17 2004 - 06:01:17 CDT