RE: Design Question
Date: Fri, 16 Oct 2009 21:05:13 +0200
Message-ID: <4814386347E41145AAE79139EAA398980D2DF284DB_at_ws03-exch07.iconos.be>
I don't know if you work for an international company, but using codes can also be easier when your application must deal with different languages.
regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
e-mail: freek.dhooge_at_uptime.be
tel. +32 (0)3 451 23 82
http://www.uptime.be
disclaimer
From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] On Behalf Of Balakrishnan, Muru [Muru.Balakrishnan_at_dishnetwork.com]
Sent: 16 October 2009 18:58
To: oracle-l_at_freelists.org
Subject: Design Question
Hello Experts,
I request your opinion on, whether column values in large tables with more than million rows should be codified for better performance. For example a customer table could have following columns, gender and card type. In our team many prefer to spell out the entire word for every row (as Male, Female, Credit Card, Debit Card etc), but my recommendation is to codify (M, F, C, D, etc) with a lookup tables when needed. Their argument is, hardware is cheap including storage, helps readability and less joins. My argument is, production hardware is not cheap (we can buy 1TB for home under $100, but production hardware costs thousands), less overall blocks used improves performance, negligible problem with joining lookup tables. Please give your opinion.
Gender
M vs Male
F vs Female
Card type
C vs Credit Card
D vs Debit Card,
P vs Prepaid Card
Thanks in advance,
Muru--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 16 2009 - 14:05:13 CDT