it would seem that some form of database views would make this type of
application seem like a table to the end user yet maintain the
normalization of the real data.  is anything like this being considered
in turbo image as we move forward or must we move to allbase for this
concept

-----Original Message-----
From: Steve Cooper [mailto:[log in to unmask]]
Sent: Tuesday, February 02, 1999 11:58 PM
To: [log in to unmask]
Subject: Re: Data Base "Normalization" VS The Real World


Therm-O-Link <[log in to unmask]> wrote:

>Okay, we have Image data bases that we are exposing to the fun world
>of PC, client/server, and ODBC.  We are displaying data for the user
>that may include data from multiple data sets.  Is it better to have
>a "normalized" data base or to have redundant data in multiple data
>sets to make it easier for the C/S application?
>

My personal experience is getting a bit dated, but I repeatedly here
sentiments
that match my data: most people who keep denormalized  or redundant data
in
their databases live to regret it.  It is a common and recurring cause
of
programming errors, and a constant struggle to figure out why the data
is out
of sync and how to fix it.  I have heard, more than once, a database
designer
saying "Never again" to the denormalized question.  I understand the
realities
out there, and it is always tempting, but I thought I would pass on
these words
from folks who have been there, done that.

Steve