I would have to agree with both of you, but I do want to share this:
The only time that I have witnessed a DB that was not completely normalized
was when there were over 150-200 tables/views in a database and they were
trying to maximize the application's efficiency. The field lookup would have
required a series of complex joins on several tables. Due to record locking
etc, the speed of the application itself would have been affected if the data
(member demographics for example) was not contained in more than one place.


jmonty


"Dave F" wrote:

I tend to agree with you.

"jahoobob via AccessMonster.com" wrote:

Read this to help you decide.
http://www.formeremortals.com/Downlo...malization.pdf
Access' Analyze table will do what the article steps you through.
That it is not being queried daily, to me, is not a good argument against
nornalizing.


Dave F wrote:
Is there ever a justification for NOT normalizing a db?

A consultant and I are in a debate right now. We have an Access db which
essentially acts as a data repository, from which data are reported upon once
a month in Excel.

My take: the db should be normalized.

His take: the db doesn't need to be normalized because it is not being
queried daily.

Thoughts?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/200608/1