<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Database machines and data warehouse appliances – the early days</title>
	<atom:link href="http://www.softwarememories.com/2008/09/15/database-machines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwarememories.com/2008/09/15/database-machines/</link>
	<description>History of software, by somebody who lived it</description>
	<lastBuildDate>Fri, 30 Jul 2010 14:36:06 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roger Reid</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-43890</link>
		<dc:creator>Roger Reid</dc:creator>
		<pubDate>Wed, 17 Feb 2010 21:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-43890</guid>
		<description>Following up months later - I can check the Z80XX chip, I have a Britton Lee CPU board back in my office.  (We were an early customer).

I keep it to show young folks what a &quot;patch&quot; is, since BL fixed often fixed bugs by adding a patch wire to the board.  That, and then I show them the memory expansion - a full megabyte of core in a 14&quot; square board.

Dunno why they call me gramps.

Roger Reid (who still misses QUEL, but loves 64GB caches)</description>
		<content:encoded><![CDATA[<p>Following up months later &#8211; I can check the Z80XX chip, I have a Britton Lee CPU board back in my office.  (We were an early customer).</p>
<p>I keep it to show young folks what a &#8220;patch&#8221; is, since BL fixed often fixed bugs by adding a patch wire to the board.  That, and then I show them the memory expansion &#8211; a full megabyte of core in a 14&#8243; square board.</p>
<p>Dunno why they call me gramps.</p>
<p>Roger Reid (who still misses QUEL, but loves 64GB caches)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gartner 2009/2010 Data Warehouse Magic Quadrant comments &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-43777</link>
		<dc:creator>Gartner 2009/2010 Data Warehouse Magic Quadrant comments &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Wed, 10 Feb 2010 23:29:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-43777</guid>
		<description>[...] Gartner correctly says that Teradata has been a data warehouse appliance vendor from the getgo. [...]</description>
		<content:encoded><![CDATA[<p>[...] Gartner correctly says that Teradata has been a data warehouse appliance vendor from the getgo. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Robertson</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-43380</link>
		<dc:creator>Bill Robertson</dc:creator>
		<pubDate>Thu, 28 Jan 2010 05:18:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-43380</guid>
		<description>&quot;...with each parent node talking to two children, until it got down to the lowest-level nodes that actually talked to disk. (This is what was called Ynet.) The architecture meant that almost exactly half the microprocessors talked to disk...&quot;

This isn&#039;t quite right. The &quot;tree structure&quot; of the YNet (to the extent that description is correct - it&#039;s arguable) had absolutely nothing to do with which processors could access disks or the ratio of processor types.

There were two types of processor types: AMPs (Access Module Processors) and IFPs (InterFace Processors). All AMPs had disks and all IFPs were diskless. One could have as few as one IFP with as many AMPs as your checkbook could buy - not that one would likely do that for fault tolerance reasons if nothing else.

There was a restriction that the number of IFPs couldn&#039;t exceed the number of AMPs (as each IFP needed a &quot;buddy AMP&quot;). However, for a large real world system, anything close to a 1:1 ratio would have likely been irrational anyway.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;with each parent node talking to two children, until it got down to the lowest-level nodes that actually talked to disk. (This is what was called Ynet.) The architecture meant that almost exactly half the microprocessors talked to disk&#8230;&#8221;</p>
<p>This isn&#8217;t quite right. The &#8220;tree structure&#8221; of the YNet (to the extent that description is correct &#8211; it&#8217;s arguable) had absolutely nothing to do with which processors could access disks or the ratio of processor types.</p>
<p>There were two types of processor types: AMPs (Access Module Processors) and IFPs (InterFace Processors). All AMPs had disks and all IFPs were diskless. One could have as few as one IFP with as many AMPs as your checkbook could buy &#8211; not that one would likely do that for fault tolerance reasons if nothing else.</p>
<p>There was a restriction that the number of IFPs couldn&#8217;t exceed the number of AMPs (as each IFP needed a &#8220;buddy AMP&#8221;). However, for a large real world system, anything close to a 1:1 ratio would have likely been irrational anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Forrest</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-42532</link>
		<dc:creator>Jon Forrest</dc:creator>
		<pubDate>Sat, 12 Dec 2009 04:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-42532</guid>
		<description>If I remember correctly, Britton-Lee&#039;s database machine used Z8000s, not Z80s.</description>
		<content:encoded><![CDATA[<p>If I remember correctly, Britton-Lee&#8217;s database machine used Z8000s, not Z80s.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-31416</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Wed, 17 Sep 2008 22:41:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-31416</guid>
		<description>Andrew,

Thanks for the corrections!

CAM</description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>Thanks for the corrections!</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew McLaren</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-31384</link>
		<dc:creator>Andrew McLaren</dc:creator>
		<pubDate>Wed, 17 Sep 2008 05:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-31384</guid>
		<description>CAFS - the ICL product was called CAFS: &quot;Content Addressable File Store&quot;. Yeah, it was one of those early ideas where the structure of the data and the structure of the hardware was closely aligned, like database machines. ICL won the Queen&#039;s Award for Technological Achievement for developing CAFS, sometime in the early 80s - and few other computer firms can claim a Queen&#039;s Award :-)

IDMS was a popular DB in ICL systems but I don&#039;t think CAFS was in any way directly derivative of IDMS.</description>
		<content:encoded><![CDATA[<p>CAFS &#8211; the ICL product was called CAFS: &#8220;Content Addressable File Store&#8221;. Yeah, it was one of those early ideas where the structure of the data and the structure of the hardware was closely aligned, like database machines. ICL won the Queen&#8217;s Award for Technological Achievement for developing CAFS, sometime in the early 80s &#8211; and few other computer firms can claim a Queen&#8217;s Award <img src='http://www.softwarememories.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>IDMS was a popular DB in ICL systems but I don&#8217;t think CAFS was in any way directly derivative of IDMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teradata decides to compete head-on as a data warehouse appliance vendor &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.softwarememories.com/2008/09/15/database-machines/#comment-31324</link>
		<dc:creator>Teradata decides to compete head-on as a data warehouse appliance vendor &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Mon, 15 Sep 2008 17:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwarememories.com/?p=34#comment-31324</guid>
		<description>[...] Teradata, which long avoided the “appliance” term, now says it sells both “data warehouse appliances” and “data mart appliances.” Indeed, it claims to have “invented the original appliance” &#8212; which is pretty close to being true.* [...]</description>
		<content:encoded><![CDATA[<p>[...] Teradata, which long avoided the “appliance” term, now says it sells both “data warehouse appliances” and “data mart appliances.” Indeed, it claims to have “invented the original appliance” &#8212; which is pretty close to being true.* [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
