All the others plus:

I use a generic lookup cache that is used clientside (it reduces joins and
therefore speeds reports etc.). It works well because it is generic and
thus relies on a standard PK symantic, i.e. integer PK's. It also makes
relationship walkers easier to write / maintain.

Therefore my vote goes for Integers.

JAC

""Rob Schuff"" <rob@...> wrote in message
news:002f01c2341b$3ee854d0$0200a8c0@picard...

> greetings folks,
>
> we are having a spirited discussion at a work about lookup table and

whether

> or not they should have a surrogate primary (integer) or whether its

better

> to just use the lookup value (or an uppercase'd copy of it) as the primary
> key. I personally have been on both sides of the fence before (normalize

to

> the max or be somewhat pragmatic). Anybody care to share their opinions?
>
> rob
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>