Stephen Look at the sample here.
> <http://www.datamodel.org/NormalizationRules.html> See how they broke company from member? Two entities. Salutations and Occupations are entities. Lookup is a vague term describing some artificial computing construct, completely different from "Invoice" or "Product". > 3NF Eliminate Columns Not Dependent On Key - If attributes do not > contribute to a description of the key, remove them to a separate table. In the OTLT you'd have LUP_CODE, LUP_DESCRIPTION, LUP_LTPFK Lup_code and lup_description describe the key. Taken together they are the key. Lup_pk would be a surrogate key. Lup_LTPFK does not describe the key. It describes the type of entity. It's only required to support the re-definition of lup_code and lup_description. If it wasn't there the table would be completely normalized to 3NF. In fact, lup_ltpfk is duplicated data! There's nothing wrong with having oodles of tables. There is a performance hit to have more records in a table than required as it takes more space and sends more data over the wire. This means more access of index keys, more chance of dead-locks. Every query in your system might touch that table. The bigger the system the more that table will be accessed. The more that table will want to twist and expand it's structure. Just because something works doesn't make it "correct" or "textbook". I can see you're not going to change your mind, so I'm done. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
