Re: How Large is a BIG Relational DB
Date: Tue, 8 Mar 1994 15:41:22 GMT
Message-ID: <KGOR.94Mar8094123_at_malibu.aadt.com>
>>>>> "Adam" == Adam Green <adamg_at_informix.com> writes: In article <adamg.763048040_at_infmx> adamg_at_informix.com (Adam Green) writes:
>> ddargo_at_us.oracle.com (Dave Dargo) writes:
>>> aevans_at_kaiwan.com (Alan B. Evans) writes:
>>>> (SVR4) using Oracle 7. Oracle 7 has a design limitation in that 1 >>>> instance of Oracle can only handle 256 GB of data.
>>> Most definately not correct. More like a design limitation of >>> around 4 Terrabytes. There are production databases in Oracle >>> larger than the 256 GB you mention (including one on a Sun box).
>>> Dave (ddargo_at_us.oracle.com)
>> Hi Dave, I kinda figured on someone questioning the old 256 gig
>> limitation - I guess you're right; only, Alan was more likely
>> talking from experience, no so much on what brand O can address,
>> but what the nag can actually handle. Care for a benchtest?
>> Still, pretty soon 4 Tbs will be small and the number of installed
>> nCUBE 'video jukeboxes' doing mainframe corporate DBMS replacement
>> is still pretty thin on the ground.
I am not sure when Sybase/Ingres/?? will have similar functionality.
I am working on a large (300GB - 2TB) combined DSS/OLTP application. I would like to have an alternative to using TeraData (NCR 3600), but have found no other database that will use multiple cpu's well in handling large (10 - 100 million row) insert/update/delete statements.
Any Comments, helpful hints, corrections are welcome.
-- Kent S. Gordon, American Airlines Decision Technologies email: kgor_at_aadt.com / All opinions are my own. Telephone:(817)931-2286 (day)/(817)431-8775 (night)/(817)963-2692 (fax) Postal: 76 Corral Drive North, Keller, TX 76248Received on Tue Mar 08 1994 - 16:41:22 CET