Comments on: Hasso Plattner calls for in-memory OLTP column stores http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/ Choices in data management and analysis Thu, 09 Feb 2012 16:57:09 +0000 hourly 1 http://wordpress.org/?v=3.0.3 By: Quick reactions to SAP acquiring Sybase | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/#comment-168162 Quick reactions to SAP acquiring Sybase | DBMS2 -- DataBase Management System Services Wed, 12 May 2010 23:54:56 +0000 http://www.dbms2.com/?p=834#comment-168162 [...] SAP’s thoughts on in-memory database management are interesting. However, I think SAP’s oft-repeated claim that it has a lot of important in-memory database technology to bring to Sybase (or for that matter SAP customers) is mainly smoke and mirrors. Cool data access methods, good niche database products, and broadly applicable multi-domain DBMS innovations are three different things. Granting that SAP probably has the first and thinks it has the second is not the same as giving it much credence for having the third. [...] [...] SAP’s thoughts on in-memory database management are interesting. However, I think SAP’s oft-repeated claim that it has a lot of important in-memory database technology to bring to Sybase (or for that matter SAP customers) is mainly smoke and mirrors. Cool data access methods, good niche database products, and broadly applicable multi-domain DBMS innovations are three different things. Granting that SAP probably has the first and thinks it has the second is not the same as giving it much credence for having the third. [...]

]]> By: Ray Wang on SAP | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/#comment-152390 Ray Wang on SAP | DBMS2 -- DataBase Management System Services Fri, 11 Dec 2009 23:17:29 +0000 http://www.dbms2.com/?p=834#comment-152390 [...] and Oracle’s (Fusion) efforts to meld memory-centric analytics with operational apps will be crucial for large enterprises — but perhaps only around the middle of the next [...] [...] and Oracle’s (Fusion) efforts to meld memory-centric analytics with operational apps will be crucial for large enterprises — but perhaps only around the middle of the next [...]

]]> By: joab jackson (joabj) 's status on Saturday, 18-Jul-09 13:36:58 UTC - Identi.ca http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/#comment-131252 joab jackson (joabj) 's status on Saturday, 18-Jul-09 13:36:58 UTC - Identi.ca Sat, 18 Jul 2009 13:37:00 +0000 http://www.dbms2.com/?p=834#comment-131252 [...] http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/ [...] [...] http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/ [...]

]]> By: Curt Monash http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/#comment-130285 Curt Monash Sat, 11 Jul 2009 21:18:48 +0000 http://www.dbms2.com/?p=834#comment-130285 Very different cases, Seth. Aggregates are updated every time a FACT changes. Dimension tables are updated every time a dimension changes. Very different cases, Seth. Aggregates are updated every time a FACT changes. Dimension tables are updated every time a dimension changes.

]]> By: Seth Grimes http://www.dbms2.com/2009/07/07/hasso-plattner-calls-for-in-memory-oltp-column-stores/#comment-130195 Seth Grimes Sat, 11 Jul 2009 11:49:05 +0000 http://www.dbms2.com/?p=834#comment-130195 Regarding the sensible argument: "columnar –> natively fast analytics –> no need to maintain aggregates –> much lower update burden" What about when, instead of aggregates, the columnar system needs to maintain software-managed *replicates* rather than aggregates? That's the Vertica situation. Seth Regarding the sensible argument:

“columnar –> natively fast analytics –> no need to maintain aggregates –> much lower update burden”

What about when, instead of aggregates, the columnar system needs to maintain software-managed *replicates* rather than aggregates? That’s the Vertica situation.

Seth

]]>