<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: White paper on memory-centric data management &#8212; excerpt</title>
	<atom:link href="http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Sun, 20 Jul 2008 14:03:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Monash Report&#187;Blog Archive &#187; Flash drives as hard-drive replacements</title>
		<link>http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-15066</link>
		<dc:creator>The Monash Report&#187;Blog Archive &#187; Flash drives as hard-drive replacements</dc:creator>
		<pubDate>Fri, 05 Jan 2007 05:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-15066</guid>
		<description>[...] SanDisk is pushing a 32-gig flash disk that costs multiple hundreds of dollars more than a large hard drive. (Here&#8217;s The Register&#8217;s take on it.) One figure they cite is a 100-fold+ improvement in access speed. The speed difference between disk and silicon, of course, is something I&#8217;ve focused on in my research into memory-centric data management, and also in some of the work on data warehouse appliances as well. They are proposing this as the entire fixed memory for laptops. And in a much cheaper vein, Nicholas Negroponte is proposing a diskless architecture for the 100-dollar laptop. [...]</description>
		<content:encoded><![CDATA[<p>[...] SanDisk is pushing a 32-gig flash disk that costs multiple hundreds of dollars more than a large hard drive. (Here&#8217;s The Register&#8217;s take on it.) One figure they cite is a 100-fold+ improvement in access speed. The speed difference between disk and silicon, of course, is something I&#8217;ve focused on in my research into memory-centric data management, and also in some of the work on data warehouse appliances as well. They are proposing this as the entire fixed memory for laptops. And in a much cheaper vein, Nicholas Negroponte is proposing a diskless architecture for the 100-dollar laptop. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; SAP&#8217;s BI Accelerator</title>
		<link>http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-6771</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; SAP&#8217;s BI Accelerator</dc:creator>
		<pubDate>Thu, 21 Sep 2006 03:55:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-6771</guid>
		<description>[...] I wrote about SAP&#8217;s BI Accelerator quite a bit in my white paper on memory-centric data management, but otherwise I seem not to have posted much about it here. In essence, it&#8217;s a product that&#8217;s all RAM-based, and generally geared for multi-hundred-gigabyte data marts. The basic design is a compression-heavy column-based architecture, evolved from SAP&#8217;s text-indexing technology TREX. Like data warehouse appliances, it eschews indexing, relying instead on blazingly fast table scans. I asked Lothar Schubert of SAP how BIA was doing in the market in its early going. This was his response: [...]</description>
		<content:encoded><![CDATA[<p>[...] I wrote about SAP&#8217;s BI Accelerator quite a bit in my white paper on memory-centric data management, but otherwise I seem not to have posted much about it here. In essence, it&#8217;s a product that&#8217;s all RAM-based, and generally geared for multi-hundred-gigabyte data marts. The basic design is a compression-heavy column-based architecture, evolved from SAP&#8217;s text-indexing technology TREX. Like data warehouse appliances, it eschews indexing, relying instead on blazingly fast table scans. I asked Lothar Schubert of SAP how BIA was doing in the market in its early going. This was his response: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Monash Report&#187;Blog Archive &#187; Burning issues in an analyst&#8217;s life</title>
		<link>http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-1545</link>
		<dc:creator>The Monash Report&#187;Blog Archive &#187; Burning issues in an analyst&#8217;s life</dc:creator>
		<pubDate>Fri, 19 May 2006 10:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2006/05/10/white-paper-on-memory-centric-data-management-excerpt/#comment-1545</guid>
		<description>[...] So anyway, I visited Intersystems today, at the insistance of PR lady Rita Shoor, even though it seemed a phone call would have sufficed. Notwithstanding that this was a relatively longstanding meeting, Linda scheduled a dinner for us in Cambridge with my stepdaughter, which is basically good, because Intersystems is in Cambridge, but forgot about my meeting, and wound up scheduling the dinner for 9:30. Rescheduling ensued, but when I drove to Intersystems for a 2:30 meeting, it was still in flux. I was in an odd state anyway driving to the meeting, because I was already rather tired (my sleep schedule oddities), but psyched from having FINALLY posted the white paper online that represented my biggest writing project in almost a decade (because of the number of sponsors). [...]</description>
		<content:encoded><![CDATA[<p>[...] So anyway, I visited Intersystems today, at the insistance of PR lady Rita Shoor, even though it seemed a phone call would have sufficed. Notwithstanding that this was a relatively longstanding meeting, Linda scheduled a dinner for us in Cambridge with my stepdaughter, which is basically good, because Intersystems is in Cambridge, but forgot about my meeting, and wound up scheduling the dinner for 9:30. Rescheduling ensued, but when I drove to Intersystems for a 2:30 meeting, it was still in flux. I was in an odd state anyway driving to the meeting, because I was already rather tired (my sleep schedule oddities), but psyched from having FINALLY posted the white paper online that represented my biggest writing project in almost a decade (because of the number of sponsors). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
