Re: Design Question
- From: Toon Koppelaars <toon@xxxxxxxxxxx>
- To: Muru.Balakrishnan@xxxxxxxxxxxxxxx
- Date: Fri, 16 Oct 2009 19:04:50 +0200
>
> 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.
>
I tend to be on your side here. The less-overall-blocks is the most
important driver here for me.
Done that before, and saved double digit percentages in sizes of table
segments.
On Fri, Oct 16, 2009 at 6:58 PM, Balakrishnan, Muru <
Muru.Balakrishnan@xxxxxxxxxxxxxxx> wrote:
> 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
>
>
>
--
Toon Koppelaars
RuleGen BV
+31-615907269
Toon.Koppelaars@xxxxxxxxxxx
www.RuleGen.com
TheHelsinkiDeclaration.blogspot.com
(co)Author: "Applied Mathematics for Database Professionals"
www.RuleGen.com/pls/apex/f?p=14265:13
Other related posts:
