It is about Architecture… not about Marketing…

Menu

Tag Archives: SAP AG

This short post is intended to provide a quick warning regarding in-memory columnar and cpu requirements… with a longer post to follow. When a row is inserted or bulk-loaded into a DBMS, if there are no indexes, the amount of cpu required is very small. The majority of the time is spent committing a transaction…

As I noted here, I think that the IBM BLU Accelerator is a very nice piece of work. Readers of this blog are in the software business where any feature developed by any vendor can be developed in a relatively short period of time by any other vendor… and BLU certainly moves DB2 forward in…

I would like to recommend to you John Appleby’s post here on the HANA blog site. While the title suggests the article is about HANA, in fact it is about trends in computing and processors… and very relevant to posts here past, present, and upcoming… I would also recommend Curt Monash’s site. His notes on Teradata…

This post has been thrown at me a couple of times now… so I’ll now take the time to go through it… and try to address the junk. It starts by suggesting that “the Germans” have started a war… but the next sentence points out that the author tossed grenades at HANA two months before…

I posted a blog on the SAP site here that discussed the implications of mobile clients. I want to re-emphasize the issue as it is crucial. While at Greenplum we routinely replaced older EDW platforms and provided stunning performance. I recall one customer in particular where we were given a query that ran in 7…

When I was at Greenplum… and now again at SAP… I ran into a strange logic from Teradata about query concurrency. They claimed that query concurrency was a good thing and an indicator of excellent workload management. Let’s look at a simple picture of how that works. In Figure 1 we depict a single query…

I recently pointed out some silliness published by Teradata to several SAP prospects. There is more nonsense that was sent and I’d like to take a moment to clear up these additional claims. In their note to HANA prospects they used the following numbers from the paper SAP published here: # of Query Streams 1…