Thread: [Fwd: MySQL announces MaxDB as new name for SAP DB]
I am forwarding this instead of providing a link because I am currently unable to connect to www.mysql.com to get any other source for this announcement. Anyway, the business model of covering both needs - speed and features - is great. However they now have officially two different databases to manage. The only thing better than that approach is one database that is fast *and* featurefull....can this be PostgreSQL? -------- Original Message -------- Subject: MySQL announces MaxDB as new name for SAP DB Date: Tue, 5 Aug 2003 22:03:17 +0200 (CEST) From: Kaj Arnö <kaj@mysql.com> To: mysql@lists.mysql.com Dear MySQL users, The second press release about the partnership between MySQL and SAP is out. We have now announced "MaxDB by MySQL" as the new name for SAP DB, as well as some of the technical specifications for the first MaxDB release, MaxDB 7.5, out Q4 2003. What does this mean for you, the MySQL user? First, the main consequence of the SAP partnership is the same as when we announced it in the first place: you'll see the development of MySQL speed up further. The SAP partnership provides MySQL AB with resources that enables us to develop new features faster. Second, if you need features which MySQL still lacks, we suggest that you take a look at MaxDB. You'll probably find them there. MySQL AB will offer databases that meet a wide range of application needs, whether you like your database fast, stable and easy to use (as in MySQL), or whether you like it enterprise-grade and feature-packed (as in MaxDB). Third, it will now be easier for you to obtain approval from your management and customers to use MySQL in mission-critical projects. SAP is trusting MySQL AB with their database needs, so why shouldn't everyone? Although the SAP partnership opens many doors for MySQL, some things will not change. We will stay true to the three MySQL benefits that have taken us where we are today: - Performance: MySQL will not sacrifice speed for features - Stability: MySQL will not accept bugs to make delivery dates - Ease of use: MySQL will not introduce complexity beyond necessity From a technical standpoint, we are working with SAP to deliver MaxDB/MySQL interoperability that will make it possible to use MaxDB and MySQL together. MaxDB 7.5 will be able to communicate using the MySQL protocol, which means that you can use the MySQL clients on it. A primary goal is to be able to easily mysqldump data from MaxDB and pipe it into a mysql client as input to MySQL -- as well as to mysqldump data from MySQL and pipe it into a mysql client as input to MaxDB. MaxDB 7.5 also aims at supporting MySQL replication. You can then use MaxDB either as a master or as a slave to MySQL, by hooking it onto the MySQL replication mechanism. Since MaxDB is a name that is easily confused with MySQL Max, but something entirely different (namely a renamed SAP DB with MySQL interoperability on top), we will reconsider the naming of MySQL Max. We haven't decided on that name, yet. Over the next months, the sapdb.org website and functionality will move to www.mysql.com, including mailing lists, documentation and download pages. The MaxDB mailing lists will stay separate from the MySQL ones, as will the documentation, but they will all be found at www.mysql.com. Community-wise, we expect a lot of interaction between the MySQL community and the MaxDB community (which still calls itself the SAP DB community) once MaxDB is out. We hope MaxDB users venturing into the MySQL mailing lists will be given a warm welcome, quite as we encourage MySQL users to make friends with the MaxDB users on their mailing list, now still to be found at http://sapdb.org/7.4/sap_db_mailinglist.htm . To sum it up: the partnership with SAP will help us create a better MySQL database faster, give you access to an enterprise-level database, and help us all convince the world that open source creates great software! Kaj -- Are you certified? http://www.mysql.com/certification/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=kaarel@future.ee
-----Original Message----- From: Kaarel [mailto:kaarel@future.ee] Sent: Wednesday, August 06, 2003 7:16 AM To: pgsql-advocacy@postgresql.org Subject: [pgsql-advocacy] [Fwd: MySQL announces MaxDB as new name for SAP DB] >Anyway, the business model of covering both needs - speed and features - >is great. However they now have officially two different databases to >manage. The only thing better than that approach is one database that is >fast *and* featurefull....can this be PostgreSQL? Kaarel, remember that you are reading a marketing announcement. Its design is to catch your eye and make you feel good about the database. mysql has a much stronger commercial focus, for good or for evil (debatable). As a potential developer, you need to be more concerned with much more practical answers: 1. How does said database affect my development time? 2. What kind of portability issues are there? 3. What are the costs associated with commercial deployment? 4. What kind of support can I expect from the user community? 5. Does the database meet my technical requirements? 6. What are the ongoing administration costs? I have found, (in almost 6 years of database work), that postgres is a clear winner in all categories. This is a experience gained not from successful projects, but from failed ones; I've learned some hard lessons that I would not like to relearn :) IMO, as of postgres 7.1, there are few reasons to choose any other database (with the special exception of the windows platform, you may be better off with ms sql server, but not for long!). If you truly understand databases and love your work, you should have an appreciation of why this is true. Merlin
Merlin, > Kaarel, remember that you are reading a marketing announcement. Its > design is to catch your eye and make you feel good about the database. Uh, you're preaching to the choir. Kaarel was pointing out that MySQL/SAP-DB gives you a choice of 2 databases, one which is fast and one which is powerful, but with PostgreSQL, you get both qualities in one database. -- Josh Berkus Aglio Database Solutions San Francisco
merlin.moncure@rcsonline.com ("Merlin Moncure") writes:
> Kaarel, remember that you are reading a marketing announcement. Its
> design is to catch your eye and make you feel good about the database.
> mysql has a much stronger commercial focus, for good or for evil
> (debatable). As a potential developer, you need to be more concerned
> with much more practical answers:
>
> 1. How does said database affect my development time?
> 2. What kind of portability issues are there?
> 3. What are the costs associated with commercial deployment?
> 4. What kind of support can I expect from the user community?
> 5. Does the database meet my technical requirements?
> 6. What are the ongoing administration costs?
That is an excellent set of questions, relevant to _any_ evaluation of
database products. I'd suggest a couple more...
7. What kind of support can I expect from the vendor/producer, and at
what costs?
That's often separate from "user community," and also points to the
issue of what kinds of support _cannot_ be provided by a "user
community" when you're dealing with proprietary software.
For instance, if you have sufficiently severe database corruption
problems with Oracle, it is possible to get them to fly in an
engineer that has tools for manipulating corrupted databases that
aren't available to the community at large.
8. What risks do I incur by choosing the software? Does the vendor
have a history of making capricious changes to the software, licenses,
or pricing?
Apple has had a history of discontinuing products about which they
had previously made big promises, to the point to which there are
people who would, as a result, reject them outright from any sort of
vendor list. Some of the way that "Rhapsody" and Newton were dealt
with was quite disgraceful.
I have seen a few database products disappear as a result of vendors
doing buyouts and/or deciding that the products weren't in their
"strategic interests." "SOLID" SQL Server was an interesting one;
they wanted to get more into the "embedded" market, and the
~$150/host licensing option has apparently disappeared, probably to
some users' chagrin.
It looks like there will be some _very_ interesting shifts of
"strategic interests" affecting the communities presently using
MySQL and SAP-DB as a result of the conglomeration of those
products, as well as the changes MySQL AB has been making in their
licenses. Those that were depending on the previous license
arrangements for SAP-DB may need to change to anew DBMS.
--
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne> rate me
http://www3.sympatico.ca/cbbrowne/languages.html
Signs of a Klingon Programmer - 12. "You question the worthiness of my
code? I should kill you where you stand!"