Re: Normalized Data base

Lina,

I assume you are referring to designing a data warehouse since you are
posting in this group. There are three basic ways of designing the model.

Third Normal Form - This is the Inmon approach and works well data mining
and building down stream data marts. It's draw backs are usually higher
development, hardware, and software costs. It's should be used for large
data warehouses with multiple sources.

Star Schema - A special from of denormalized schema. This is the Kimbal
approach. It good in situations of combining multiple sources and the use
is intended to be more direct user access.

Denormalized - This should be used in data warehouses that really only have
one significant source and the warehouse will be used from more direct
reporting than anything else. It's relatively quick simple and cheap but
has issues with integration.

Whichever approach you choose to take realize that once reports and other
uses are written against it, changing the general approach is expensive.

Just opinions....

"Lina Manjarres" <LinaManjarres@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A3CF8EA4-FAB4-4831-8BBF-4AFBCD41F5C6@xxxxxxxxxxxxxxxx
>I have been arguing with my partner if we shoud or not design a normalized
> data base or denormalized. How, can we know when we should choose one or
> the
> other?
>
> Thanks a lot!


.

Loading