Database Reference
In-Depth Information
A Final Thought
Through years of teaching database design and instructing people in how to use various
RDBMS software programs, I've observed an interesting phenomenon: People who are fa-
miliar with the fundamental principles of proper database design have a better comprehen-
sion of their RDBMS and the tools it provides than those who know little at all about data-
base design. I believe this is due to the fact that the people who know database design are
able to understand
why
the RDBMS provides certain tools and
how
they can (and should)
use them. For this reason—as well as the many others presented in this topic—it is to your
distinct advantage to learn and understand good database design techniques. This topic
does not map the only road, but it is, I believe, the straightest, surest, and most easily
traveled.
Summary
This chapter contrasted relational database design with weaker, less effective design
formats. First, we looked at flat-file design. You learned that there are numerous fatal
problems with this approach and that it should be completely avoided. We then examined
spreadsheet design and you saw how constrained this approach can be. The chapter closed
with a discussion of designing a database using RDBMS software. You learned that this
type of design is perilously dependent on your familiarity and skill level with the software.
Unlike a good database design method, designing a database around an RDBMS does not
provide you with principles and a rationale for designing a proper database structure. Su-
perficially, in the short run, the software product looks as good—it just doesn't work as
well in the long run as the design method discussed in this topic.
