> *our db instance is about 80% full. What would the drawback > be of creating MANY more data volumes, such that the db is > only 30% full? Would this overkill have a detrimental effect, > and if so, how big? The benefit is of course that the > database manager does not have to be so vigilant in terms of > not filling the db.
Same as described. SAPDB will balance _automatically_ between the volumes in low I/O times so after a week or two you will have all volumes balanced loaded, there's no need to reorganize (like in other databases *hint-hint*). If you add ONE additional the same (side-) effects will occur as if you were creating from scratch. 80 % is quite full so you should consider adding another volume. The size of the filled database will maybe impact performance when sorting huge resultsets. > I will find this out by experimenting, but it would be like > walking in the dark.... It has dawned on me that tweaking a > database is no trivial business! Yeah.. tweaking max. performance out of the system is an iterative process, there's never a general solution for everyone and every installtion since this heavily depends on what you're doing on the data. Increasing the CACHE_SIZE to the maximum size your system can handle (in terms of available memory etc.) is generally a good approach for the first tweak. Regards, 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]
