February 8, 2012

Comments on the analytic DBMS industry and Gartner’s Magic Quadrant for same

This year’s Gartner Magic Quadrant for Data Warehouse Database Management Systems is out.* I shall now comment, just as I did on the 2010, 2009, 2008, 2007, and 2006 Gartner Data Warehouse Database Management System Magic Quadrants, to varying extents. To frame the discussion, let me start by saying:

*As of February, 2012 — and surely for many months thereafter — Teradata is graciously paying for a link to the report.

Specific company comments, roughly in line with Gartner’s rough single-dimensional rank ordering, include:


12 Responses to “Comments on the analytic DBMS industry and Gartner’s Magic Quadrant for same”

  1. Larry Dooley on February 8th, 2012 4:40 pm


    you didn’t include Microsoft. It’s in the challenger quadrant. Two things everyone overlooks about the low TOC for Microsoft (and I’ve been using MS products for well over 20 years) is first there is a ton of code you need to write. Second, is the Microsoft’s cavalier attitude to backward comparability. Code I wrote for Oracle 5-10 years ago still works (may need to update for better functionality but it works). Stuff I wrote 5-10 years ago for Microsoft is a crap shoot on whether it works or not.

  2. Curt Monash on February 8th, 2012 5:47 pm


    Look again; Microsoft is in there (it was sixth on Gartner’s “list”). 🙂

    Interesting comment on Microsoft backward compatibility. Do you have some specific examples to point to?

  3. Bob Riel on February 9th, 2012 4:48 pm

    You didn’t mention ParAccel. They seem to be still in the game and getting the job done w/o being acquired. Were they mentioned?

  4. Curt Monash on February 9th, 2012 4:52 pm


    Look again; I did mention ParAccel.

  5. ikke on February 10th, 2012 1:18 pm


    I was in London on the Gartner Bi summit where this was presented. I didn’t witness the end of this presentation but there is one very interesting point that was made there.

    Gartner is currently promoting the idea of an LDW (logical datawarehouse) which is compromised of multiple blocks of
    – a traditional structured DBMS (your old EDW)
    – big data systems
    – in memory DBMS
    all in one logical access point for your user. This LDW vision was not applied to this years MQ, but it will be influencing next years. So while this MQ is a non event since it’s mostly a copy of last year, next year might be a blast.

  6. unholyguy on February 10th, 2012 2:11 pm

    IMO the LDM thing is a good idea but it will be years before it actually works. It also remains to be seen whether it ends up being multiple blocks or just gets all sucked into the hadoop framework

  7. Curt Monash on February 10th, 2012 3:16 pm

    I left the whole LDW idea out of this post for two reasons:

    1. Length. Comments like those above — “You didn’t mention Subject X.” “Actually, I did.” — almost never happen on this blog; their presence in this case suggests the post overwhelmed people with length as it was.

    2. It’s a concept I’ve been writing about for years under different names, and I frankly don’t know the details of Gartner’s spin on it.

    That said, it’s certainly on my to-do list for a separate post.

  8. ikke on February 10th, 2012 5:29 pm


    The moment something new comes up the first remarks are always ‘ this will replace the old X’ . This has never proven true. Hadoop will compliment our current landscape and will live side-by-side with technology we’ve been using for some years now. (Gartners vision and also mine)
    Gartner also said that no current tech works for all the necessary cases here (LDW). But the moment they start using this as a measure in their MQ’s it put’s more focus there for some companies


    I can’t share the slides we recieved from Gartner, but in short it’s a virtual layer so users connect to one evironment. Behind this the right tech is choosen for the individual usecase.(in-memory,big-data,appliance,columnar,… whatever you need)

  9. unholyguy on February 10th, 2012 5:59 pm

    Remember hadoop is a framework not a software product. Multiple pieces of software can and do connect to data and eachother via the hadoop api tiers. It’s better to think of it as a big mainframe then a database

    The advantage of making mpp databases speak hadoop and use hdfs as an underlying data store is pretty significant, as it eliminates the need to ship the data around. It doesn’t mean you don’t still have separate systems or that hadoop replaces anything, it’s just the level of interconnect, do they talk over the network and ship data or do they talk api and share data?

  10. Curt Monash on February 10th, 2012 8:04 pm


    On that level of generality, it’s obviousness. But hey — kudos to Gartner for teaching “obvious” stuff to folks who actually may not have grasped it yet.

  11. VLDB Solutions » Gartner Magic Quadrant for Data Warehouse Database Management Systems on April 2nd, 2012 8:49 am

    […] Like many folk out there, I am as interested in what the industry analysts make of the report as the report itself. Curt Monash’s comments are here: http://www.dbms2.com/2012/02/08/gartner-magic-quadrant-data-warehouse-2011-2012/ […]

  12. Comments on Gartner’s 2012 Magic Quadrant for Data Warehouse Database Management Systems — concepts | DBMS 2 : DataBase Management System Services on February 5th, 2013 8:24 am

    […] also commented on the 2011, 2010, 2009, 2008, 2007, and 2006 Gartner Magic Quadrants for Data Warehouse […]

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:


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.