Re: Left AS/400 and Returned

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

> The reason shops don't normalize is more likely because it's 
> difficult to master and there is little perceived benefit.


I don't know why people perceive normalization as difficult to 
master-- IMHO, it's a 'simple' process if you have the kind of mind 
that can think like a computer, and can 'see' redundancy in a 
database 'through inspection.'

The biggest trap that a programmer / database designer can fall into 
is including a table of any sort in a database.  Once you realize 
that that's the first sign of a bad design, the rest is 'easy!'

The rules of 1st, 2nd, and 3rd normal form as usually expressed are 
not always clear, but it's well worth learning their 'hidden meaning!'

One of the rules of normalization is that all databases must be in at 
least 3rd normal form at some point in the design process.  Only 
after that point can you even consider "demoralizing" the database. 
The kinds of things that might (so shoot me now) be considered for 
denormalizing is a database containing the names of the months of the 
year, or the days of the week-- things that "couldn't possibly change 
or need more entries!"

Of course, there are those accounting systems that run 13 months per 
year instead of 12...   (:

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx