MySQL
Analysis of open source DBMS vendor MySQL (recently acquired by Sun Microsystems), its products, and other products in the MySQL ecosystem. Related subjects include:
Infobright update
In connection with the announcements that:
- Infobright is open sourcing its analytical DBMS product (which is a really good idea)
- Infobright raised a $10 million VC round, with Sun as a new investor
I got my first real Infobright update since January. Highlights included: Read more
| Categories: Data warehousing, Infobright, MySQL, Open source | 2 Comments |
Infobright’s open source move has a lot of potential
Infobright announced today that it’s going full-bore into open source – specifically in the MySQL ecosystem — with the licensing approach, pricing, distribution strategy, and VC money from Sun that such a move naturally entails. I think this is a great idea, for a number of reasons: Read more
| Categories: Columnar database management, Data warehousing, Infobright, MySQL, Open source | 4 Comments |
Infobright goes open source — sound bites
As has recently become my custom when there is industry news, I herewith provide quotable sound bites about Infobright and its move to an open source strategy. Weather permitting, I’ll be on a plane to the Netezza conference this afternoon. And I’ve only slept about 10 hours since Thursday. So I hope these suffice, although if they don’t and you email me I’ll try to respond by some time Tuesday morning.
- For almost anybody in the MySQL world who needs high-performance analytics, Infobright is the first good solution.
- Infobright’s product strengths and use cases are a great match for open source.
- Most leading analytic DBMS have open source roots, but they generally haven’t been open sourced themselves. Infobright immediately becomes one of the premier open source analytic database offerings. The only serious open source rival that’s coming to mind is MonetDB.
- Storage engines are MySQL’s achilles heel. Each good MySQL storage engine is precious.
- Infobright has enough production references to show that it can get the job done for many data mart uses. It won’t meet everybody’s needs, but it’s well worth an experimental download.
- If you want to build a little data mart and run it yourself, most good products are too complicated or expensive. But in the right use cases, Infobright pretty much runs itself, and there’s no arguing with the Community Edition price (free).
- So Infobright is a great fit for the individual downloader – i.e., for the stereotypical open source user.
- Netezza, DATAllegro, Vertica, ParAccel, Greenplum, and Aster Data are all based in one way or another on PostgreSQL (even though Vertica includes no PostgreSQL code). DATAllegro was based on Ingres. Infobright and Kickfire are based on MySQL.
- If Infobright doesn’t get the job done, try downloading Vertica, which – while closed source – is also free for download and development.
- The “rough set” part of Infobright’s story is a lot of mumbo-jumbo, but the “knowledge grid” part is more real.
- When you compare Infobright to Teradata, Netezza, Greenplum, or even Vertica, it’s kind of a toy. But when you compare it to generic MySQL, it’s more like rocket science.
- Infobright was too little, too late in the mainstream analytic DBMS market. They had to do something different. Kudos to them for recognizing that.
- The Infobright product has some serious limitations. If you want a market that’s willing to adopt a DBMS with serious limitations, the MySQL world is the place for you.
Posts today on open source DBMS
- Infobright’s smart move to open source
- General Infobright update
- Infobright sound bites
- The many faces of open source DBMS
| Categories: Data warehousing, Infobright, MySQL, Open source | 3 Comments |
Top DBMS on Linux
I was looking up George Crump’s blogs in connection with his recent post on SSDs, and I stumbled upon one that outlines at great length what features Linux backup systems should have. I won’t claim to have read it word for word, but what did catch my eye were a couple of comments on DBMS market share, which boiled down to:
- Oracle
- MySQL
- PostgreSQL
| Categories: IBM and DB2, Market share and customer counts, MySQL, Oracle, PostgreSQL | Leave a Comment |
Sun’s Rock chip is going to revolutionize OLTP? Yeah, right.
Ted Dziuba offers a profane and passionate screed to the effect that it would be really, really wonderful if Sun’s forthcoming Rock chip magically revolutionized OLTP. His idea — if I may dignify it with that term — seems to be that by solving some programming issues in multithreading, Sun will achieve orders of magnitude performance improvements in DBMS processing, with MySQL as the beneficiary.
Frankly, I don’t know what in the world Dziuba is talking about, and I strongly suspect that neither does he. Wikipedia wasn’t terribly enlightening, except to point out that some of the ideas originated with Tom Knight, which is encouraging. Ars Technica has a decent article about the Rock chip, but it’s hard to find support for Dziuba’s enthusiasm in their more sober discussion.
| Categories: MySQL, OLTP | 4 Comments |
Microsoft is buying DATAllegro
I’ve long argued that:
- Oracle and Microsoft are doomed in the data warehouse market unless they acquire MPP/shared-nothing data warehouse DBMS and/or data warehouse appliances.
- DATAllegro is the ideal acquisition for either of them.
Microsoft has now validated my claim by agreeing to buy DATAllegro. As you probably know, we’ve been covering DATAllegro extensively, as per the links listed below.
Basic deal highlights include: Read more
Pushback on the PostgreSQL vs. MySQL comparison
It should come as no surprise that not everybody agrees with EnterpriseDB’s views on the PostgreSQL/MySQL comparison. In particular, the High Availability MySQL blog offers a detailed rebuttal post, with more in the comment thread. According to MySQL fans, EnterpriseDB got its facts wrong on several matters regarding MySQL and InnoDB, especially in the areas of triggers and locking. And of course they disagree with EnterpriseDB’s general conclusion. 🙂
| Categories: MySQL, Open source, PostgreSQL | Leave a Comment |
How is MySQL’s join performance these days?
In a comment thread on a recent post comparing MySQL to Postgres, Jonathon Moore chimed in based on experience with both products. His characterization of some MySQL problems: Read more
| Categories: Infobright, MySQL, Open source | 8 Comments |
PostgreSQL vs. MySQL, as per EnterpriseDB
EnterpriseDB put out a white paper arguing for the superiority of PostgreSQL over MySQL, even without EnterpriseDB’s own Postgres Plus extensions. Highlights of EnterpriseDB’s opinion include:
- EnterpriseDB asserts that MyISAM is the only MySQL storage engine with decent performance.
- EnterpriseDB then bashes MyISAM for all sorts of well-deserved reasons, especially ACID-noncompliance.
- EnterpriseDB asserts that row-level triggers, lacking in MySQL but present in PostgreSQL, are the most important kind of trigger.
- EnterpriseDB claims PostgreSQL is superior in procedural language support to MySQL.
- EnterpriseDB claims PostgreSQL is superior in authentication support to MySQL.
| Categories: EnterpriseDB and Postgres Plus, Mid-range, MySQL, Open source, PostgreSQL | 17 Comments |
Unreliable web MySQL application (Technorati/WordPress)
Technorati yesterday exposed an application error, to wit (in what presumably should be a blog content region): Read more
| Categories: MySQL | 6 Comments |