Dennis, Thanks for the thoughts, the historical snapshot, and for
paying attention to the question. I am on the DW list now, and
will newby-ize them straight away.
- Ross
-Original Message-
Sent: Friday, December 07, 2001 11:16 AM
To: Multiple recipients of list ORACLE-L
Ross - Sti
I've been bodging my way though setting up a database to hold summary info
for 11 million assets with various look-up tables around it, the whole to be
refreshed weekly. Its not that big - around 15Gb, it doesn't have a
timestamp as the partition key and it does not contain transaction info, but
On Friday 07 December 2001 20:35, Robert Chin wrote:
> >> My short take on this is that a datawarehouse is a OLTP database..
>
> What ??? I think you should keep that "short take" to yourself for the
> benefit of those who are seeking to learn/understand about DWH.
> It's not uncommon to find
>> My short take on this is that a datawarehouse is a OLTP database..
What ??? I think you should keep that "short take" to yourself for the benefit
of those who are seeking to learn/understand about DWH.
It's not uncommon to find OLTP databases with de-normalized data, and they are
certainly
I don't think that size has much to do with it. You can have lots of data
but if it's all in a few tables then it doesn't qualify as a datawarehouse
(IMHO).
My short take on this is that a datawarehouse is a OLTP database with
de-normalized data that supports a DSS application.
--
Please see t
Ross - Still hung up on size hmmm.
How about this for a definition. A data warehouse encompasses data
for the entire organization. A data mart services data for a portion of the
organization.
The history of this subject is relevant. In the 80's there were
Executive Information Sy
I, like many others, have a problem with the "size is everything"
definition. I worked with a 2 TB DSS system six years ago that wasn't
a real "data warehouse". And I've seen a true datawarehouse fledgling
that was under 200 GB (with lots of free space).
However, even making the nonsense assump
Jared,
Thanks. I have the main RK book. Like it. Understand what
little i have read of it. I am just interested in what
folks thought about "size vs. DW definition" was.
I *do* think, tho, that "size does matter".
I don't consider my shared E: drive a datawarehouse
because it can support a
Ross,
A DW is defined by purpose and design, not by size.
A collection of Data Marts, ( tables for star joins ) is not
a DW either. DW's are used to create data marts.
If you don't already have the database books from
Kimball, I suggest you acquire them.
Data Warehouse Toolkit
http://www.am
Barbara... have you been talking to men again...?
As I was instructed by the Oracle Data Warhouse class instructor last
year... it isn't the amount of data, but what it's purpose is... what you
do with it.
He was a neat teacher... Harley and all.
April
-Original Message-
To: Multipl
Ross
Size doesn't matter.
No, really.
Who's imposing the "amount of data" constraint??
Push Dodge and Gorman's "Oracle8 Data Warehousing" book toward your
damagement, and somehow trick them into reading the first chapter. They
quote Inmon (of course) -- a data warehouse is a "subject oriented,
in
11 matches
Mail list logo
