Slashdot Mirror


SAP and MySQL Join Forces

An anonymous reader writes "Heise Online is reporting that SAP and MySQL are going to cooperate (German article, you may want to use Google's translation). Short summary: MySQL and SAP are going to develop a new database server. 'The primary responsibility for the development and product management is with MySQL' says SAP spokesperson Karl-Heinz Hess. Until the new database is released, SAP will continue to develop its own free database system SAP DB, however it will now use the MySQL brand name." On a related note, IBM is introducing a low-end version of DB2.

21 of 229 comments (clear)

  1. So does this mean... by zutroy · · Score: 4, Funny

    ...that MySQL will now simulcast in Spanish?

  2. SAP and MySQL - The Difference is in the Name! by Anonymous Coward · · Score: 2, Funny

    SAP's lack of success can be contributed to their name. Who wants to be called a "SAP"? No one! Coversely, MySQL's success is also due to its name. It's MySQL, and not YourSQL. Everyone loves owning things and calling them theirs.

    1. Re:SAP and MySQL - The Difference is in the Name! by grub · · Score: 3, Funny


      It's MySQL, and not YourSQL. Everyone loves owning things and calling them theirs

      Ohh.. so that's why Windows owns the desktop, because of the My Computer icon. All this time I thought it was because of robust coding and rock solid performance.

      --
      Trolling is a art,
  3. Lets hope they dont call it by sfraggle · · Score: 5, Funny

    "SAP and MySQL announced that they would call the new database 'MySQL Firebird'.."

    --
    were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
    1. Re:Lets hope they dont call it by zoid.com · · Score: 4, Funny

      They have already decided to call it Mozilla.

    2. Re:Lets hope they dont call it by Anonymous Coward · · Score: 1, Funny

      Almost, it's GNU/MySQL-MozillaPhoenixFirebird XP Plus!.

    3. Re:Lets hope they dont call it by Pharmboy · · Score: 2, Funny

      Firebird = "Firebird Isn't Really Expected to Be an Ingenious or Real Database"

      Another recursive acronym.....

      --
      Tequila: It's not just for breakfast anymore!
  4. predicting the future.... by DailyGrind · · Score: 4, Funny

    Oracle sues SAP for $1Billion dollars claiming that SAP, which had previously licenced Oracle technology, is transferring Oracle's IP to mySQL.

    L.Ellison is heard saying: "There is no way that mySQL could become enterprise ready so quickly without help from SAP and through the use of Oracle's IP"

    --
    You will have to pry my proprietary software $$$ from my cold dead hands!
    1. Re:predicting the future.... by cshark · · Score: 1, Funny

      The microsoft licenses oracle saying, "what conflict of interest? Na... We support your right to bilk the customer for all they're worth."

      --

      This signature has Super Cow Powers

  5. Never heard of SAP... by Anonymous Coward · · Score: 2, Funny

    I was kind of hoping MySQL would partner with IBM or some other high-visibility company that could deploy it at the enterprise level... you know, do for MySQL what has been done for Linux. It's a nice project, and seems to be working out pretty well here on Slashdot, but outside of that I don't think anybody is really familiar with it, which is unfortunate because I've been able to do a lot with it (OTOH, everybody seems to have heard of IBM DB, Oracle, or Microsoft SQLServ).

    So, nice to see somebody else forming some kind of partnership where perhaps the companies can prop each other up marketing-wise, but doesn't seem like that big of a deal.

  6. SAP setzt auf MySQL by rwiedower · · Score: 4, Funny

    Does this mean MySQL will now only accept SQL commands in german? That might increase the querytimes significantly....

    1. Re:SAP setzt auf MySQL by caluml · · Score: 3, Funny
      Hehe - English to German:
      * von der Tabelle IN DER somefield = "eine Last des Textes" UND des something_else > 4 VORWÄHLEN Sie;

      And back to English:
      * of the table IN somefield = "the load of the text" AND something_else > 4 PRESELECTING it;

    2. Re:SAP setzt auf MySQL by tundog · · Score: 2, Funny

      You joke about this, but have you ever tried to debug an SAP R/3 program? The comments aren't so bad, some of 'em you can even translate, but it's the variable names that are a bitch. Theey're not even words, they're 12-letter abbreviations for words like Gegengewichtsgabelstapler [fork lift].

      --
      All your base are belong to us!
  7. welcome translation, liking this am I by Linux_ho · · Score: 3, Funny

    Goods are I, for on, delights to see this. Collaboration between information technology firms is always reception. Ears love I pieces of less important by approximately large firms as well as SAP releasing its intellectual property to the open source partnership.

    --
    include $sig;
    1;
  8. But does SAP have a cute logo like by Anonymous Coward · · Score: 1, Funny
  9. oh no! by bgs4 · · Score: 2, Funny

    SAP is turning the nose!

    we're all doomed.

  10. Re:Actuality by brer_rabbit · · Score: 4, Funny

    The UNION of these two databases can't JOIN? Maybe they didn't PREPARE? If they can't COMMIT what they brought to the TABLE then perhaps they should DROP dead.

  11. Reminds me of another system.... by pjdepasq · · Score: 4, Funny
    I don't usually post this kind of stuff, but thinking that mySAP would be a good name for a new server made me think of this old Internet email I've been saving:
    Manufacturing Information Access Software System (MIASS)

    This memo is to announce the development of a new plant-wide software system. We are currently building a data warehouse that will contain all plant manufacturing data. The program is referred to as the "Manufacturing Information Access Software System" (MIASS).

    Next Monday at 9:00 there will be a meeting in which I will show MIASS. We will continue to hold demonstrations throughout the month so that all employees will have an opportunity to get a good look at MIASS. As for the status of the implementation of the program, I have not addressed the networking aspects so currently only one person can be in MIASS at a time. This should change as MIASS expands.

    Several people are using the program already and have come to depend on it. Just this morning I walked into a subordinate's office and was not surprised to find that he had his nose buried in MIASS. I've noticed that some of the less technical personnel are somewhat afraid of MIASS. Just last week, when asked to enter some information into the program, I had a secretary say to me "I'm a little nervous, I've never put anything in MIASS before." I volunteered to help her through her first time and when we were through she admitted that it was relatively painless and she was actually looking forward to doing it again. She went so far as to say that after using SAP and Oracle, she was ready to kiss MIASS.

    I know there are concerns over the virus that was found in MIASS upon initial installation, but I am pleased to say the virus has been eliminated and we were able to save MIASS. In the future, however, protection will be required prior to entering MIASS.

    We planned this database to encompass all information associated with the business. So as you begin using the program, feel free to put anything you want into MIASS. As MIASS grows larger, we envision a time when it will be commonplace to walk by an office and see a manager hand a paper to an employee and say "Here, stick this in MIASS".

    This program has already demonstrated great benefit to the company during recent OSHA and EPA audits. After requesting certain historical data the agency representatives were amazed at how quickly we provided the information. When asked how the numbers could be retrieved so rapidly our Environmental Manager proudly stated "Simple, I just pulled them out of MIASS".

  12. Google Translation by pruneau · · Score: 4, Funny
    ...or "Easy acces to the surreal for dummies"

    My two favorite:

    The chess move fits well into the Walldorfer concept to reduce the commercial meaning from data base servers to. SAP turns the nose, data bases actually the all world commodity became already longer and no cause, users enormous license costs abzuverlangen.
    Just in the mood of wasting bandwidth.
    --
    [Pruneau /\o^O/\ warranty void if this .sig is removed]
  13. Re:A dynamite combination? by PizzaFace · · Score: 3, Funny
    A database with the features that SAP DB has and the ease-of-use that MySQL offers could be very interesting indeed.
    Let's hope it doesn't end up with the features of MySQL and the ease-of-use of SAP DB.
  14. Next Generation SQL: PQL by Fweeky · · Score: 2, Funny
    Words may be longer, true, but the commands so much more authoritative!

    Sigh, when will people realise that computers work better if you're polite, meek and gentle around them; just think how much more data would be lost without people around the world repeating words to the effect of "Please, Please don't fail until this backup's complete" when hard drives start to fail!

    In this vein, I have started development of a next generation data processing language, aimed at harnessing the hugely underused power of politeness in this field, where data integrity is paramount.

    Here's an example query:
    DEAR PQL_SERVER. -- begin transaction

    ALLOW_ME_TO_INTRODUCE_MYSELF AS Mr username password. -- authenticate;
    -- username is a maximum of 1 letter, and password must be a suitably respected surname.
    -- Mrs and Ms are of course also allowed, and may have impacts on the exact
    -- speed and quality of the results, depending on server configuration and orientation.

    PLEASE_ACCEPT UPTO 20% OF MY_QUOTA. -- enable certain optimizations.

    IF (it_would_not_be_too_much_bother) COULD_YOU_PLEASE
    FETCH any_columns_you_can FROM MyTable
    AND MAYBE(IF (you_have_time))
    FILTER OUT ANY WHERE MyTable.ID IS NOT SOMEWHERE_AROUND 50.

    -- enable consistency checks in result
    PLEASE_TAKE_CARE.

    THANK_YOU_VERY_MUCH. -- end transaction; expect response within 3-4 days.
    -- Don't forget to acknowledge (THANK) the server sufficiently
    -- once it has been received, or server errors may result later.