SIGIA-L Mail Archives: Re: SIGIA-L: Architectecting of Databases
Re: SIGIA-L: Architectecting of Databases
From: David Adams (dpadams_at_island-data.com)
Date: Thu Feb 08 2001 - 02:13:42 EST
> On a similar note, a few years ago I got so frustrated with one DBA I was
> working with, who wanted to plunge right in without a moments planning,
> that I spent a day at the bookstore reading books until I found one ...
> which I brought home and told him that if he didn't read and digest that
> book at least, I wouldn't do the project with him ... i think it was called
> "Relational Database Design for Mere Mortals" or some such thing. After a
> few hours reading it, it seemed to be the best blend of relational db
> theory and information design I could find. He never did read it though,
> and I spent the next year chasing around behind him trying to manipulate
> table structures to suit the nefarious plans I had for the project... and
> when we broke up, I really regretted not snagging it from him ;o)
The book is called "Database Design for Mere Mortals" and is by Michael J.
Hernandez. It is inexpensive ($27 US list) and easy to understand. I
_highly_ recommend this book to people who want to understand and
participate in database design. It requires no background in databases or
database theory. This is very good since database books are, almost without
exception, incomprehensible.
I have only two real criticisms of the book:
* Hernandez does not relate his principles and practices back to the
terminology used in all other database books. This is frustrating if you
know database theory or would like to go on from Hernandez to learn more.
* Hernandez says to never save calculated data. There isn't a databse in the
world without calculated data for one reason or another. It just isn't
practical (even the originators of database theory say this.) Perhaps
Hernandez overstates the case since storing calculations is one of the
handful of easy and painful mistakes people first fall into. A better
principle is "don't store calculated data without long and serious
consideration."
I have several other database book reviews at my site:
http://www.4dcompanion.com/bookreviews/databases.html
Tip: If you have to negotiate with database people, learn some of the
jargon. The rules of normalization are often misused to intimidate or
silence non-database people. Here is a summary of the rules of normalization
in plain language:
A place for everything and everything in its place.
-- Grandma
If you want to read a (too-long-for-the-screen) explanation of
normalization, I have an article up at my site that can help:
Normalization Is a Nice Theory
http://www.4dcompanion.com/downloads/papers/normalization.html
And as a 732K PDF:
http://www.4dcompanion.com/downloads/papers/normalization.pdf
Best,
------------------------------
David Adams
Island Data Management
Kailua, HI 96734
dpadams_at_island-data.com
http://www.island-data.com/
808/263-2905
------------------------------
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:54:31 EST
|
