February 6, 2009

Final (for now) slides on how to select a data warehouse DBMS

I’ve now posted a final version of the slide deck* I first posted Wednesday.  And I do mean final; TDWI likes its slide decks locked down weeks in advance, because they go to the printer to be memorialized on dead trees.  I added or fleshed out notes on quite a few slides vs. the prior draft. Actual changes to the slides themselves, however, were pretty sparse, and mainly were based on comments to the prior post.  Thanks for all the help!

*That’s a new URL.  The old deck is still up too, for those morbidly curious as to what I did or didn’t change.

Comments

14 Responses to “Final (for now) slides on how to select a data warehouse DBMS”

  1. Draft slides on how to select an analytic DBMS | DBMS2 -- DataBase Management System Services on February 6th, 2009 9:16 am

    […] The slides have now been finalized. Share: These icons link to social bookmarking sites where readers can share and discover new web […]

  2. Hellena Smejda on February 8th, 2009 9:02 pm

    Hi, Curt — Did you change the name of this powerpoint presentation? Is it how to select an analytic DBMS or a data warehouse DBMS. Are they interchangeable? — Hellena

  3. Curt Monash on February 9th, 2009 10:08 am

    The title is what it is on the first page of the presentation. :)

    But I tend to use the terms “analytic DBMS” and “data warehouse DBMS” pretty interchangeably, especially when focusing — as I usually do — on terabyte+ scales.

  4. Jos van Dongen on February 9th, 2009 1:15 pm

    Hi Curt,

    It’s great you put in MonetDB in the example columnar DBMS examples. I missed LucidDB though, that’s the other open source columnar contender. If you’re interested, there are some bechmarks (and references to others) on my website; I’m currently working on a TPC-H sf 10/100 comparison between MonetDB, LucidDB and Infobright.

  5. Curt Monash on February 9th, 2009 4:19 pm

    I can’t get everything in there.

    MonetDB comes up a bit more than LucidDB in my life, although the sample size is so small I wouldn’t attach much importance to that.

  6. Leandro Tubia on February 19th, 2009 5:10 am

    Hi
    Your presentation is really brilliant and specially usefull for me that sometimes I’m in the vendor side and others in the customer side.
    I would add two important tests:
    1) Recovery behavior: test how DB recover from network microcuts or other unwanted services interrumption scenarios. In standard OLTP databases recovery process could last hours or days till transaction log is fully roll backed. I don’t know who much memory centric DBs or column based ones, lasts to recover after restarting.
    2) Interoperability with other DBs: it’s usual that new technologies are not deployed solely within the current customer architecture, as different steps of migration projects could obligue to face a temporal scenario of distributed queries among different technologies. But connecivity tests are not enough to assure that products can interoperate: real queries must be tested so as to get sure connectivity is stable enough. I’ve got very surprised when I’ve found that sometimes client providers failed solving queries with certain complexity.
    Thanks

  7. Curt Monash on February 19th, 2009 6:16 am

    Leandro,

    Thanks for commenting, especially with the nice compliments!

    #1 sounds like the “baseball bat test” I talk about.

    #2 I’m inclined to disagree with. I think federated queries are evil, and would rather see data recopied in most scenarios.

  8. Even more final version of my TDWI slide deck | DBMS2 -- DataBase Management System Services on February 25th, 2009 9:09 pm

    […] in less than an hour.  So the latest version of my slide deck should prove truly final, unlike my prior […]

  9. 37 Ways To Get More From Analytics | DBMS2 -- DataBase Management System Services on April 29th, 2009 4:26 am

    […] posted several stages of my thinking in connection with a February presentation on how to buy an analytic DBMS. The whole process seemed like a success, with good input early on, and at least one new client […]

  10. Ed Bernier on September 4th, 2009 8:42 pm

    On your slide: “General areas of differentiation” you missed one very important one – “Out of the box performance”. The simplicity side of appliances is sorely lacking in some architectures and this is what drives agility. The ability to support totally unpredictable queries with no indexes required. Netezza is the only vendor to date that doesn’t require indexes and requires minimal configuration.

  11. Ziadul Huq on August 15th, 2011 10:33 am

    Greenplum is a Columnar DBMS, it also support row-base table.

  12. Curt Monash on August 15th, 2011 1:58 pm

    Are they saying that now when selling? It’s not really true.

    http://www.dbms2.com/2009/10/14/greenplum-hybrid-columnar/ has more.

  13. Tariq on September 14th, 2012 2:14 am

    Hi Curt, great presentation. I am actually trying to figure out which one is better for telecommunications data? Currently I have installed Infobright but now i hear that even Vertica is better. Its confusing.

  14. Curt Monash on September 14th, 2012 10:41 am

    Tariq,

    It would depend on your use case. Also, a number of these products are very good.

    Vertica’s two clearest advantages over Infobright are that it scales out further and that it has more analytic capabilities, especially via embedded analytics. If neither of those matters greatly to you, and you’re getting good performance from Infobright, why would you switch?

Leave a Reply




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.