RE: [NON-TECH] arguments for supporting maxdb

Hi all,

Please have a look at these statements and comment integrated into the original 
question below

Best
Jörg 




History:  SAP AG Teaming Up with MySQL AB
-----------------------------------------

Cooperation agreement (Cross-Licensing) with MySQL AB in 2003.

MySQL is the most popular Open Source DBMS.

Combining the enterprise class MaxDB technology with the community and 
eco-system of MySQL.

SAP DB has been renamed to MaxDB (it has not been sold to MySQL !).

MySQL AB has become SAP Global Technology Partner.


Facts
-----

SAP continues to own MaxDB.

SAP continues to develop MaxDB.

SAP continues to support MaxDB. 

SAP continues to offer MaxDB
*       Database of choice for SAP solutions
*       "Batteries included" component of some SAP products
*       Default component of SAP Netweaver, esp. 'full license' (see pricing 
update Oct 2004)


MySQL has commercial rights to resell MaxDB.

MySQL's dual licensing business model is applied to MaxDB
*       GPL version for Open Source projects, development, trial, demo
*       Commercial license and support by MySQL
*       Commercial license and support by SAP 



What Does this Mean for SAP Customers?
--------------------------------------

Rebranding does not affect existing SAP DB customers

MaxDB is the continuation of the SAP DB code line, that means identical 
behaviour and performance.

MaxDB 7.5 has been released backward up to R/3 3.1I (Extended SAP-Kernel).
 
Replacing  the Open Source versions of SAP DB 7.3 and 7.4 by MaxDB 7.5 has no 
impact on their SAP  maintenance schedule.
  
Pricing for new MaxDB customers in 2004: License is 3% of SAV.

No change for SAP DB users upgrading to MaxDB.
 
No impact for mySAP SCM and liveCache customers.


  
-----Original Message-----
From: Kristian Rink [mailto:krink@xxxxxxxxxxx] 
Sent: Friday, March 18, 2005 2:03 PM
To: maxdb@xxxxxxxxxxxxxxx
Subject: [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"
>>> Nonsense, see above

- "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"
>>> Nonsense, we run large mission critical application landscapes and as 
>>> liveCache are active with the world's largest companies. Outsourcers love 
>>> to run SAP DB for its ease of maintenance. Some of them run more than 
>>> hundred system partly even in the 

- "it doesn't scale up well under heavy load or with huge amounts of
   data"
>>> Nonsense, it is fully comparable to the others

- "it's unusable in clustered environments"
>>> Nonsense, in terms of high availability clusters it can run with  common 
>>> architectures available.  

...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=daniel.dittmar@xxxxxxx



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