Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

MySQL Quietly Drops Support For Debian Linux [UPDATED]

Posted by kdawson on Wed Dec 13, 2006 11:35 AM
from the any-color-as-long-as-it's-black dept.
volts writes "MySQL quietly deprecated support for most Linux distributions on October 16, when its 'MySQL Network' support plan was replaced by 'MySQL Enterprise.' MySQL now supports only two Linux distributions — Red Hat Enterprise Linux and SUSE Linux Enterprise Server. We learned of this when MySQL declined to sell us support for some new Debian-based servers. Our sales rep 'found out from engineering that the current Enterprise offering is no longer supported on Debian OS.' We were told that 'Generic Linux' in MySQL's list of supported platforms means 'generic versions of the implementations listed above'; not support for Linux in general." Update: 12/13 20:52 GMT by J : MySQL AB's Director of Architecture (and former Slash programmer) Brian Aker corrects an apparent miscommunication in a blog post: "we are just starting to roll out [Enterprise] binaries... We don't build binaries for Debian in part because the Debian community does a good job themselves... If you call MySQL and you have support we support you if you are running Debian (the same with Suse, RHEL, Fedora, Ubuntu and others)... someone in Sales was left with the wrong information"
+ -
story

Related Stories

[+] PostgreSQL vs. MySQL comparison 390 comments
prostoalex writes "Ever find yourself wondering which open source database is the best tool for the job? Well, wonder no more, and let your tax dollars do the work in the form of Fermi National Accelerator Laboratory publishing this unbiased review of MySQL vs. PostgreSQL. After reading it, however, it seems that MySQL ranks the same or better on most of the accounts." My poor sleepy eyes misread the date of posting on here; caveat that this is more then 15 months old.
[+] Ian Murdock: Debian "Missing a Big Opportunity" 330 comments
Natester writes "While Debian struggles to get its next release (Etch) out the door, the project's founder, Ian Murdock, has spoken out about politics, the lack of firm leadership, and Ubuntu's meteoric rise in prominence. Murdock believes that Debian is "process run amok" — nobody feels empowered to make decisions, leading to the sluggish rate of progress."
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.
  • Oh well (Score:5, Insightful)

    by 0racle (667029) on Wednesday December 13 2006, @11:37AM (#17223332)
    Is it really a problem? If you worried about support wouldn't you be using a distro that also offers support contracts?
      • Re:QUIETLY? (Score:5, Informative)

        by uglyduckling (103926) <uglyduckling.flashmail@com> on Wednesday December 13 2006, @12:16PM (#17223944) Homepage
        The real problem? "MySQL Quietly Drops Support..." ? Ok - so what should they do? Place posters all around your city saying "WE DROP SUPPORT FOR DEBIAN USERS!!!"?

        I think the point is that they haven't made it clear, even on their website [mysql.com] that they have made a business decision to ignore everything but Red Hat and Suse. From the story: "We learned of this when MySQL declined to sell us support for some new Debian-based servers. Our sales rep 'found out from engineering that the current Enterprise offering is no longer supported on Debian OS.'". So a company got bitten by using a generic (Debian) Linux then asking for support and finding out that "generic" means anything but.

        They really should make some sort of statement, even if it's market spun, e.g. "...for the benefit of our enterprise customers we are concentrating on supporting the two most popular commercial distributions... we expect third-party support companies and the active MySQL community to continue supporting less popular and non-commercial distributions". (P.S. for the benefit of anyone flicking through, I made that up!)

  • Bit misleading (Score:5, Informative)

    by Anonymous Coward on Wednesday December 13 2006, @11:38AM (#17223344)
    MySQL (the database) still works with Debian, but MySQL (the support company) no longer sells support for Debian.
        • Re:Bit misleading (Score:5, Insightful)

          by jellomizer (103300) on Wednesday December 13 2006, @01:50PM (#17225326)
          Get one system with Red Hat. Put MySql on it get the suport. If the problem doesn't work on red hat and your own. Then call them up and tinker with the one RedHat box until it works and do the same on your box. Supporing every Linux Distro is disasterious for a company. To many of them all with their own quarks it make offering support near impossible. By sticking to a few Distros they can quickly figure out if it is an OS Problem or a MySQL problem.
        • Re:Bit misleading (Score:5, Informative)

          by modir (66559) on Wednesday December 13 2006, @02:25PM (#17225914) Homepage Journal
          The article here on Slashdot is a little bit misleading. You still can get support from them. Them main part is this:
          Will you support MySQL Binaries built by third-party vendors? No.
          http://www.mysql.com/company/legal/supportpolicies /policies-04.html#q04 [mysql.com]

          The person who wrote this article wanted to take the binaries provided by Debian. And this doesn't work. But if you take the binaries from MySQL you should still get support.
  • Solution (Score:5, Informative)

    by Shawn is an Asshole (845769) on Wednesday December 13 2006, @11:41AM (#17223378)
    Loudly drop support for MySQL. Here are two excellent alternatives:

    PostgreSQL [postgresql.org]
    Firebird [firebirdsql.org]

    Still, Debian provides good MySQL packages. Use them instead. If you need support, I'm sure you could find someone to provide it for you.
      • Re:Solution (Score:5, Insightful)

        by Anonymous Coward on Wednesday December 13 2006, @12:03PM (#17223750)
        Ahh, the good old "who do you sue" chestnut. How's suing Oracle working out for you whenever you find bugs in their database, or if you got bad advice from their support techs?
        • Indeed... (Score:5, Insightful)

          by Svartalf (2997) on Wednesday December 13 2006, @12:18PM (#17223972) Homepage
          The "who do you sue" line's as old as the hills and, largely speaking, irrelevant because you're never
          going to get to first base unless it's a screw-up of epic proportions. Even then, it's more likely to
          be a colossal waste of your time and merely an exercise of fattening your lawyer's wallet.
      • Re:Solution (Score:5, Interesting)

        by virtual_mps (62997) on Wednesday December 13 2006, @12:06PM (#17223814)
        you think that mysql support will buy unlimited legal/financial liability for costs incurred by downtime of your mysql installation?

        really?

        seriously?

        hahahahahahaha

        What your support contract buys you is the ability to call someone on the phone. If it makes your boss happy to have someone to call and yell at when shit breaks, well, ok.
      • Re:Solution (Score:5, Insightful)

        by Thomas Charron (1485) <twaffleNO@SPAMgmail.com> on Wednesday December 13 2006, @12:22PM (#17224056) Homepage
        I have never in my entire life seen a softare company held financially liable for lost sales as a result of a database failure. Please, feel free to cite one single lawsuit if you can find one.
      • Re:Solution (Score:5, Insightful)

        by peragrin (659227) on Wednesday December 13 2006, @12:28PM (#17224150)
        You know in the software industry that is a bunch of bullshite.

        If that were true then MSFT wouldn't have any money at all as they would be responsible for billions in lost sales annually. Just one Virus through one product line(not even windows but MS SQL) a year would be expensive. Yet MSFT doesn't have to pay so why would Mysql, or IBM, or any other software company for lost sales or data?
  • Generic, huh? (Score:5, Insightful)

    by Just Some Guy (3352) <kirk+slashdot@strauser.com> on Wednesday December 13 2006, @11:41AM (#17223390) Homepage Journal

    I guess that's fair - my company migrated to supporting only "generic Red Hat Database", aka PostgreSQL.

    Seriously, except in cases where you have no choice about database availability, I can't see a single reason to use MySQL these days. All of their cool features are owned by their competitors, and they're starting to pull desperate financing tricks like whittling away tech support and partnering with SCO. Are people still using it for new deployments, and if so, why?

    • Re:Generic, huh? (Score:5, Interesting)

      by LWATCDR (28044) on Wednesday December 13 2006, @11:47AM (#17223494) Homepage Journal
      Simple. Every nickel and dime hosting company uses MySQL so every CMS blog, and forum supports MySQL.
      Up to and including Slashcode.
      It is now catch 22. Everybody uses MySQL because everyone uses MySQL.
      Heck I use MySQL for our CMS because not every module supports PostgreSQL.
      I would much rather use PostgreSQL for everything but I don't have time to re-invent the wheel.
  • by Paulitics (1036046) on Wednesday December 13 2006, @11:42AM (#17223418)

    MySQL only lets me spoon it.

    But Postgre lets me fork it all night long.

  • Get Ready... (Score:5, Interesting)

    by eno2001 (527078) on Wednesday December 13 2006, @11:43AM (#17223426) Homepage Journal
    I see that a definite split of "Premium Linux" vs. "Unsupported Linux" is coming soon to a vendor near you. That doesn't mean that Linux will die, it's just going to smell funny (possibly like pee).
  • by iamjoltman (883526) on Wednesday December 13 2006, @11:44AM (#17223438)
    I see there's already a few comments that the code should be forked. The thing is, what is forking going to do for it? They are dropping support for Linux distros, but that's not saying it won't run on other distros, just that it's not supported. The only way a fork would do anything is if the forked version had it's own support as well.
  • Why all the drama? (Score:5, Insightful)

    by derrickh (157646) on Wednesday December 13 2006, @11:51AM (#17223560) Homepage
    Why is this such a sore spot for so many people? Just because MySql no longer supports the flavor of the month distro of Linux, you all throw up your hands crying 'I never liked you anyway'.

    The vast majority of mysql users will never buy a support contract, and those few who do, will probably be RedHat or Suse. (When was the last time a Debian user admitted he needed help for anything?)

    Instead of having to support dozens of distros, Mysql is supporting the main two. It may be Open Source, but it's still a business.

    D
    • Re:Let's fork it! (Score:5, Informative)

      by eln (21727) on Wednesday December 13 2006, @11:42AM (#17223416) Homepage
      I suppose you could do that, but unless you're planning on offering Enterprise support for your offering on a wide variety of platforms, you're not really gaining anything. MySQL will presumably still run on Debian, at least for now, but without the ability to buy support for it on that platform, you're not going to get approval to put it on that platform in any sort of business-critical environment.

      Now, if you wanted to start a new company that offered Enterprise support for MySQL on Debian, you might have something there. I don't know that you would make any money, but at least you'd be offering something that isn't currently offered.
      • Re:Let's fork it! (Score:5, Insightful)

        by jmorris42 (1458) * <jmorris@noSpam.beau.org> on Wednesday December 13 2006, @11:50AM (#17223544) Homepage
        > I don't know that you would make any money, but at least you'd be offering something that isn't currently offered.

        I doubt it. And more important than my opinion, MySQL doubts it and has the sales figures to show it. Companies don't normally kill off profitable products and services, not even evil/stupid corporations.
        • Profitability (Score:5, Insightful)

          by Colin Smith (2679) on Wednesday December 13 2006, @12:23PM (#17224058)

          I doubt it. And more important than my opinion, MySQL doubts it and has the sales figures to show it. Companies don't normally kill off profitable products and services, not even evil/stupid corporations.
          Just because one person can't do something profitably, doesn't mean that someone else can't do it profitably.
           
        • by brokeninside (34168) on Wednesday December 13 2006, @12:24PM (#17224086)
          If a company holds that it can make a 50% ROI on one product line and a 25% ROI on onther product line (and all other things being held equal) they will put their resources into the line with the 50% ROI until such time as the law of diminishing returns brings the marginal ROI for additional resources being added to under 25%.

          For example, when I was a kid a local pizza delivery chain started delivering breakfast pizzas. They made money hand over fist. But after a few months, the calculated that the additional cost of maintaining a third shift of workers and an expanded breakfast menu would bring in more money if put into opening additiona stores serving the traditional lunch, dinner, late night crowd with the normal pizzaria menu.

          Most likely what is happening is that the MySQL corporation finds that if it spends the same number of dollars training a support tech, those dollars bring in more money if the tech is dedicated to Redhat and/or SuSE than if the tech is also trained on Debian. This doesn't mean that there is no market for Debian support. It means only that MySQL has a higher relative profit from supporting just two databases. The calculation may be different for another company that has a different resource pool. For example a company that already supports Debian Linux, may have a very low marginal cost for adding MySQL on Debian support and, consequently, have a far higher ROI for supporting MySQL on Debian.

    • Re:Let's fork it! (Score:5, Insightful)

      by Drasil (580067) on Wednesday December 13 2006, @11:51AM (#17223568)
      Guys, it's time to fork MySQL.

      ...or switch to the excellent Postgres [postgresql.org] which is more open and a more complete SQL implementation than MySQL anyway.

      Expect to see more things like this happening as the IT landscape undergoes it's coming changes.

    • Re:Let's fork it! (Score:5, Interesting)

      by suntac (252438) <`gro.tluclanimret' `ta' `srewuoL.nahoJ'> on Wednesday December 13 2006, @11:59AM (#17223692) Homepage
      Mmm fork MySQL? Why? There is nothing wrong with the code. You could try to fork the support and start a company specialized in MySQL support on Debian.....

      I think there is a market for this. The only thing you need is a couple of good people. You/we(the community) could also create a company GPL style. Create a pool of people willing to devote there time on solving MySQL Debian support problems. Create a ticket like system and assign questions to people in the pool.

      This way you can quickly create a non-profit company with little to non investments. The biggest "problem" is that you have to attract people willing to become part of you expert pool.

      While writing this, it might even be a good challenge to start this..... I will think some more about this. :-) Anyone in? ;-)

      Regards,
      Johan Louwers.
    • by chundo (587998) <(jeremy) (at) (jongsma.org)> on Wednesday December 13 2006, @12:01PM (#17223714)
      I doubt that's the point. I'm sure they just decided that rom a cost/benefit perspective, money spent training their support staff on Debian wasn't worth the amount of business they were getting from Debian customers. Which makes a lot of sense to me - in my experience, people that run Debian servers have a more thorough knowledge of the system and administering it, and consequently have less need/desire for software support (yourself included, it sounds like). And assuming that's true, it's also not much of a stretch to assume that someone that interested in the guts of a system would choose something like Postgres over MySQL anyways if they had a choice, since it's had more advanced features for much longer than MySQL has.