<?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: Data warehouse storage options &#8212; cheap, expensive, or solid-state disk drives</title>
	<atom:link href="http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Thu, 09 Feb 2012 21:52:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-219661</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sun, 24 Apr 2011 16:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-219661</guid>
		<description>I think you&#039;d do best to check with Sybase on that. Prices change too often for me to have that memorized.

On the plus side, they often have fairly clear web pages with their list pricing.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;d do best to check with Sybase on that. Prices change too often for me to have that memorized.</p>
<p>On the plus side, they often have fairly clear web pages with their list pricing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sai</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-219658</link>
		<dc:creator>sai</dc:creator>
		<pubDate>Sun, 24 Apr 2011 16:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-219658</guid>
		<description>Dear all,

Does anybody know what is the cost of additional storage of 1 TB added to an existing Warehouse.  My client company is having SYbase IQ Datawarehouse, and I&#039;m just curious to know what would be the incremental cost of 1TB, coz they might add upto 3.

Regards,

Sai.</description>
		<content:encoded><![CDATA[<p>Dear all,</p>
<p>Does anybody know what is the cost of additional storage of 1 TB added to an existing Warehouse.  My client company is having SYbase IQ Datawarehouse, and I&#8217;m just curious to know what would be the incremental cost of 1TB, coz they might add upto 3.</p>
<p>Regards,</p>
<p>Sai.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eBay followup &#8212; Greenplum out, Teradata &#62; 10 petabytes, Hadoop has some value, and more &#124; DBMS 2 : DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-186898</link>
		<dc:creator>eBay followup &#8212; Greenplum out, Teradata &#62; 10 petabytes, Hadoop has some value, and more &#124; DBMS 2 : DataBase Management System Services</dc:creator>
		<pubDate>Sat, 09 Oct 2010 14:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-186898</guid>
		<description>[...] Teradata and Greenplum, Oliver previously indicated he was inclined to attribute this more to specific Sun Thumper hardware/storage choices than to [...]</description>
		<content:encoded><![CDATA[<p>[...] Teradata and Greenplum, Oliver previously indicated he was inclined to attribute this more to specific Sun Thumper hardware/storage choices than to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Sampson</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-167713</link>
		<dc:creator>Curt Sampson</dc:creator>
		<pubDate>Sat, 08 May 2010 06:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-167713</guid>
		<description>Or someone can just go write a sensible DBMS that doesn&#039;t force you to link the logical format with the physical. There&#039;s no reason that several normalized relations can&#039;t be stored as a single denormalized table on disk, if that happens to be best for the query load. Column-oriented systems are an example of a different storage method under a relational front-end, though they suffer just as badly from not being able to store things in a row-oriented manner when that makes more sense.</description>
		<content:encoded><![CDATA[<p>Or someone can just go write a sensible DBMS that doesn&#8217;t force you to link the logical format with the physical. There&#8217;s no reason that several normalized relations can&#8217;t be stored as a single denormalized table on disk, if that happens to be best for the query load. Column-oriented systems are an example of a different storage method under a relational front-end, though they suffer just as badly from not being able to store things in a row-oriented manner when that makes more sense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Revisiting disk vibration as a data warehouse performance problem &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-167698</link>
		<dc:creator>Revisiting disk vibration as a data warehouse performance problem &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Sat, 08 May 2010 04:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-167698</guid>
		<description>[...] April, I wrote about the problems disk vibration can cause for data warehouse performance. Possible performance hits exceeded 10X, wild as that [...]</description>
		<content:encoded><![CDATA[<p>[...] April, I wrote about the problems disk vibration can cause for data warehouse performance. Possible performance hits exceeded 10X, wild as that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-121147</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Tue, 12 May 2009 14:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-121147</guid>
		<description>Robert,

I understand the appeal of saying something like &quot;The reason we need to be aware of physical design is largely complex query performance. Complex query performance is an issue mainly because of I/O. If we have better storage technology, that problem goes away, and we can start ignoring physical design the way the theorists have always wanted us to.&quot;

But I think we&#039;re a long way from reaching that ideal, at best.  Data warehouses are BIG, and getting bigger.  They&#039;ll push the limits of hardware technology for a long time to come.</description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>I understand the appeal of saying something like &#8220;The reason we need to be aware of physical design is largely complex query performance. Complex query performance is an issue mainly because of I/O. If we have better storage technology, that problem goes away, and we can start ignoring physical design the way the theorists have always wanted us to.&#8221;</p>
<p>But I think we&#8217;re a long way from reaching that ideal, at best.  Data warehouses are BIG, and getting bigger.  They&#8217;ll push the limits of hardware technology for a long time to come.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Young</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-121137</link>
		<dc:creator>Robert Young</dc:creator>
		<pubDate>Tue, 12 May 2009 12:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-121137</guid>
		<description>Check Andandtech for reviews of SSD.  The latest is from 20 March 2009.  Deals explicitly with some of the issues here.  An earlier review dealt with the &quot;block&quot; write versus read.

The value of SSD is not going to be in highly redundant, flat-file (called whatever you want) style datastores; price will be too high.  The value will be in high NF relational databases.  Now, in my opinion (which you can read, and I am not alone), SSD will be the motivator that merges back OLTP with its various replicants.  SSD, and the flash versions (both MLC and SLC) are only the latest low-end implementations (check Texas Memory Systems for one example of industrial strength SSD), removes the join penalty from 3/4/5NF databases.  

The bottleneck will be in finding folks with enough smarts to embrace (again) Dr. Codd&#039;s vision.  The xml folk are not those kind of folk.  My candidate is Larry Ellison.  The reason is that the Oracle architecture, MVCC, is superior for OLTP (IBM finally just capitulated with entrpriseDB).  With SSD, he can use the Oracle database, appropriately normalized, to support both without stars and snowflakes.  A true one stop solution.</description>
		<content:encoded><![CDATA[<p>Check Andandtech for reviews of SSD.  The latest is from 20 March 2009.  Deals explicitly with some of the issues here.  An earlier review dealt with the &#8220;block&#8221; write versus read.</p>
<p>The value of SSD is not going to be in highly redundant, flat-file (called whatever you want) style datastores; price will be too high.  The value will be in high NF relational databases.  Now, in my opinion (which you can read, and I am not alone), SSD will be the motivator that merges back OLTP with its various replicants.  SSD, and the flash versions (both MLC and SLC) are only the latest low-end implementations (check Texas Memory Systems for one example of industrial strength SSD), removes the join penalty from 3/4/5NF databases.  </p>
<p>The bottleneck will be in finding folks with enough smarts to embrace (again) Dr. Codd&#8217;s vision.  The xml folk are not those kind of folk.  My candidate is Larry Ellison.  The reason is that the Oracle architecture, MVCC, is superior for OLTP (IBM finally just capitulated with entrpriseDB).  With SSD, he can use the Oracle database, appropriately normalized, to support both without stars and snowflakes.  A true one stop solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Callaghan</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-120317</link>
		<dc:creator>Mark Callaghan</dc:creator>
		<pubDate>Thu, 07 May 2009 05:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-120317</guid>
		<description>Curt,

I agree with you that workload has something to do with performance. Ignore the poor wording. I mean that you won&#039;t get 10X more MB/s or IOPs from 15k SAS versus 7200 RPM SATA. Teradata has done clever things with track aligned reads to optimize disk performance. I would much rather read about that.</description>
		<content:encoded><![CDATA[<p>Curt,</p>
<p>I agree with you that workload has something to do with performance. Ignore the poor wording. I mean that you won&#8217;t get 10X more MB/s or IOPs from 15k SAS versus 7200 RPM SATA. Teradata has done clever things with track aligned reads to optimize disk performance. I would much rather read about that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-119632</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sat, 02 May 2009 22:42:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-119632</guid>
		<description>Mark,

Maybe the eBay guys diagnosed their situation correctly and maybe they didn&#039;t, but I can&#039;t begin to fathom your basis for saying that workload has nothing to do with it.

CAM</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>Maybe the eBay guys diagnosed their situation correctly and maybe they didn&#8217;t, but I can&#8217;t begin to fathom your basis for saying that workload has nothing to do with it.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Callaghan</title>
		<link>http://www.dbms2.com/2009/04/28/data-warehouse-storage-options-cheap-expensive-or-solid-state-disk-drives/#comment-119585</link>
		<dc:creator>Mark Callaghan</dc:creator>
		<pubDate>Sat, 02 May 2009 13:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=768#comment-119585</guid>
		<description>@Michael - you are the first person to ever claim that a 15k enterprise-grade SAS disk can do 10x more IOPs than a 7200 RPM consumer-grade SATA disk. Congratulations.

@Curt - workload has nothing to do with it. Oliver has made a controversial claim with no substantiation. That is marketing and nothing else.</description>
		<content:encoded><![CDATA[<p>@Michael &#8211; you are the first person to ever claim that a 15k enterprise-grade SAS disk can do 10x more IOPs than a 7200 RPM consumer-grade SATA disk. Congratulations.</p>
<p>@Curt &#8211; workload has nothing to do with it. Oliver has made a controversial claim with no substantiation. That is marketing and nothing else.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

