<?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: The core of the Vertica story still seems to be compression</title>
	<atom:link href="http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Sun, 07 Mar 2010 17:35:54 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Some pushback from DATAllegro against the columnar argument &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/comment-page-1/#comment-93175</link>
		<dc:creator>Some pushback from DATAllegro against the columnar argument &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Wed, 06 Aug 2008 22:39:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/#comment-93175</guid>
		<description>[...] do most of that ourselves&#8221; line of argument, some of which I&#8217;ve summarized in a comment here. But he made two other interesting points as [...]</description>
		<content:encoded><![CDATA[<p>[...] do most of that ourselves&#8221; line of argument, some of which I&#8217;ve summarized in a comment here. But he made two other interesting points as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/comment-page-1/#comment-53232</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Wed, 19 Sep 2007 19:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/#comment-53232</guid>
		<description>Trackbacks on my blogs are a HUGE problem, both outgoing and incoming.  I&#039;m hoping that&#039;s a function of the weird Bulgarian Wordpress theme I&#039;m using, and will get fixed when I change the blogs&#039; look.  (Coming soon, but just when I got back my web designer went on a snorkeling vacation of her own! Glub, glub, glub. Smart woman!)

Even so, the Wordpress dashboard captured your incoming link.  So *I* knew you&#039;d linked, even if my readers didn&#039;t ...

Netezza would be the first to agree that their usage of the term &quot;materialized views&quot; is somewhat notstandard.  Indeed, just about every vendor has different terminology in the area.  E.g., so far as I can figure out, Teradata does have conventional materialized views, but calls them &quot;join indexes.&quot;  And there&#039;s some subtle difference between Oracle and IBM in the materialized view area, although I&#039;ve forgotten right now what it is.

CAM</description>
		<content:encoded><![CDATA[<p>Trackbacks on my blogs are a HUGE problem, both outgoing and incoming.  I&#8217;m hoping that&#8217;s a function of the weird Bulgarian Wordpress theme I&#8217;m using, and will get fixed when I change the blogs&#8217; look.  (Coming soon, but just when I got back my web designer went on a snorkeling vacation of her own! Glub, glub, glub. Smart woman!)</p>
<p>Even so, the Wordpress dashboard captured your incoming link.  So *I* knew you&#8217;d linked, even if my readers didn&#8217;t &#8230;</p>
<p>Netezza would be the first to agree that their usage of the term &#8220;materialized views&#8221; is somewhat notstandard.  Indeed, just about every vendor has different terminology in the area.  E.g., so far as I can figure out, Teradata does have conventional materialized views, but calls them &#8220;join indexes.&#8221;  And there&#8217;s some subtle difference between Oracle and IBM in the materialized view area, although I&#8217;ve forgotten right now what it is.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Briggs</title>
		<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/comment-page-1/#comment-53228</link>
		<dc:creator>Tom Briggs</dc:creator>
		<pubDate>Wed, 19 Sep 2007 18:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/#comment-53228</guid>
		<description>Heh, no I understand your opinions on MPP databases. :)  I interpreted your comments to mean that Oracle/MS could be competitive if they added similar features, which may not have been your intent.

I think that &quot;materialized views&quot; is a misnomer when used in the context of NZ - it feels (to me) much more like a column store than a materialized view.  Now that you reference the old post about vertical partitioning, however, NZ&#039;s MViews remind me even more of Kognitio&#039;s in-memory images than anything else.  So thanks for pointing that out.

I wrote a blog post of my own about that, actually, which links to this post, but for some reason trackbacks to your blog have never worked for me, so... you&#039;d have no way to know that. :)</description>
		<content:encoded><![CDATA[<p>Heh, no I understand your opinions on MPP databases. <img src='http://www.dbms2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   I interpreted your comments to mean that Oracle/MS could be competitive if they added similar features, which may not have been your intent.</p>
<p>I think that &#8220;materialized views&#8221; is a misnomer when used in the context of NZ &#8211; it feels (to me) much more like a column store than a materialized view.  Now that you reference the old post about vertical partitioning, however, NZ&#8217;s MViews remind me even more of Kognitio&#8217;s in-memory images than anything else.  So thanks for pointing that out.</p>
<p>I wrote a blog post of my own about that, actually, which links to this post, but for some reason trackbacks to your blog have never worked for me, so&#8230; you&#8217;d have no way to know that. <img src='http://www.dbms2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/comment-page-1/#comment-53168</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Wed, 19 Sep 2007 00:36:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/#comment-53168</guid>
		<description>Tom,

If you&#039;re saying that shared-nothing MPP is the way to go for high end data warehousing, I agree completely, and have said so many times. :)

As for Netezza&#039;s limited materialized view capability, which of course can be mimicked by other vendors&#039; fuller materialized view features -- I agree up to a point.  Materialized views and/or specialized indices (including bitmaps) can capture some of the benefits of a columnar architecture. But at this time &quot;some&quot; is the operative word.

DATAllegro&#039;s &lt;a href=&quot;http://www.dbms2.com/2007/03/19/datallegro-versus-vertica-columnar-systems/&quot; rel=&quot;nofollow&quot;&gt;vertical partitioning&lt;/a&gt; seems even a bit slicker than materialized views.  Netezza&#039;s zone maps have similar benefits.  But the Vertica guys do make a compelling case that a fully columnar architecture goes further than those row-based workarounds.

CAM</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>If you&#8217;re saying that shared-nothing MPP is the way to go for high end data warehousing, I agree completely, and have said so many times. <img src='http://www.dbms2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>As for Netezza&#8217;s limited materialized view capability, which of course can be mimicked by other vendors&#8217; fuller materialized view features &#8212; I agree up to a point.  Materialized views and/or specialized indices (including bitmaps) can capture some of the benefits of a columnar architecture. But at this time &#8220;some&#8221; is the operative word.</p>
<p>DATAllegro&#8217;s <a href="http://www.dbms2.com/2007/03/19/datallegro-versus-vertica-columnar-systems/"  rel="nofollow">vertical partitioning</a> seems even a bit slicker than materialized views.  Netezza&#8217;s zone maps have similar benefits.  But the Vertica guys do make a compelling case that a fully columnar architecture goes further than those row-based workarounds.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Briggs</title>
		<link>http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/comment-page-1/#comment-53144</link>
		<dc:creator>Tom Briggs</dc:creator>
		<pubDate>Tue, 18 Sep 2007 20:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/09/18/vertica-columnar-database-compression/#comment-53144</guid>
		<description>I think that Netezza&#039;s materialized view functionality does essentially what you suggest - duplicating certain columns from a table in an automatically maintained &quot;view&quot;.  I&#039;m not sure if they&#039;re compressed, but it&#039;s certainly an interesting parallel.

And while I could (eventually) see Oracle or MS doing something similar, I think the advantage that Vertica has is horizontal scalability.  Even Oracle RAC can&#039;t seriously compete, for BI purposes, with Netezza or Vertica, at least not for the same cost/performance.  As such I don&#039;t think that having the feature(s) you suggest would put them on par with NZ/VT performance-wise.  Simply having a similar feature may be enough for marketing purposes though.</description>
		<content:encoded><![CDATA[<p>I think that Netezza&#8217;s materialized view functionality does essentially what you suggest &#8211; duplicating certain columns from a table in an automatically maintained &#8220;view&#8221;.  I&#8217;m not sure if they&#8217;re compressed, but it&#8217;s certainly an interesting parallel.</p>
<p>And while I could (eventually) see Oracle or MS doing something similar, I think the advantage that Vertica has is horizontal scalability.  Even Oracle RAC can&#8217;t seriously compete, for BI purposes, with Netezza or Vertica, at least not for the same cost/performance.  As such I don&#8217;t think that having the feature(s) you suggest would put them on par with NZ/VT performance-wise.  Simply having a similar feature may be enough for marketing purposes though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.266 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-03-07 20:47:55 -->
