Re: Design Question

From: Robert Freeman <>
Date: Fri, 16 Oct 2009 14:26:32 -0700 (PDT)
Message-ID: <>

AMEN to that!! Especially when you have to deal with translations!!

 Robert G. Freeman
Oracle ACE
Ask me about on-site Oracle Training! RMAN, DBA, Tuning, you name it! Author:
Oracle Database 11g RMAN Backup and Recovery (Oracle Press) - ON IT'S WAY SOON! OCP: Oracle Database 11g Administrator Certified Professional Study Guide (Sybex) Oracle Database 11g New Features (Oracle Press) Oracle Database 10g New Features (Oracle Press) Other various titles

  • Original Message ---- From: D'Hooge Freek <> To: "" <>; "" <> Sent: Fri, October 16, 2009 1:05:13 PM Subject: RE: Design Question

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.


Freek D'Hooge
Oracle Database Administrator
tel. +32 (0)3 451 23 82

From: [] On Behalf Of Balakrishnan, Muru [] Sent: 16 October 2009 18:58
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.


M vs Male
F vs Female

Card type

C vs Credit Card
D vs Debit Card,
P vs Prepaid Card

Thanks in advance,
-- Received on Fri Oct 16 2009 - 16:26:32 CDT

Original text of this message