Re: Very Large Tables

Am Donnerstag, 27. Januar 2005 21:32 schrieb Robert Schaefer:
> We are in the process of migrating a very large tables ( multi-billion rows
> ) to reside on a MAXDB or some other open-source database. The following
> concerns have been raised:

You really mean multi-billion = >1.000.000.000 = >1.000 millions ? Uuups.

> 1. Is there a way to specify the location of a table or an index on to a
> specific volume or set of volumes ( akin a tablespace)?

No. MaxDB spreads the data (= load) evenly over all configured volumes. Hot 
spots should be avoided automatically. 

Drawback: you can't put "archive" data on slow disks and frequently used data 
on fast disks.

> 2. Are there any performance concerns relating to querying small subsets of
> data from very large tables?

What do you mean? 

3. Does MaxDB volumes need reorganisations?

No. They are not fragmenting.

4. Does SAP use MaxDB for DataWarehouses?

Yes.

5. How is the disk-space consumption of MaxDB compared to others?

You might see a space decrease of about 25% compared to Oracle. 

Nixnutz

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx