<?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: Database management system choices – relational data warehouse</title>
	<atom:link href="http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Sun, 20 Jul 2008 01:29:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-74010</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Thu, 21 Feb 2008 20:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-74010</guid>
		<description>John,

I'd missed that Teradata feature.  Thanks!

DATAllegro does "multi-temperature" in another way.  In essence, they let you put two different brands of disk in the same installation, one of which is cheaper/bigger/slower than the other.  Then they manage it all as a fairly seamless logical whole, as part of their grid strategy.

CAM</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>I&#8217;d missed that Teradata feature.  Thanks!</p>
<p>DATAllegro does &#8220;multi-temperature&#8221; in another way.  In essence, they let you put two different brands of disk in the same installation, one of which is cheaper/bigger/slower than the other.  Then they manage it all as a fairly seamless logical whole, as part of their grid strategy.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: john mc tighe</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73994</link>
		<dc:creator>john mc tighe</dc:creator>
		<pubDate>Thu, 21 Feb 2008 17:44:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73994</guid>
		<description>Hi Curt,

One nice feature that Teradata now offer is the ability to mix "hot" (frequently accessed) and "cold" (rarely accessed) data on the same disc spindles.
This gets around the limitations of disk reader speeds  vs increased density discs. 
If say only 20% of the data on a spindle is hot then it stands to reason that the data can be read from many spindles that bit quicker than trying to read all the hot data from fewer spindles.
Maybe other products have similar functionality...
BTW I currently work with SQL Server so I am not trying to promote TD ! Too expensive IMHO.

John</description>
		<content:encoded><![CDATA[<p>Hi Curt,</p>
<p>One nice feature that Teradata now offer is the ability to mix &#8220;hot&#8221; (frequently accessed) and &#8220;cold&#8221; (rarely accessed) data on the same disc spindles.<br />
This gets around the limitations of disk reader speeds  vs increased density discs.<br />
If say only 20% of the data on a spindle is hot then it stands to reason that the data can be read from many spindles that bit quicker than trying to read all the hot data from fewer spindles.<br />
Maybe other products have similar functionality&#8230;<br />
BTW I currently work with SQL Server so I am not trying to promote TD ! Too expensive IMHO.</p>
<p>John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73567</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Tue, 19 Feb 2008 17:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73567</guid>
		<description>Tom,

I haven't talked enough with Dataupia to make many &lt;em&gt;en passant&lt;/em&gt; comments about them.

E.g., I just caught an error in the bullet you commented on -- I had implied ParAccel's Oracle compatibility was already available, when in fact that's a "roadmap" item, with a vague delivery timeframe target that they freely admit isn't set in stone.  I knew enough to edit that, without hesitation. For Dataupia I wouldn't be as sure about what's real and what isn't.

CAM</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>I haven&#8217;t talked enough with Dataupia to make many <em>en passant</em> comments about them.</p>
<p>E.g., I just caught an error in the bullet you commented on &#8212; I had implied ParAccel&#8217;s Oracle compatibility was already available, when in fact that&#8217;s a &#8220;roadmap&#8221; item, with a vague delivery timeframe target that they freely admit isn&#8217;t set in stone.  I knew enough to edit that, without hesitation. For Dataupia I wouldn&#8217;t be as sure about what&#8217;s real and what isn&#8217;t.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Briggs</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73551</link>
		<dc:creator>Tom Briggs</dc:creator>
		<pubDate>Tue, 19 Feb 2008 15:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73551</guid>
		<description>Any reason you didn't mention Dataupia in the transparency/compatibility bullet?  That is their whole play, isn't it?</description>
		<content:encoded><![CDATA[<p>Any reason you didn&#8217;t mention Dataupia in the transparency/compatibility bullet?  That is their whole play, isn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73289</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Mon, 18 Feb 2008 07:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73289</guid>
		<description>Greg,

I've been an analyst since 1981, and I've always dealt with huge amounts of semi-confidential and only partly-verified info.  (My stock analyst years were at the beginning of that period, long before Reg FD.) A big part of an analyst's skill lies in figuring out what's actually for real.  

I'm usually right.  Not always, to be sure.  But usually.  At least about reading the current state of the market and technology.  Predictions are sometimes a different matter ...

Best,

CAM</description>
		<content:encoded><![CDATA[<p>Greg,</p>
<p>I&#8217;ve been an analyst since 1981, and I&#8217;ve always dealt with huge amounts of semi-confidential and only partly-verified info.  (My stock analyst years were at the beginning of that period, long before Reg FD.) A big part of an analyst&#8217;s skill lies in figuring out what&#8217;s actually for real.  </p>
<p>I&#8217;m usually right.  Not always, to be sure.  But usually.  At least about reading the current state of the market and technology.  Predictions are sometimes a different matter &#8230;</p>
<p>Best,</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Rahn</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73283</link>
		<dc:creator>Greg Rahn</dc:creator>
		<pubDate>Mon, 18 Feb 2008 07:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73283</guid>
		<description>Thanks for info.  I apologize if you think I want to argue - not the case at all.  The engineer in me just likes to see supporting evidence and some more details surrounding some of your statements.

Cheers.</description>
		<content:encoded><![CDATA[<p>Thanks for info.  I apologize if you think I want to argue - not the case at all.  The engineer in me just likes to see supporting evidence and some more details surrounding some of your statements.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73276</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Mon, 18 Feb 2008 05:37:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73276</guid>
		<description>User data = data.  Not work space. Not indexes. Not aggregate tables. Not disks used for mirroring.  Not the disk space savings from compression.  Just raw data.

http://www.dbms2.com/2006/09/28/expansion-ratio-data-warehouse-explosion/

As for naming the big databases -- I'm sorry.  Most of the info I get about particular users is under possible NDA, and I often don't bother checking what has or hasn't made it into press releases and the like.  However, I do know DATAllegro has a press release about a multihundred terabyte site.  Dataupia put out a release about a big user very recently.  (If memory serves, they called it 150 terabytes, but upon query from me said it was 120 Tb of user data. I haven't posted about it yet.)  eBay, which I just posted about, is not -- I'm pretty sure -- running its main warehouses on Oracle or SQL Server. If I get clarity for public consumption, I'll update accordingly.  Walmart has huge data warehouses, and is a long-time Teradata customer.  Ditto K-Mart pre-Sears-merger.  I posted about a 35 Tb Sun/Greenplum site where Oracle had been thrown out.  And so on.

If you really want to learn and not just argue, there are a lot of pointers out there. If nothing else, just take the obvious suspects for the largest warehouses, leave out whoever you think will be bewildering due to decentralized IT decision making or secrecy (hint: start that list with Amazon and the intelligence community), and start seeing who's known to be their vendor.

Have you even read my prior posts on these subjects?  There's a reasonably decent search capability on my sites.

CAM</description>
		<content:encoded><![CDATA[<p>User data = data.  Not work space. Not indexes. Not aggregate tables. Not disks used for mirroring.  Not the disk space savings from compression.  Just raw data.</p>
<p><a href="http://www.dbms2.com/2006/09/28/expansion-ratio-data-warehouse-explosion/"  rel="nofollow">http://www.dbms2.com/2006/09/28/expansion-ratio-data-warehouse-explosion/</a></p>
<p>As for naming the big databases &#8212; I&#8217;m sorry.  Most of the info I get about particular users is under possible NDA, and I often don&#8217;t bother checking what has or hasn&#8217;t made it into press releases and the like.  However, I do know DATAllegro has a press release about a multihundred terabyte site.  Dataupia put out a release about a big user very recently.  (If memory serves, they called it 150 terabytes, but upon query from me said it was 120 Tb of user data. I haven&#8217;t posted about it yet.)  eBay, which I just posted about, is not &#8212; I&#8217;m pretty sure &#8212; running its main warehouses on Oracle or SQL Server. If I get clarity for public consumption, I&#8217;ll update accordingly.  Walmart has huge data warehouses, and is a long-time Teradata customer.  Ditto K-Mart pre-Sears-merger.  I posted about a 35 Tb Sun/Greenplum site where Oracle had been thrown out.  And so on.</p>
<p>If you really want to learn and not just argue, there are a lot of pointers out there. If nothing else, just take the obvious suspects for the largest warehouses, leave out whoever you think will be bewildering due to decentralized IT decision making or secrecy (hint: start that list with Amazon and the intelligence community), and start seeing who&#8217;s known to be their vendor.</p>
<p>Have you even read my prior posts on these subjects?  There&#8217;s a reasonably decent search capability on my sites.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Rahn</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73247</link>
		<dc:creator>Greg Rahn</dc:creator>
		<pubDate>Mon, 18 Feb 2008 03:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73247</guid>
		<description>When there are documented references to your 100+ TB db claims, please share them.  I'm interested in the big data arena as I'm sure other readers are.

WRT "unnatural acts": I've never had to do this, nor heard of anyone who has, and would not see why it would need to be done.  Seems to me like a case of poor SQL writing skills rather than an Oracle product limitation.  If you have a test case I'd gladly look at it offline.

Can you give the definition that you use for "user data" and explain the difference between the Winter Corp definitions?
Why is this number 1/5 - 1/10 as much in Oracle data warehouses?  Is this ratio also applied to other data warehouse platforms?</description>
		<content:encoded><![CDATA[<p>When there are documented references to your 100+ TB db claims, please share them.  I&#8217;m interested in the big data arena as I&#8217;m sure other readers are.</p>
<p>WRT &#8220;unnatural acts&#8221;: I&#8217;ve never had to do this, nor heard of anyone who has, and would not see why it would need to be done.  Seems to me like a case of poor SQL writing skills rather than an Oracle product limitation.  If you have a test case I&#8217;d gladly look at it offline.</p>
<p>Can you give the definition that you use for &#8220;user data&#8221; and explain the difference between the Winter Corp definitions?<br />
Why is this number 1/5 - 1/10 as much in Oracle data warehouses?  Is this ratio also applied to other data warehouse platforms?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73209</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sun, 17 Feb 2008 23:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73209</guid>
		<description>And looking at your latest Winter Corp links -- what I and most other people call "user data" seems to be what they're calling "normalized data".  In Oracle data warehouses, that's commonly 1/5 - 1/10 as much as what Winter Corp calls "user data".

CAM</description>
		<content:encoded><![CDATA[<p>And looking at your latest Winter Corp links &#8212; what I and most other people call &#8220;user data&#8221; seems to be what they&#8217;re calling &#8220;normalized data&#8221;.  In Oracle data warehouses, that&#8217;s commonly 1/5 - 1/10 as much as what Winter Corp calls &#8220;user data&#8221;.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73206</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sun, 17 Feb 2008 23:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/15/specialty-data-warehouse-database-management/#comment-73206</guid>
		<description>Telling me -- unless under NDA -- constitutes making a claim public.

As for "unnatural acts" -- can you write the SQL one would think you can write, or do you have to union over the result sets from a partitioned set of tables to get your results?</description>
		<content:encoded><![CDATA[<p>Telling me &#8212; unless under NDA &#8212; constitutes making a claim public.</p>
<p>As for &#8220;unnatural acts&#8221; &#8212; can you write the SQL one would think you can write, or do you have to union over the result sets from a partitioned set of tables to get your results?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
