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 assumption, there would have to be a
time factor.  What would have been a VLDB five years ago might be
smallish today.  And a few tomorrows into the future, it might be
"It's only a petabyte, you can't call THAT a data warehouse!".  At
this exact moment, the answer is 42 (x 10 GB).  However, that answer
is now obsolete.

-Don Granaman
[OraSaurus]

----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, December 06, 2001 3:55 PM


> Informal survey: Datawarehousing.
>
> Limiting Assumption:   "A necessary and sufficient condition for
defining
> something
> to be a datawarehouse is the amount of data
> to be stored."
>
> Question/Poll:   Given the above ridiculous constraint, at/above
what size
> can something
> be considered a data warehouse?
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Mohan, Ross
>   INET: [EMAIL PROTECTED]


-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Don Granaman
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to