[NON-TECH] arguments for supporting maxdb

Hi all;

hope this is not completely OT here (sorry if so; feel free to toast me
PM if you like). Overally, we are using a (proprietary) document
management system and, since maxdb has quite much convinced us to be
robust and reliable, right now thinking about whether to ask the
manufacturer of this dms to support maxdb. Currently they are supporting
Oracle (all platforms) and MSSQL (windows only), and, when we talked to
them on CeBIT, they provided us with quite some "arguments" why it is
not a good idea to use maxdb instead of oracle. Those arguments included
things like

- "maxdb is not a mature product and, while being released to the open
   source community, merely has been 'abandoned' by SAP and is not
   longer actively maintained"

- "though maxdb is actually used with SAP R/3, it's only used for data 
   that aren't considered mission-critical and even this way only in
   small installations while most of the R/3 customers still decide to
   go with Oracle"

- "it doesn't scale up well under heavy load or with huge amounts of
   data"

- "it's unusable in clustered environments" 

...and some others. Though this certain company apparently is in a
partnership with Oracle (which would explain those things to be
pro-Oracle FUD), they're also (looking at their website) in sort of a
partnership with SAP, providing a wide range of R/3 related solutions so
they should know what they are talking about...

To cut things short: Can anyone around here (on- or offlist) give me
some hints on that, as well as some arguments on features that make
maxdb indeed a thing worth considering while thinking about deploying a
new database server?

Thanks in advance and bye,
Kris


-- 
Kristian Rink   -- Programmierung/Systembetreuung
planConnect GmbH * Strehlener Str. 12 - 14 * 01069 Dresden
0176 24472771 * krink@xxxxxxxxxxx

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