<?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: Arguments AGAINST data warehouse appliances</title>
	<atom:link href="http://www.dbms2.com/2007/01/23/arguments-against-data-warehouse-appliances/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2007/01/23/arguments-against-data-warehouse-appliances/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Fri, 08 Aug 2008 00:22:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: The Monash Report&#187;Blog Archive &#187; Guide to my recent research on computing appliances</title>
		<link>http://www.dbms2.com/2007/01/23/arguments-against-data-warehouse-appliances/#comment-16584</link>
		<dc:creator>The Monash Report&#187;Blog Archive &#187; Guide to my recent research on computing appliances</dc:creator>
		<pubDate>Sat, 27 Jan 2007 07:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/01/23/arguments-against-data-warehouse-appliances/#comment-16584</guid>
		<description>[...] Half or more of the computing appliance vendors I’ve looked into follow very similar hardware strategies: They use mainly standard parts; they include uncommon but off-the-shelf networking (and sometimes encryption) accelerators; and they of course optimize the mix of those parts and general hardware architecture as well.  (EDIT: I actually gave names to three strategies &#8212; even if they were just &#8220;Type 0&#8243;, &#8220;Type 1&#8243;, and &#8220;Type 2&#8243; &#8212; in this overview of data warehouse appliance vendors. And in another post I considered arguments about whether one would want a data warehouse appliance at all.)  Examples I’ve posted about recently include – and I quote the forthcoming column – “DATallegro and Teradata (data warehousing), Cast Iron Systems (data integration), Barracuda Networks (security/antispam), Blue Coat Systems (networking), and Juniper (security and networking).&#8221;  (ANOTHER EDIT:  But I think DATAllegro&#8217;s strategy has changed.) [...]</description>
		<content:encoded><![CDATA[<p>[...] Half or more of the computing appliance vendors I’ve looked into follow very similar hardware strategies: They use mainly standard parts; they include uncommon but off-the-shelf networking (and sometimes encryption) accelerators; and they of course optimize the mix of those parts and general hardware architecture as well.  (EDIT: I actually gave names to three strategies &#8212; even if they were just &#8220;Type 0&#8243;, &#8220;Type 1&#8243;, and &#8220;Type 2&#8243; &#8212; in this overview of data warehouse appliance vendors. And in another post I considered arguments about whether one would want a data warehouse appliance at all.)  Examples I’ve posted about recently include – and I quote the forthcoming column – “DATallegro and Teradata (data warehousing), Cast Iron Systems (data integration), Barracuda Networks (security/antispam), Blue Coat Systems (networking), and Juniper (security and networking).&#8221;  (ANOTHER EDIT:  But I think DATAllegro&#8217;s strategy has changed.) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
