Hello Leig, with SAP DB / MySQL MaxDB there is no such thing like partitioned tables/indices/... . Anyway, this does not mean that huge tables have a degraded performance because
- there are not the table restrictions regarding backup as they are known for O., and being the reason to use partitons for higher availability - Parallelism for physical data access can be achieved by using more than 1 data volume, on different physical disks, the data is spread automatically between the data volumes (the data of a table does not reside only in one data volume). So, device contention can be reduced without bothering the definition of individual tables. So if you just wanted to create partitions to put the partitions into several 'tablespaces', just define more data volumes, and let SAP DB decide automatically, only if you have special queries that will operate on individual partitions it may be an issue. Regards Alexander SchrÃder SAP DB, SAP Labs Berlin > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, December 08, 2003 10:43 AM > To: [EMAIL PROTECTED] > Subject: sapdb with huge tables > > > Hi, My frend: > > My boss is interestred in SAPDB. But I don't know how to > optimize huge tables in SAPDB. With ORACLE database we can > use PARTITION TABLE to devide huge tables into small pieces. > What can I do with SAPDB? > I need your help. > Thanks > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
