Database Reference
In-Depth Information
table (either partially or totally), and programming code that refers to the table.
You must be sure to list every effect.
Add this document to the documentation you compiled for the database. Even if you re-
verse the changes later, this record could prevent you from yielding to a future impulse to
attempt the same types of changes.
Summary
The chapter opened by examining the two circumstances under which you might feel com-
pelled to depart from proper database design techniques. You learned that breaking the
rulesisacceptable
if
youaredesigningananalyticaldatabase;otherwise,youshoulddesign
the database properly first and then make deliberate decisions to break or bend specific
rules. You then learned that the most common reason for departing from proper design
techniquesistoimproveprocessingperformance.Althoughthis
is not
asatisfactoryreason
for breaking the rules, there are times when circumstances dictate that you must consider
such changes.
We then continued with a discussion of the alternate measures you can take to improve
processing performance, such as enhancing or upgrading the hardware and reviewing the
implementationofthedatabase.Youlearnedthatyoushoulddoallyoucantoimproveper-
formance first and depart from proper design techniques only as a last resort. The chapter
then closed with a list of items you should record if you need to break the rules.