Re: Very Large DB

For what it is worth, we have about 6 databases that size or larger. Two of them are in O8. We are working on migrating the other 4 to O8.

For databases this size, O8, whether true relational or not, is where we want to be. The deciding factors are the fact that you can partition large tables, making access to them easier (partition level indexes) and administration easier (individual partitions can be backed up or recovered- possibly made read only.)

You haven't said whether you are doing OLTP or OLAP. We are basically OLTP and archives. We will be doing OLAP this summer with a combination of the 6. It will be O8.

We do not use the flat file approach.

I would suggest you go Oracle 8.
In article <3519046D.F85_at_rell.NOSPAM.com>,   Doug Barnes <dwb_at_rell.NOSPAM.com> wrote:
>
> Jason D. Weil wrote:
> >
> > I am leading a development effort that will result in a multi-billion
> > row database, on the order of 400GB. About 80% of this database could
> > properly reside in a single partitioned table, each row being fairly
> > small. There is some contention within our organization as to whether to
> > implement this as a completely relational database (using Oracle 8), or
> > to implement the largest table as flat files and use Oracle as a front
> > end for accessing these data. Does anyone have experience with this type
> > of problem? Have you had success with either of these approaches, or is
> > there another, better, candidate?
>
> Sure would hate to do a full table scan on that thing.
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Wed Mar 25 1998 - 00:00:00 CET