🚀 go-pugleaf

I don't know of any off hand. The general rule we've adhered to is a balance
between usability and normalization. IOW, if you find yourself doing a lot
of JOIN's to resolve data references then it may be time to consider
consolidating some tables. Also, we try to keep our primary keys to a
minimum so as to avoid unnecessarily indexing tables just prior to queries
(simple and complex). For the most part, our primary keys are a single value
(DOUBLE PRECISION or INTEGER) and we feed GEN_ID() to them (starting from
the very bottom end, -2147483648 or something like that, generators default
to 0, but since GEN_ID uses an integer we find this works just fine).


"Christopher Smith" <smitty1each@earthlink.net> wrote in message
news:3ada280f_2@dnews...
> Recent discussions in school have argued against higher levels of
> normalization as being too detrimental to performance.  I've never worked
> much beyond stand-alone applications.  Are there books/case
studies/articles
> that anyone knows of pertaining to performance tradeoffs for normalization
> when doing database design?
> Regards,
> Chris
>
>