ntareen_at_yahoo.com (Nisar Tareen) wrote in message news:<6134f1ca.0410131241.2d3cc4cc_at_posting.google.com>...
> I will do the due diligent that the I/O verses the storage space. In
> some cases even a redundancy may help me in the overall performance.
>
> Yes, if you ask academic, his answer will be Normalize it to maximum
> but working daily in the pits with Developers I know and feel your
> concern, I will go and add the name in the table instead of making an
> i/o. but check the overall impact on the application, How it will be
> added /update in the file.
>
> Do the due diligent.
It is not merely "academic" to normalise, it is "practical" too.
Denormalised designs require more complicated code to keep the
redundant data in sync with reality, and are prone to errors. In my
experience, when someone makes a denormalisation like this in an OLTP
database, 9 times out of 10 they do it without any real justification
other than "well, I think it will help performance". They should
concentrate on sorting out the real performance issues, not
denormalising based on knee-jerk "practicality". In 14 years or so I
have never (and I do mean NEVER) come across a case where a
denormalisation of this kind was really justified. The trouble is,
everyone knows how to denormalise; real performance tuning takes more
skill.
Received on Thu Oct 14 2004 - 06:17:55 CDT
