Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Oracle Lines Up Unbreakable MySQL

Posted by Hemos on Mon Jan 29, 2007 12:10 PM
from the the-swirling-of-large-and-small dept.
munchola writes "MySQL CEO, Marten Mickos, has revealed to CBRonline that Oracle has threatened to provide support for MySQL and is already distributing the open source database. "They have hinted to us that they will," said Mickos, indicating that the database giant is planning to repeat its October 2006 Unbreakable Linux plan, which saw it undercut Red Hat with enterprise Linux support. Despite the competitive threat, Mickos is unmoved. "I hope they do that," he said, noting that it would be seen as an endorsement of the open source database.""
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • I find it hard to believe that a company with the amount of overhead that Oracle has will be able to provide mySQL support for the same rates that mySQL can; the primary benefit for Oracle is that they'll be able to offer bundled support with people who already have Oracle support and want the convenience of dealing with one company for all their support needs.

    Definitely a win-win situation for mySQL, because they get press and legitimacy without losing too much business. The "unbreakable linux" deal probably hurt RedHat a hell of a lot more than this will hurt mySQL.
    • by khasim (1285) <brandioch.conner@gmail.com> on Monday January 29 2007, @12:31PM (#17801802)
      Same reasons. The more publicity, the better. If Oracle believes in it enough to offer support, everyone else can feel a little bit easier about using it.
      • by Zonk (troll) (1026140) on Monday January 29 2007, @01:03PM (#17802324)
        I doubt they'd support PostgreSQL. MySQL is basically a non-competitor. While PostgreSQL still isn't, it's much closer. Postgres is fully ACID compliant, is very strict about it's data, has mature support for just about everything (still lacks in clustering and replication, though...), is very fast, scales well, etc.

        When you hit the limitations with MySQL, need a feature it doesn't support, etc, Oracle can point you to a sales rep. There are far less limitations with PostgreSQL. It wouldn't make as much business sense to encourage it's use.
        • by Electrum (94638) <david@acz.org> on Monday January 29 2007, @05:18PM (#17805712) Homepage
          Postgres is fully ACID compliant

          As is MySQL [mysql.com].

          has mature support for just about everything

          It lacks anlaytic functions [oracle.com].
                • Re: (Score:3, Informative)

                  (This might in itself be a stupid example, but this(That mysql will commit, even if the transaction contains error) is a real problem, when doing developing using java/php))

                  This behavior is perfectly valid. Oracle does the same thing. This is a feature: you, the user, can choose to ROLLBACK or continue on error. Would you want a typo to abort a transaction during interactive use?

                  SQL> CREATE TABLE t (id int NOT NULL UNIQUE);
                  Table created.

                  SQL> SET AUTOCOMMIT OFF

                  SQL> INSERT INTO t

      • by ortholattice (175065) on Monday January 29 2007, @01:23PM (#17802624)

        Same reasons. The more publicity, the better. If Oracle believes in it enough to offer support, everyone else can feel a little bit easier about using it.

        I doubt it. Unlike MySQL, PostgreSQL is much more of a direct competitor to Oracle. In fact, I've converted PG databases to Oracle with ease. (Why did I do this? The client wanted Oracle, so I ported our PG product to it.) The translation of some rather intensive PL/pgSQL to PL/SQL was almost trivial, with a translator script I wrote in a day. The resemblance is so close that if I didn't know better (and maybe I don't), I would almost say PG "borrowed" some of its syntax from Oracle. Going back would be a little harder if some of the more obscure Oracle PL/SQL features were used, but probably not rocket science for most applications. There are other interesting resemblances - you can see very meticulous, almost obsessive Oracle emulation in the behavior of date/time stuff (search the PG source code for "Oracle" - beautifully commented stuff is in there).

        With MySQL on the other hand, even without getting into an ACID problems discussion (some of which have been improved in recent releases), has a very poor feature overlap with Oracle, not a minor one being not having anything like PL/SQL.

        I guess the thing that bothers me personally about this is that it is publicity for MySQL, subconsciously encouraging more people to adopt it over the (IMHO) much better PostgreSQL. I think that it will poison your mind to learn DB theory from MySQL. :) But that is just my personal view and I encourage alternate viewpoints.

      • Same reasons.

        The same reasons being most likely that by "supporting" MySQL or PostgreSQL they are effectively suffocating the companies who continue to develop of those databases and probably poaching a few sales too. Eventually those other companies might go down the tubes or at least suffer financially and Oracle can turn around and claim "see you can't trust open source, buy Oracle".

        I wonder why MS doesn't try the same thing - push out Microsoft Linux, complete with a free Vista / Windows runtime i

    • Re:Mikos is right. (Score:5, Interesting)

      by jimbojw (1010949) <.moc.liamg. .ta. .r.mij.nosliw.> on Monday January 29 2007, @12:39PM (#17801942) Homepage

      > the primary benefit for Oracle is that they'll be able to offer bundled support with people who already have Oracle support and want the convenience of dealing with one company for all their support needs

      This is not a trivial point.

      Brand recognition goes a long way when a company is shopping for support. Companies that already pay for Oracle support might be very willing to tack-on MySQL support from them, rather than to establish a new relationship with MySQL.

      Also, since Oracle will be distributing the MySQL database themselves, the unsuspecting middle-manager might think that "MySQL" is just another Oracle offering, or component of their architecture. It's the old "bundled with" implies "created by" heuristic.

    • Oracle has one kind of customer, MySQL has another kind of customer.

      Just a guess, but I'll go out on a limb and state that any hopes MySQL had in wooing really pricey billable hour customers is evaporating. Even if I'm wrong, the mood at MySQL has probably been a little less happy when they figured out Oracle was going after the top of the consulting/support dollars.

      There's still *so* much they have to offer for businesses willing to pay. They just need to keep at it and understand that Oracle won't be th
      • There are things that we don't support, sure, but claiming that we don't support primary keys is ridiculous.

        I suggest that the parent is ignorant and/or trolling.
  • by Anonymous Coward on Monday January 29 2007, @12:19PM (#17801564)
    Sounds great! Maybe GM will "threaten" to buy fuel for my car, or Amazon will "threaten" to return my library books for me so I don't have to.
  • by Sweetshark (696449) on Monday January 29 2007, @12:26PM (#17801712)
    Customer: XYZ doesnt work. Help me!
    Oracle: MySQLs XYZ is crap - you better buy a real DBMS. As a support customer we can offer you Oracle 10g Enterprise at a reasonable prize!
    • If you don't know why you need Oracle, you don't need Oracle.

      Oracle makes it's money primarily by selling support and service, not by selling licenses, so while they may try to sell you a license, they're not going to go out of their way to snag an itty-bitty fish that's not going to be able to afford support.

      And frankly, if you're big enough to afford support, you probably DO need Oracle...mySQL is a good tool, but I'd be really hesitant about setting up a big accounting system on mySQL.
      • Re: (Score:2, Insightful)

        And frankly, if you're big enough to afford support, you probably DO need Oracle...mySQL is a good tool, but I'd be really hesitant about setting up a big accounting system on mySQL.
        That's what PostgreSQL is for.
    • On the other hand, Oracle 10g is overkill for many shops. MySQL is a great solution for many small databases, and Oracle Support now offers some more legitimacy to the product.

      I've seen a number of shops with a situation like this:

      Customer: "We're a small shop. We need an RDMBS. We can't afford a DBA. The sales rep said the Oracle Installer is easy to use, and I can install Oracle on my own.

      But to install the Oracle *client* , I need to download 3 ISOs, install Xwindows on the server, tunnel Xwindows over SSH. While installing the Oracle Server, the installer crashed out halfway through due to some Java bug. When I tried the installer a second time, the installer refuses to proceed and says that this database already exists.

      I called your support line urgently for help, and was transferred not once, not twice but SIX times before they threw my case over over to some department called 'Customer Care' because of a problem with my 'entitlement'. This is my first time calling Oracle Support, so forgive me if I don't understand your byzantine phone support.

      I opened this case last Thursday. Today is Tuesday, and I only just heard back from the entitlement department--- I called Saturday, but was told I had to call back Monday (I thought I said this was urgent)--- they finally got back to me with the proper license.

      Now that I have the license, can someone please help me with the problem I ran into 5 days ago?

      While I was waiting for this problem, my friend came over, installed MySQL in 5 minutes, and created a basic data model in 30 minutes. I can do basic data changes with phpMyAdmin. THIS is what I need. Please tell me why I need to spend $10K on some Oracle 10g Support Licenses?"
      • I would love to know if you could install mysql by yourself and not hit any issues? Maybe the problem here isn't the software..?

        I know plenty of people who have installed Oracle by themselves, with 10g its pretty simple. I've installed Oracle on many systems and i've never had to do what you've described.

        Sounds like you need to spend money on support because your going to need it sooner or later... You may want to be a bit proactive and go buy some support from mysql right now.
        • Re: (Score:3, Interesting)

          I once did a "developer usability study" for some uni class, was told to basically get on the net, and set up the computer to be a development environment for developing a small dynamic webpage with a db backend.
          Having never done web dev before I went with the biggest target, MySQL backend with apache/php front, literally took me 5 minutes to download and install MySQL with its nice developer tools, and maybe another 10 minutes to have a reasonable understanding of how those tools work.

          Now, I've never in
      • installed MySQL in 5 minutes, and created a basic data model in 30 minutes ...and six months later we realized that none of our data integrity checks had actually been enforced.
      • But to install the Oracle *client* , I need to download 3 ISOs, install Xwindows on the server, tunnel Xwindows over SSH.

        Installing the Instant Client [oracle.com] involves merely unzipping a file.
  • by dk.r*nger (460754) on Monday January 29 2007, @12:28PM (#17801744)

    ..and is already distributing the open source database
    Oracle distributing MySQL? Now, there's a sound business decision if I ever saw one. 80%(*) of Oracle's customers are there for buzzwords compliance - now they can get the database they actually need, and Oracle stays synonymous with databases in the enterprise.

    The rest of us can push MySQL saying "this is what Oracle recommends, just free".

    (*) I just pulled that number from clear air.
    • by Rob T Firefly (844560) on Monday January 29 2007, @12:32PM (#17801810) Homepage Journal

      (*) I just pulled that number from clear air.
      As a highly-trained professional business analyst at the top of my field, I'll thank you to stop muscling in on my freaking scam.
    • by martenmickos (467191) on Monday January 29 2007, @01:35PM (#17802798)

      Thanks everyone for the interesting comments. It's a good discussion and I think there have been some good points made. I see Oracle and MySQL serving two distinct markets, so in most cases we are not competitors.

      One point of clarification: I never said that Oracle has threatened MySQL. (I think this may have been the writer's editorial comment.) Instead, I view it as a positive thing that Oracle distributes MySQL. I have often suggested that Oracle should distribute MySQL and I've made the same suggestion to Microsoft. Perhaps Oracle, Microsoft or IBM will provide support for MySQL and that could be good for open source in general. (And note that Red Hat, HP and others already do so.)

      If people want to buy support for MySQL from Oracle, that's great. And of course, if they want to buy it from us, we are fine with that also.

      -Marten Mickos, MySQL AB
  • Oh man, how low can you go? Providing support? How DARE they!

    Really though, I think people will see it as an endorsement (and more so, people might think that Oracle is losing faith in its flagship product). It's one thing to provide support for Linux, but MySQL is directly competing with Oracle (to a degree). I really don't know what message they're trying to send here, but if it's that people should buy Oracle, I really don't see how this will help.

    Anyway, competition is good. If Oracle thinks it can
  • Oracle (Score:5, Informative)

    by Scareduck (177470) on Monday January 29 2007, @12:39PM (#17801940) Homepage Journal
    Actually buying their products was an out-and-out nightmare, as the rules changed every six months. You never got a consistent sales rep dedicated to your account, and they were always bringing in someone new who couldn't explain what was going on especially well. You had to keep buying new releases, because support for old versions died out, quicker and quicker over time.

    As for Oracle support, it was the main thing we looked forward to at first (this was the mid-90's); but it, too, got worse over time. I would not trust Oracle to properly support MySQL, especially since they have no motivation to push it, and they are not the developers (and in fact are in competition with them).

    • Re:Oracle (Score:5, Insightful)

      by Rorschach1 (174480) on Monday January 29 2007, @01:47PM (#17802962) Homepage
      You're obviously using the wrong channels. I've never had any trouble obtaining Oracle licenses. The streamlined acquisition process goes like this:

      1. Government agency your company works for pays $90 million for Oracle licenses
      2. Larry Ellison gives your congressman a nice campaign contribution
      3. Government agency happily hands over license certificates by the wheelbarrow load to show that they were needed in the first place

      Never once had to deal with a sales rep.
  • Upgrade Pathing (Score:4, Insightful)

    by Phrogman (80473) on Monday January 29 2007, @01:02PM (#17802286) Homepage
    I am sure this is just an effort on Oracle's part to capture as much of the low end database market as they can, then offer a seemless, supported upgrade to Oracle's DBMS for those who reach the limits of mysql or who start needing requirements that mysql can't support. This lets them continue to bombard customers with reasons to upgrade, while still getting support contract money from them. If the mysql community benefits from this, I am sure its just an accidental byproduct of a marketing and sales effort and nothing more.
  • by mangu (126918) on Monday January 29 2007, @01:22PM (#17802604)
    While many people are commenting that Oracle's motivation is to gather sales for their own DB, I can see another motivation here. Oracle maintenance can be a nightmare for unexperienced DBAs. If they can move their lesser customers to MySQL that could mean less support costs for Oracle, while keeping the paying customer.


    I doubt very much that most DBAs that have a support contract with Oracle and move to MySQL will say "OK, now we don't need that contract anymore". They will keep it as insurance for who knows if MySQL will work as expected? They feel they may need to move back to Oracle in the future. After all, if they had felt at ease with MySQL to begin with, they wouldn't need Oracle to tell them how good it is.

  • From the company that censors [argeniss.com] people pointing out how shoddy their in-house software is?
  • Yeah, so they'll offer the same mess of convoluted support that they do for their Oracle database. Big Deal.

    I can provide Oracle support on a two-headed coin: Side A - you must have a typo somewhere; Side B - you'll need to find a work-around.

    And, of course there'll be another user forum of everyone asking for the same help that you are (with very few useful answers).

  • . . . to the Nine Circles of Oracle Support Hell.

  • by C_Kode (102755) on Monday January 29 2007, @01:44PM (#17802928) Homepage Journal
    C_Kode Software is releasing a new version of the MySQL Database. Very Unbreakable MySQL (V.U.M.) MySQL. This will be based of anything that we like and will prove to be better because I said it was. It will be very fast. We like to call it Vroom VUM! Does your app VUM? If not, shell out $50 a year to me and I will allow you to tell anyone your app VUMs.
  • The thread here seems to question (a) the value of Oracle and (b) why this would be good for Oracle's customers. Here are my 0.0002 cents:

    My current client is a large insurance company. (More than $7 billion dollars of policies a year underwritten by a staff of more than 1,200 people.)

    We have lots of Oracle, SQL/Server, and MS/Access applications all over the place. The Oracle data is generally available to everyone. We have more than 50 analysts who use a combination of Hyperion (formerly Brio) and SAS
    • by nuzak (959558) on Monday January 29 2007, @12:23PM (#17801648) Journal
      > If you came up with a ratio of $spent/$productivity, Oracle would probably throw a divide by zero error.

      Whereas MySQL would silently insert a default value.
    • Re:Oracle Sucks (Score:4, Interesting)

      by MyLongNickName (822545) on Monday January 29 2007, @12:28PM (#17801732) Journal
      Serious question: What exactly is the advantage of Oracle over SQL Server? I asked that to an Oracle DBA once, and he just got red in the face and stammered about having more options to configure things the way he wanted. I asked what exactly he configured, and basically got a lecture on Microsoft being evil. I then asked if he thought Larry Ellison was a saint, and the conversation just continued to devolve.

      Serious question: why is Oracle considered so much better that SQL Server?
      • Re: (Score:2, Interesting)

        I've taken two Oracle classes (could have gotten certified, but I really didn't care that much). Basically, unless you're running into the tens of thousands of users, there's not much difference. Now, as a DBA, there are some things I would prefer to do in Oracle rather than SQL Server (though I'd much rather do them in an open source DB like MySQL or PostgreSQL), but I don't think it's worth the (massively) added cost unless you really are running it in an enterprise situation.
      • Re: (Score:3, Insightful)

        What exactly is the advantage of Oracle over SQL Server?
        Primarily, I would imagine that the advantage is that you don't have to run your DB on Windows, which has not had such a "rock solid" reputation in the past (compared to the Unix derivatives).
      • Re: (Score:3, Interesting)

        What exactly is the advantage of Oracle over SQL Server?

        I'm rather fond of their Analytic Functions [orafaq.com], which allow for convenient queries against other table rows. For example, given a table of time-stamped log entries you can write a query to "Show me the time intervals between successive log entries."

        I'm hoping these will show up in Postgresql soon.
        • Interesting reading, for sure. I know I have spent a lot of time writing "complex" SQL queries to accomplish the same thing. Interesting having a built in functions that will help accomplish the same thing.

          Question: Performance-wise, is this the equivalent of using SQL subqueries? Or is there some type of database optimization that gives it a performance advantage?
      • Re: (Score:3, Informative)

        >"Serious question: What exactly is the advantage of Oracle over SQL Server? I asked that to >an Oracle DBA once, and he just got red in the face and stammered about having more options >to configure things the way he wanted. I asked what exactly he configured, and basically >got a lecture on Microsoft being evil. I then asked if he thought Larry Ellison was a >saint, and the conversation just continued to devolve.

        >Serious question: why is Oracle considered so much better that SQL Server?"
        • Re: (Score:2, Interesting)

          by Anonymous Coward
          Not quite true. I supported a large customer (a national, no nationwide, building society in the UK), that has several million customers in the DB, and a couple of thousand users directly logged onto it, and several thousand remote users. (this is SQL Server BTW), and its fine, fast and responsive.

          Now, the things we had to do to make this work are basically: use stored procedures.

          Now I work with a large breakdown company that uses Oracle, and we've seen barely a difference. Oracle is just as performant, and
      • by Evets (629327) on Monday January 29 2007, @03:03PM (#17803982) Homepage Journal
        Oracle performs better in enterprise environments, hands down. Oracle Clustering is more intelligently implemented than SQL Clustering. PL/SQL scripts are easier to debug than those in MS SQL.

        OTOH, SQL Server is extremely simple to install and administer for low volume environments. DTS Provides a nice simple transport mechanism. Enterprise manager, while kludgy, is relatively intuitive.

        For fine tuning, Oracle provides finer control - but that's not to say that SQL doesn't provide a lot of control over DB Tuning features.

        Then there are the little things that crop up over experienced usage - like the first time you try to take a MS SQL backup from one machine to another and end up perplexed for an hour. Or when you're 6 gig backup file won't copy from one machine to another without 3rd party software (really a windows issue, not SQL Specific). Or when you discover that you can't replicate certain tables or columns, can't copy blobs using sql scripts, etc. Things like that.

        A lot of applications treat the database as a storage engine and leave platform specific performance enhancements by the wayside in favor of database-agnostity. Because of this, MySQL is much closer to being a legitimate competitor than you would think. People talk about "ACID Compliance", but really most applications don't need ACID Compliance and just because you can't do something one particular way doesn't mean it can't be done.

      • I don't have enough MS SQL 2005 experience, but MS SQL 2000 didn't scale very well. The implementation of "shared locks" and "lock escalation" in MSSQL meant that many readers + one big writer = near total database deadlock. The readers would be locked-out every time the writer touched a page they were reading. Oracle, PostGreSQL, and SQL 2005 support a system where readers never interfere with writers.

        I know that there are big database features in Oracle that are way over my head and I can't go into. S
      • Microsoft SQL Server (which is Sybase in diguise) has an in-memory lock structure; if your transaction acquires too many row locks, your locks are escalated (to page locks or table locks). While these rows are locked, readers are blocked.

        Because of this, your are encouraged to keep your SQL Server transactions as short as possible. By default, isql DML commits after every statement, and you must use a BEGIN TRANSACTION/COMMIT if this is not what you want.

        Oracle does not use a memory structure for row lo

      • To be honest, if said person only knew one DBMS and not the other, they're not qualified to answer those questions anyway.
    • by Rorschach1 (174480) on Monday January 29 2007, @12:36PM (#17801892) Homepage
      They're not aimed at the same markets. I haven't followed this too closely, but I assume the reason Oracle is interested in MySQL at all is that they're somewhat complimentary products. MySQL is great if you want a lightweight, fast database that doesn't need to be terribly robust.

      I doubt MySQL is ever going to have the sort of PL/SQL support Oracle does, and you're not likely to see things like enterprise-class clustering, data partitioning, replication, and so forth. If you added all that to MySQL, it'd wind up just like Oracle - big, complex, and expensive. They occupy opposite ends of the spectrum.

      And for what it's worth, I've got an Oracle database on a modest single-processor AMD server with a single hard drive handling about 20 inserts per second with R-tree spatial indexing and it keeps up just fine, with a bit of tuning. Given a real server with multiple drives I'd be able to optimize things much better, but it's just a testbed.

      Comparing MySQL to Oracle is a little like comparing a high-performance motorcycle to an M1A2 tank. They'll both get you from point A to point B, but with different levels of cost and safety.
      • I doubt MySQL is ever going to have the sort of PL/SQL support Oracle does, and you're not likely to see things like enterprise-class clustering, data partitioning, replication, and so forth. If you added all that to MySQL, it'd wind up just like Oracle - big, complex, and expensive. They occupy opposite ends of the spectrum.

        And that heaven for that! Look, most of us want a database system we can use for our own limited but still important purposes. We don't need a lot of enterprise-level crud bogging us down. I'd never think of using MySQL on the large scale, but then that's what I have Oracle for. Oracle is over-muscled for a lot of simple stuff; MySQL is better for a medium-weight application.

        And as an aside, the reason that Oracle is doing this is to get their name in the small-to-middle size market. Oracle's been dominating larger firms for years now, but that means there's little room for growth. If they can try to reach smaller markets and spread their name around, when some of these smaller companies outgrow their MySQL set-ups, Oracle will be ready to step in with their enterprise apps.

        • > Look, most of us want a database system we can use for our
          > own limited but still important purposes. We don't need a
          > lot of enterprise-level crud bogging us down.

          So true. I'm running a small database (only 20 million records) [blogs.com], and PostgreSQL [postgresql.org] is more than sufficient. We use it in production, too [getindi.com], and it's quite solid.

          Maybe someday when we get up to 100 TB or so we'll think about something else, but by then PostgreSQL will probably be capable of handling that load as well...
      • Re: (Score:3, Interesting)

        Rorschach1,

        Indeed we view MySQL competing in different markets from the legacy closed source databases. We have focused on new applications, often web-based systems, ecommerce, reporting, analysis and so on, rather than traditional ERP applications. There are many features that DB2 and Oracle have of which they are very proud. And we are also proud *not* to have all of the complexity of those features. Our focus is not on features, but on reliability, ease of use and performance.

        Charles Phillips of Orac
    • "Postgres, the only other threat on the first point, was nullified with Oracle's acquisition of the only backend to it with atomic commits"

      No, it was the innodb for MySQL that Oracle acquired, this has nothing to do with PostGresQL. Unlike MySQL PostgresQL has always had attomic commits.