[AccessD] On DB Bloat, Bad DB Design, and various

I have never yet seen a case where denormalization is correct, except in
OLAP apps, which are fundamentally different that OLTP apps. I have been
overruled by higher-ups on this point several times, and never once been
convinced of their correctness. Show me a case in an OLTP app where
denormalization is correct, and demonstrate why it is correct as opposed
to the "logically correct" model.

Arthur

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
(AccessD)
Sent: Monday, May 24, 2004 3:24 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] On DB Bloat, Bad DB Design, and various

When a database has been completely normalized then to improve the
performance, the DB has to be 'carefully' de-normalized. This is where
the art comes in, like tuning a guitar.

There are many photographers out there who claim to be professional. It
is not enough to simply know all the rules of composition, design and
colour. There is an indefinable property that makes a photographer a
master of their craft. Their ability to interpret what they see and
produce can is not fully qualified; if it could be we would all be
Masters.

The same is true with programming and database design.

IMHO
Jim