The Fog is Getting Thicker…

English: San Francisco in fog

San Francisco in fog (Photo credit: Wikipedia)

I renamed this so that Teradata folks would not get here so often… its not really about Intelligent Memory… just prompted by it. The post on Intelligent Memory is here. – Rob

Two quick comments on Teradata’s recent announcement of Intelligent Memory.

First… very very cool. More on this to come.

Next… life is going to become very hard for my readers and for bloggers in this space. The notion of an in-memory database is becoming rightfully blurred… as is the notion of column store.

Oracle blurs the concepts with words like “database in-memory” and “hybrid column compression” which is neither an in-memory database or a column store.

Teradata blurs the concept with a strong offering that uses DRAM as a block-IO device (like the old RAM-disks we used to configure on our PCs).

Teradata and Greenplum blur the idea of a column store by adding columnar tables over their row store database engines.

I’m not a fan of the double-speak… but the ability of companies to apply the 80/20 rule to stretch their architectures and glue on new advanced technologies is a good thing for consumers.

But it becomes very hard to distinguish the products now.

In future blogs I’ll try to point out differences… but we’ll have to go a little deeper into the Database Fog.

2 thoughts on “The Fog is Getting Thicker…

  1. What is HANA’s take on the hot vs. cold data? Is there any advantage in maintaining cold data on memory?

    First off, do you think we can clearly identify HOT/COLD data ?

    Like

    • Hi Sangram,

      Check out the important paper here (http://queue.acm.org/detail.cfm?id=1413264) for a basic definition of what should be in-memory. In short, this famous paper suggests that any data that is touched by any process within 90 minutes should be in-memory.

      A simpler, and very much related, view comes from Teradata who suggest that 90% of your DW queries hit 20% of your DW data… So this 20% of your data should be in-memory.

      Beyond this, you have to look for business justification. For example, if you are deploying BI to mobile devices where 3 second response or less is required… You may need to put at a in-memory to meet those service level requirements.

      Rob

      Like

Comments are closed.