Re: Indexed PF vs. LF performance

In my case, I would make that architecture decision based on 

requirements.

Same here. I've been using more sequential, numeric identity keys lately, but Rob had a good point about the State Code table. The state code is a lot more descriptive than a numeric identifier, and easier to remember for data entry, and very unlikely to change.

Consistency is a consideration but not an overriding
one.

I agree.

The trick is deciding when they are appropriate, and that
can be different for different circumstances.

One question I ask myself is whether there might be any cause to allow users to change an otherwise descriptive key field in a maintenance program. Maybe it's a data warehouse used for reporting where rules of normalization may not strictly apply. If so, then use an identity key rather than a descriptive one.

-Nathan.