DBMS product categories

Analysis of database management technology in specific product categories. Related subjects include:

February 23, 2007

Really big databases

Business Intelligence Lowdown has a well-dugg post listing what it claims are the 10 largest databases in the world. The accuracy leaves much to be desired, as is illustrated by the fact that #10 on the list is only 20 terabytes, while entirely unmentioned is eBay’s 2-petabyte database (mentioned here, and also here). Read more

February 21, 2007

If you can’t trust the storage vendors …

… isn’t that another reason to go with massively parallel systems?

StorageMojo has a great post on storage myth and reality.

Want to continue getting great research about DBMS, analytics, and other technologies related to data management? Then subscribe to our feed, by RSS/Atom or e-mail! We recommend taking the integrated feed for all our blogs, but blog-specific ones are also easily available.

January 31, 2007

MySQL IPO — not so fast

MySQL told Computer Business Review they’re thinking strongly of an IPO this year, but also wouldn’t mind waiting. Frankly, I think they shouldn’t come public until they can prove solid acceptance of Version 5, because Version 4 remains in too many ways an embarrassment.

Also, investors need a chance to see whether MySQL’s new enterprise all-you-can-eat pricing scheme is a success, both financially and in terms of service delivery.

January 27, 2007

EnterpriseDB’s Oracle clone — fact or fiction?

PostgreSQL-based EnterpriseDB is attracting a bit of attention. Philip Howard, as he does of most products, takes a favorable view. Seth Grimes regards the company as dirty, rotten liars. The company suggests that Everquest gameplay* runs on an RDBMS. I find this inherently implausible, and hence am starting out with a skeptical view of the company’s marketing messages.

*As in character movement. The idea that character inventory is stored in an RDBMS I find vastly more credible. Ditto other less volatile aspects of character state.

Read more

January 27, 2007

Data warehouse appliance hardware strategies

Recently, I’ve done extensive research into the hardware strategies of computing appliance vendors, across multiple functional areas. Data warehousing, firewall/unified threat management, antispam, data integration – you name it, I talked to them. Of course, each vendor has a unique twist. But some architectural groupings definitely emerged.

The most common approaches seem to be:

Type 1: Custom assembly from off-the-shelf parts. In this model, the only unusual (but still off-the-shelf) parts are usually in the area of network acceleration (or occasionally encryption). Also, the box may be balanced differently than standard systems, in terms of compute power and/or reliability.

Type 2 (Virtual): We don’t need no stinkin’ custom hardware. In this model, the only “appliancy” features are in the areas of easy deployment, custom operating systems, and/or preconfigured hardware.

And of course there are also appliances of Type 0: Custom hardware including proprietary ASICs or FPGAs.

Different markets had different emphases; e.g., firewall appliances are typically Type 1, while antispam devices cluster in Type 2. But the data warehouse appliance market is highly diverse, which maybe shouldn’t be a surprise. After all, the revenue market leader is non-appliance software vendor Oracle, while noisy upstart Netezza is famous for its FPGA. Read more

January 27, 2007

And then there were two: DATAllegro seems to be going with standard hardware

A while ago – for example, in a comment dated July 9, 2006 — CEO Stuart Frost of DATAllegro hinted that the company might port its software to commodity hardware before long. If this user story is to be believed, that has now happened. (Specific quote: “the Datallegro system is based on Dell and EMC hardware …”) Officially, the company is doing a Sgt. Schultz on the subject. But the evidence is pretty clear. Read more

January 23, 2007

Can MySQL scale?

Making the rounds of cyberspace is a report by MediaTemple, a hosting company, on how it believes it will solve its difficulties with grid-based MySQL hosting.

Takeaways include:

  1. MySQL has real issues with handling diverse, high-volume workloads.
  2. When MySQL gets overloaded, database corruption is routine.
  3. Some people write really, really bad MySQL web applications.

With the possible exception of #2, I doubt any of this surprises anybody.

January 23, 2007

Arguments AGAINST data warehouse appliances

Data warehouse appliance opponents like to argue that history is conclusively on their side. Database machine maker Britton-Lee, eventually bought by Teradata, fizzled. LISP machines were a spectacular failure. Rational Software’s origins as a special-purpose Ada machine maker had to be renounced before the company could succeed.

But the true story is more mixed. Teradata continues to this day as a major data warehouse technology player, and as far as I’m concerned Teradata indeed makes appliances. If we look further than the applications stack, we find that appliances actually occupy a large and growing share of the computing market. So a persuasive anti-appliance argument has to do more than just invoke the names of Britton-Lee and Symbolics.

I just ran across an article by MIT professor Samuel Madden that attempts to make such a case. And his MIT colleague Mike Stonebraker made similar arguments to me a few days ago. They are not wholly unbiased; indeed, both are involved in Vertica Systems. With that caveat, they have an interesting three-part argument:

Read more

November 11, 2006

Federation in the MySQL empire

Marten Micklos, CEO of MySQL, gave a recent speech speculating about a big federated “database in the sky,” providing all sorts of Web 2.0 benefits. Apparently, the idea isn’t at all fleshed out yet. Even so, I have a nagging suspicion he’s pointing in somewhat the wrong direction.

That’s because I think federating relational databases is a generically bad idea. You can federate sets of services, and you can generate services from relational databases – and that’s where DBMS2 (DataBase Management System Services) got its name. This is a superior approach to direct database federation, for two main reasons. (By “direct federation,” I mean some sort of structure in which there’s a giant virtual database whose schema more or less directly incorporates much of the schema of each individual database.)

Read more

October 5, 2006

Introduction to Kognitio WX-2

Kognitio called me for a briefing this morning on their WX-2 product. Technical highlights included:

Much like the other “new” MPP data warehouse vendors, Kognitio claims to never have knowingly been outbenchmarked, whether on performance or on TCO factors such as ease of installation.
Read more

← Previous PageNext Page →

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.