-- Gurelei [EMAIL PROTECTED] on 05/10/02 10:43:23 -0800
Hi.
We are designing a small database using a data
warehousing desing. We have created a 3rd normal form
and are now debating whether and how to denormalize
it. I see the pluses of denormalization - easier
queries creation and
Jared,
Thanks for the answer. I must admit my ignorance in
terminology as for me data warehouse and data mart a
pretty much the same thing except for size. I
understand that data mart is smaller. The database I'm
referring to could probably be described as data mart
as it is going to be rather
One philosophy of DW states that you build a DW that is
fairly normalized, much like an OLTP database, albeit one
with a temporal component and complete logging of transactions
within the data.
This is then used as a warehouse. The data from the DW is used
to assemble data marts. These data
-- Gurelei [EMAIL PROTECTED] on 05/10/02 12:13:27 -0800
Jared,
Thanks for the answer. I must admit my ignorance in
terminology as for me data warehouse and data mart a
pretty much the same thing except for size. I
understand that data mart is smaller. The database I'm
referring to
The distinction between a data mart and a data warehouse is not size (Size
doesn't matter). It just works out that way usually...
The distinction between a DM and a DW is its function within the entire
decision-support strategy. A data warehouse is the consolidation point for
all data from all
A DW stores data in a denormalised fashion, that's one
point that every body knows but it is also subject
oriented. It is also developped one subject at a time.
A DW is multi-subjects as a datamart is on one
subject.
From Bill Inmon
From the data warehouse data flows to various
departments
:
Subject:Re: data warehousing desing - to denormalize or not to
denormalize - that
The distinction between a data mart and a data warehouse is not size
(Size
doesn't matter). It just works out that way usually...
The distinction between a DM and a DW is its function within the entire
