How DBMS Vendors Admit to an Architectural Limitation: Part 2 – Teradata Intelligent Memory

This is the second post (see Part 1 here) on how vendors adjust their architecture without admitting that the previous architecture was flawed. This time we’ll consider Teradata and in-memory…. When SAP HANA appeared Teradata went on the warpath with a series of posts and statements that were pointed but oddly miscued (see the references below).…

HANA, BLU, Hekaton, and Oracle 12c vs. Teradata and Greenplum – November 2013

I would like to point out a very important section in the paper on Hekaton on the Microsoft Research site here. I will quote the section in total: 2. DESIGN CONSIDERATIONS  An analysis done early on in the project drove home the fact that a 10-100X throughput improvement cannot be achieved by optimizing existing SQL…

BLU Meanies: Data In-memory

IBM is presenting a DB2 Tech Talk that compares the BLU Accelerator to HANA. There are several mistakes and some odd thinking in the pitch so let me address the issues as a way to explain some things about HANA and about BLU. This blog will consider what data needs to be in-memory. IBM like…

The Fog is Getting Thicker…

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…