<?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: Word of the day:  &#8220;Compression&#8221;</title>
	<atom:link href="http://www.dbms2.com/2007/03/16/data-warehouse-compression/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2007/03/16/data-warehouse-compression/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Sun, 20 Jul 2008 14:05:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Will database compression change the hardware game?</title>
		<link>http://www.dbms2.com/2007/03/16/data-warehouse-compression/#comment-23044</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Will database compression change the hardware game?</dc:creator>
		<pubDate>Sun, 25 Mar 2007 19:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/16/data-warehouse-compression/#comment-23044</guid>
		<description>[...] I&#8217;ve recently made a lot of posts about database compression. 3X or more compression is rapidly becoming standard; 5X+ is coming soon as processor power increases; 10X or more is not unrealistic. True, this applies mainly to data warehouses, but that&#8217;s where the big database growth is happening. And new kinds of data &#8212; geospatial, telemetry, document, video, whatever &#8212; are highly compressible as well. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve recently made a lot of posts about database compression. 3X or more compression is rapidly becoming standard; 5X+ is coming soon as processor power increases; 10X or more is not unrealistic. True, this applies mainly to data warehouses, but that&#8217;s where the big database growth is happening. And new kinds of data &#8212; geospatial, telemetry, document, video, whatever &#8212; are highly compressible as well. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Compression in columnar data stores</title>
		<link>http://www.dbms2.com/2007/03/16/data-warehouse-compression/#comment-22642</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services&#187;Blog Archive &#187; Compression in columnar data stores</dc:creator>
		<pubDate>Thu, 22 Mar 2007 04:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2007/03/16/data-warehouse-compression/#comment-22642</guid>
		<description>[...] column stores allow the processors to operate directly on compressed data. But once again, I don&#8217;t see why row stores can&#8217;t do that too. For example, when you join via bitmapped indices, exactly what you&#8217;re doing is operating on highly-compressed data.Want to continue getting great research about DBMS, analytics, and other technologies related to data management? Then subscribe to our feed, by RSS/Atom or e-mail! We recommend taking the integrated feed for all our blogs, but blog-specific ones are also easily available.       &#8226; &#8226; &#8226; [...]</description>
		<content:encoded><![CDATA[<p>[...] column stores allow the processors to operate directly on compressed data. But once again, I don&#8217;t see why row stores can&#8217;t do that too. For example, when you join via bitmapped indices, exactly what you&#8217;re doing is operating on highly-compressed data.Want to continue getting great research about DBMS, analytics, and other technologies related to data management? Then subscribe to our feed, by RSS/Atom or e-mail! We recommend taking the integrated feed for all our blogs, but blog-specific ones are also easily available.       &#8226; &#8226; &#8226; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
