 




<?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: Exadata: At what price?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/eye-on-oracle/exadata-at-what-price/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/eye-on-oracle/exadata-at-what-price/</link>
	<description>A SearchOracle.com blog</description>
	<lastBuildDate>Thu, 24 Jan 2013 12:22:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Kevin Closson</title>
		<link>http://itknowledgeexchange.techtarget.com/eye-on-oracle/exadata-at-what-price/#comment-1375</link>
		<dc:creator>Kevin Closson</dc:creator>
		<pubDate>Wed, 15 Oct 2008 16:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://eyeonoracle.blogs.techtarget.com/2008/10/15/exadata-at-what-price/#comment-1375</guid>
		<description><![CDATA[&quot;[...text deleted...] because questions remain over what software needs to be purchased on the server side and how much data fits into an Exadata cell anyway.&quot;

  There cannot be any confusion over how much data fits in an Oracle Exadata Storage Cell. There are a fixed number of 12 disks and they are either 300GB SAS or 1000GB SATA. After performing the math for gross capacity, the deployment needs will reduce the value down based on specifics of the deployment such as mirroring (2-way, 3-way) and what percentage of the disk geometry to use for application data. A good rule of thumb is 60% of 2-way mirrored net capacity, or 1TB for the SAS option and 3.6TB for the SATA option. Certain applications will do just fine placing data over a greater percentage of the disks so the 1TB and 3.6TB values can adjust upward. 

  In the end, all of the disk capacity is usable. Varying from the rule-of-thumb 60% is application specific.]]></description>
		<content:encoded><![CDATA[<p>&#8220;[...text deleted...] because questions remain over what software needs to be purchased on the server side and how much data fits into an Exadata cell anyway.&#8221;</p>
<p>  There cannot be any confusion over how much data fits in an Oracle Exadata Storage Cell. There are a fixed number of 12 disks and they are either 300GB SAS or 1000GB SATA. After performing the math for gross capacity, the deployment needs will reduce the value down based on specifics of the deployment such as mirroring (2-way, 3-way) and what percentage of the disk geometry to use for application data. A good rule of thumb is 60% of 2-way mirrored net capacity, or 1TB for the SAS option and 3.6TB for the SATA option. Certain applications will do just fine placing data over a greater percentage of the disks so the 1TB and 3.6TB values can adjust upward. </p>
<p>  In the end, all of the disk capacity is usable. Varying from the rule-of-thumb 60% is application specific.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
