|
Booth, In the way of an overview..., while getting rid of or never creating "membered" files in the first place is the beginning of good relational design, there is more. Usually, you want to do what is called "normalization", at least to 3rd normal form if you are creating tables for most transaction-type applications. (If you're doing data warehouse tables, then you need to "denormalize" your table design using what's known as a "star" or "snowflake".) The reasons why are covered in books and courses on doing relational database design. A good relational DBA, thoroughly trained and experienced in good relational design, would be the person to seek out to do your table designs. He/She should also be able to help with good index, view, referential integrity, store procedure and trigger design where needed. If they have ever been a programmer against relational tables they can also help you with your application design on how to best access your "normalized" relational tables. Its really not all that hard, just work. Let me know if I can help. Take care, Dave
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.