Database Reference
In-Depth Information
Note
A database can be designed by a single individual or a design team composed of
two or more individuals. Throughout the remainder of the topic, I use the phrase
database developer
and the word
developer
to refer to the person or group design-
ing the database.
The Importance of Completing the Design Process
OnethingIwanttomakeperfectlyclearfromtheverybeginningistheimportanceofcom-
pleting the design process. I'm often asked if it's truly necessary to go through the entire
design process. My answer is always a resounding “Yes!” I'm then asked whether it's still
necessary if someone is only going to create a “simple” database. (
Simple
is one of the
most dangerous words known to database developers.
Nothing
is ever “simple.”) Again,
my answer is yes, it's
still
necessary. The type, size, or purpose of the database is totally
irrelevant to the value of undertaking a fully developed design. You should implement and
follow the database design process from beginning to end.
It is a well-known and proven fact that it is a bad idea to attempt to design a database
without employing a thorough database design process. Many database problems are
caused by poor database design, and
partially
following the design process is just about as
badasnotusingitatall.Anincompletedesignisapoordesign.Onlyifyoufollowthrough
with a whole, unabbreviated design process are you assured a sound structure and data in-
tegrity.
Animportantpointtokeepinmindisthatthelevelofstructuralintegrityanddataintegrity
in your database is directly proportional to how thoroughly you follow the design process.
The less time you spend on the design process, the greater the risk you run of encounter-
ingproblemswiththedatabase.Thoroughlyfollowingthedatabasedesignprocessmaynot
eliminate all of the problems you might encounter when designing a database, but it will
greatly help to minimize them. As you work with your RDBMS software, you'll find that
a well-designed database is easier to implement than a poorly designed one.
Databases are not hard to design; it just takes a little time to design them properly. Don't
allow yourself to take shortcuts when it seems as if the design process is taking too
long—just be patient and remember what a wise old sage once said:
There's
never
time to do it right, but there's
always
time to do it over!
