<?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: Extreme Buzz About Oracle OpenWorld</title>
	<atom:link href="http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/feed/" rel="self" type="application/rss+xml" />
	<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/</link>
	<description>Oracle Database Performance And Scalability Blog</description>
	<lastBuildDate>Mon, 01 Mar 2010 22:11:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ghassan</title>
		<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/comment-page-1/#comment-255</link>
		<dc:creator>ghassan</dc:creator>
		<pubDate>Sun, 21 Sep 2008 17:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://structureddata.org/?p=75#comment-255</guid>
		<description>Brett,
TimesTen is not intended for DWH, so it is not easy to compare it to ParAcell or other such databases.
As for what Oracle will announce, well wait and see.</description>
		<content:encoded><![CDATA[<p>Brett,<br />
TimesTen is not intended for DWH, so it is not easy to compare it to ParAcell or other such databases.<br />
As for what Oracle will announce, well wait and see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Schroeder</title>
		<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/comment-page-1/#comment-258</link>
		<dc:creator>Brett Schroeder</dc:creator>
		<pubDate>Sat, 20 Sep 2008 22:32:33 +0000</pubDate>
		<guid isPermaLink="false">http://structureddata.org/?p=75#comment-258</guid>
		<description>Thanks for the paper reference.

Since Exasol, ParAcell etc are &quot;in-memory&quot; databases, then wouldn&#039;t a more realistic/fair comparison be against Oracle Times Ten DB (instead of 10g or 11g)?</description>
		<content:encoded><![CDATA[<p>Thanks for the paper reference.</p>
<p>Since Exasol, ParAcell etc are &#8220;in-memory&#8221; databases, then wouldn&#8217;t a more realistic/fair comparison be against Oracle Times Ten DB (instead of 10g or 11g)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Rahn</title>
		<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/comment-page-1/#comment-256</link>
		<dc:creator>Greg Rahn</dc:creator>
		<pubDate>Fri, 19 Sep 2008 18:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://structureddata.org/?p=75#comment-256</guid>
		<description>@Brett

Unfortunately I can not comment on speculation but I would like to add some thoughts with regards to the rest of your comments.

Vertica has not and can not run a TPC-H benchmark due to limitations of the current product.  In order to use Vertica, you must have a star schema and the TPC-H schema is not a star schema, it most closely resembles a 3NF model.  The reason for this is the Vertica query optimizer is very limited.  Some limitations of the current optimizer are that it does not support subqueries or IN lists.  It also does not support any of the &lt;a href=&quot;http://68.142.116.68/docs/cd/B28359_01/server.111/b28313/analysis.htm&quot; rel=&quot;nofollow&quot;&gt;analytic functions&lt;/a&gt; commonly found in BI/DW queries that Oracle does.

Vendors like ParAccel and Exasol have achieved top spots in the TPC-H 3TB scale factor and under by approaching the problem differently.  Their secret sauce is to have all the data in memory.  I don&#039;t think it takes a computer scientist to tell you that reading data from memory will be an order of magnitude faster than reading data from disk.  But what happens when they have to read data from disk?  I suspect the results are not nearly as stunning.

I would encourage you and others who think column store databases are superior to row stores for BI/DW workloads to look at Allison Holloway and David DeWitt&#039;s presentation from &lt;a href=&quot;https://www.cs.auckland.ac.nz/research/conferences/vldb08/index.php/VLDB_08&quot; rel=&quot;nofollow&quot;&gt;VLDB 2008&lt;/a&gt; which has an alternate title of &quot;&lt;a href=&quot;https://www.se.auckland.ac.nz/conferences/VLDB2008resources/presentations/papers/R39.ppt&quot; rel=&quot;nofollow&quot;&gt;Yet Another Row Store vs Column Store Paper&lt;/a&gt;&quot;.</description>
		<content:encoded><![CDATA[<p>@Brett</p>
<p>Unfortunately I can not comment on speculation but I would like to add some thoughts with regards to the rest of your comments.</p>
<p>Vertica has not and can not run a TPC-H benchmark due to limitations of the current product.  In order to use Vertica, you must have a star schema and the TPC-H schema is not a star schema, it most closely resembles a 3NF model.  The reason for this is the Vertica query optimizer is very limited.  Some limitations of the current optimizer are that it does not support subqueries or IN lists.  It also does not support any of the <a href="http://68.142.116.68/docs/cd/B28359_01/server.111/b28313/analysis.htm" rel="nofollow">analytic functions</a> commonly found in BI/DW queries that Oracle does.</p>
<p>Vendors like ParAccel and Exasol have achieved top spots in the TPC-H 3TB scale factor and under by approaching the problem differently.  Their secret sauce is to have all the data in memory.  I don&#8217;t think it takes a computer scientist to tell you that reading data from memory will be an order of magnitude faster than reading data from disk.  But what happens when they have to read data from disk?  I suspect the results are not nearly as stunning.</p>
<p>I would encourage you and others who think column store databases are superior to row stores for BI/DW workloads to look at Allison Holloway and David DeWitt&#8217;s presentation from <a href="https://www.cs.auckland.ac.nz/research/conferences/vldb08/index.php/VLDB_08" rel="nofollow">VLDB 2008</a> which has an alternate title of &#8220;<a href="https://www.se.auckland.ac.nz/conferences/VLDB2008resources/presentations/papers/R39.ppt" rel="nofollow">Yet Another Row Store vs Column Store Paper</a>&#8220;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chen Shapira</title>
		<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/comment-page-1/#comment-254</link>
		<dc:creator>Chen Shapira</dc:creator>
		<pubDate>Fri, 19 Sep 2008 17:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://structureddata.org/?p=75#comment-254</guid>
		<description>I took the bait. Originally I planned to attend Real World Performance Roundtable, but it was dropped in favor of Database Accelerator.

Poor Juan Loaiza - he&#039;ll be giving same presentation three times on Thursday!</description>
		<content:encoded><![CDATA[<p>I took the bait. Originally I planned to attend Real World Performance Roundtable, but it was dropped in favor of Database Accelerator.</p>
<p>Poor Juan Loaiza &#8211; he&#8217;ll be giving same presentation three times on Thursday!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett Schroeder</title>
		<link>http://structureddata.org/2008/09/19/extreme-buzz-about-oracle-openworld/comment-page-1/#comment-257</link>
		<dc:creator>Brett Schroeder</dc:creator>
		<pubDate>Fri, 19 Sep 2008 14:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://structureddata.org/?p=75#comment-257</guid>
		<description>My guess is that Oracle will get column-store capability (great for DSS/DW, not so great for OLTP). Products like Vertica claim to beat Oracle on (unaudited) TPCH by factors of 10-100 in query time. All the major RDBMS&#039;s vendors are lagging new products like Vertica, Exasol, Netezza, Kickfire etc in warehouse performance. Consider these results for TPCH @ 1TB: Oracle on Solaris = 119,000 QphH and costs $24/QphH while an Exasol product = 1,000,000 QphH and costs $1/QphH....that&#039;s 10X faster and 24X cheaper. Granted, Oracle does a lot of things these products don&#039;t do but numbers like that force any company to think long and hard about buying more Oracle licenses.

Column store is something that Oracle can code up relatively quickly. In addition, Kevin Closson wrote several times about these new data warehouse products and column-store, then went awfully quiet on his blog :-) I suspect he&#039;s had his head down coding and/or testing this column-store feature.</description>
		<content:encoded><![CDATA[<p>My guess is that Oracle will get column-store capability (great for DSS/DW, not so great for OLTP). Products like Vertica claim to beat Oracle on (unaudited) TPCH by factors of 10-100 in query time. All the major RDBMS&#8217;s vendors are lagging new products like Vertica, Exasol, Netezza, Kickfire etc in warehouse performance. Consider these results for TPCH @ 1TB: Oracle on Solaris = 119,000 QphH and costs $24/QphH while an Exasol product = 1,000,000 QphH and costs $1/QphH&#8230;.that&#8217;s 10X faster and 24X cheaper. Granted, Oracle does a lot of things these products don&#8217;t do but numbers like that force any company to think long and hard about buying more Oracle licenses.</p>
<p>Column store is something that Oracle can code up relatively quickly. In addition, Kevin Closson wrote several times about these new data warehouse products and column-store, then went awfully quiet on his blog :-) I suspect he&#8217;s had his head down coding and/or testing this column-store feature.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
