Re: How to store 50 Terabytes per day?

I would think that the database would be reasonable in size as the images could
be stored as .img for example and then referenced as external inside Oracle.
Isn't that the basic concept used for the map imaging today? There would be
no problem adding disk drives to accomidate the needed capacity. Wasn't it a few weeks ago that we heard about a 1TB disk for $1200? Ron

>>> <tim_at_sagelogix.com> 09/08/2004 12:40:24 PM >>>
A couple things are certain:

• ETL would have to consist of inserts only once, no updates or deletes EVER. This goes back to the design of the data model and the proper understanding of time-variant data. It's not hard, but so many people with experience in the OLTP world can only think in terms of current-image data.
• Current-image data would have to be implemented as either views or materialized views, if desired...
• Along with the principle of insert only, partitioning by RANGE on a time column will be crucial, with subpartitioning on a frequently-queried other column being an important option to consider. However, due to the volume of data, one might well consider hourly partitions, which would consume almost the limit of 65,535 partitions by itself if data retention is 7 years or so, making subpartitioning not feasible...

Boy, would I love to get my hands on that database! :-)

-Tim

--
To unsubscribe -
mailto:oracle-l-request_at_freelists.org&subject=unsubscribe 
To search the archives - http://www.freelists.org/archives/oracle-l/
--
To unsubscribe - mailto:oracle-l-request_at_freelists.org&subject=unsubscribe 
To search the archives - http://www.freelists.org/archives/oracle-l/