Dear SAP DB Community, MySQL has today announced that the SAP DB database will be rebranded as "MaxDB," which will be offered as a MySQL AB product beginning in Q4 2003. This letter is written to inform you, the SAP DB community member, what this rebranding is all about and how it will affect you.
According to the partnership between SAP and MySQL, MySQL acquired full commercial rights to develop and market future releases of SAP DB. In order to utilize these rights, the agreement specifies that SAP DB is to be renamed under a MySQL brand. This rebranding has now been agreed upon, and from Q4 2003, the name of the product will be MaxDB. The name MaxDB retains the "DB" part of SAP DB, and the "Max" part refers to the full set of features and enterprise level functionality that characterises SAP DB. Below the main effects of the rebranding are explained. We at MySQL are very much committed to working closely with the SAP DB community, and we hope that the transition plan will enable you to easily and smoothly continue your cooperation with us in making the SAP DB / MaxDB an even better and more popular database for the whole open source Community. SAP DB - MaxDB rebranding: 1. Versioning and new interoperability features 2. Web site, documentation and downloads 3. Support and mailing lists 4. Licensing and the availability of old version 1. Versioning and new interoperability features The SAP DB versioning will be carried over to the new MaxDB release. This means that the following version after SAP DB 7.4 will carry the new name and thus be Max DB 7.5.0. MaxDB 7.5 will offer new functionalities for the user interested in interoperability with MySQL. A MySQL proxy will be available making it possible to connect using the MySQL protocol to the MaxDB server. This enables the user to utilize familiar MySQL clients and practical MySQL tools like mysqldump and mysqlimport with the MaxDB database. Another useful addition is an understanding of the MySQL replication protocol, which makes it possible to easily put up a replication where a MaxDB is acting as a slave to a MySQL master database. For SAP DB users a smooth and easy upgrade will be offered from SAP DB 7.4 to MaxDB 7.5. Due to the SAP Netweaver 6.40 release schedule the first MaxDB 7.5.0 will be a pure rebranded SAP DB 7.4. MaxDB 7.5.1 will provide the described MySQL-related added functionality. The aim of the interoperability between MaxDB and MySQL is to make it easier for present MySQL users to use MaxDB. We depend on the SAP DB community to help any such new MaxDB users, just as we depend on the MySQL community to help newcomers among the MySQL users. 2. Web site, documentation and downloads An important change for you as a SAP DB user concerns the website. In Q4 when MaxDB is released, the www.sapdb.org website will move to www.mysql.com/maxdb/. From then on, all relevant MaxDB information, documentation and downloads will be available under the MySQL website. The pages on www.sapdb.org will be permanently redirected to the corresponding pages on www.mysql.com. The MaxDB documentation and download pages will be integrated with the MySQL documentation and download pages. SAP DB versions 7.3 and 7.4 will be made available for download on www.mysql.com during a sunset period until 31 March 2004. After that only MaxDB will be offered. 3. Mailing list The main interactive channel for SAP DB users has been the mailing lists, where SAP personnel have actively participated. SAP has indicated to us that they plan no change in their mailing list presence after the MaxDB release. The actual mailing lists will however be renamed with maxdb instead of sapdb and moved to the MySQL listserver (@lists.mysql.com). The transition requires no actions from the subscribers of the mailing lists as they will be automatically moved to the renamed lists. The mailing lists will be moved by the end of September 2003, and information regarding the move will be sent to all subscribers. Should you no longer wish to be part of the renamed maxdb mailing list, you are of course free to unsubscribe either before or after the transition to @lists.mysql.com. However, we very much look forward to your continued subscription to the renamed list. 4. Licensing and the availability of old versions MaxDB will follow the MySQL dual licensing policy, which in short is "if you're free, we're free -- if you're commercial, we're commercial". This means that the product is released completely under the GPL and that a commercial license is offered to those customers who wish to distribute it commercially, without themselves being GPL. SAP DB has been offered under a different licensing scheme, as the interfaces have been L-GPL. As MySQL is increasing its expertise in MaxDB, we hope to work together closely with you to create opportunities for each other. Our joint interest is to build up the momentum for MaxDB, increasing its use and the supply of services around the product. Let's help each other out in this venture! Please contact us, either on this list or in private, to suggest to us what we can do for the future of SAP DB, now renamed MaxDB! Best regards, The SAP DB team of MySQL AB, now renaming itself The MaxDB team of MySQL AB _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
