> > MaxDB has a complete different data storage approach as e. > g. Oracle or DB2. > > There are not tablespaces, datafiles, extents, and > controlfiles. MaxDB > > uses Volumes and spreads the data accross those volumes. > You have no > > influence where a table is stored so you will never run > into "hotspots". > > But it also means that you have no chance to optimize it if > the usage pattern is bad; and unfortunately there is no way > to change the size of a volume (is there?). I personally > found SQL Server to be the most hassle free RDBMS I have > worked with. I'm sorry to say that on this list but also YMMV...
What do you mean with "usage pattern"? Usually (in 99 % of the cases) this is not necessary since the I/O is spread always across all volumes. A (parallel) access to read from N volumes is much faster than a single read on a single disk. How often do you need to move tables from one tablespace to another - in real life? Greetz, SIEGENIA-AUBI KG Informationswesen i.A. Markus Döhr SAP-CC/BC, SAPDB-DBA Tel.: +49 6503 917-152 Fax: +49 6503 917-7152 E-Mail: [EMAIL PROTECTED] Internet: http://www.siegenia-aubi.com -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
