<?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: Other notes on Oracle data warehousing</title>
	<atom:link href="http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Thu, 09 Feb 2012 16:57:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Initial reactions to IBM acquiring SPSS &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-133027</link>
		<dc:creator>Initial reactions to IBM acquiring SPSS &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Tue, 28 Jul 2009 17:34:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-133027</guid>
		<description>[...] notable point is that SPSS is more SQL-oriented than SAS. Thus, SPSS has gotten performance benefits from Oracle&#8217;s in-database data mining technology that SAS apparently [...]</description>
		<content:encoded><![CDATA[<p>[...] notable point is that SPSS is more SQL-oriented than SAS. Thus, SPSS has gotten performance benefits from Oracle&#8217;s in-database data mining technology that SAS apparently [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-104090</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Fri, 12 Dec 2008 16:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-104090</guid>
		<description>I&#039;m hoping MDX becomes a standard, I applaud
Oracle&#039;s 11G material cube approach but OLAP 
4GL is not as elegant as MDX.  MS analysis
services and reporting services can generate
full MDX queries you can tweak instead of 
writing entire statements from scratch.  Looking
for the next version of Essbase to do this.  
I believe the power of OLAP is drag n&#039; drop to
minimize coding along with all the data&#039;s permutations pre-indexed ( cube ).  I wonder are
there any OLAP appliances out there that are
specifically designed for just OLAP cubes....</description>
		<content:encoded><![CDATA[<p>I&#8217;m hoping MDX becomes a standard, I applaud<br />
Oracle&#8217;s 11G material cube approach but OLAP<br />
4GL is not as elegant as MDX.  MS analysis<br />
services and reporting services can generate<br />
full MDX queries you can tweak instead of<br />
writing entire statements from scratch.  Looking<br />
for the next version of Essbase to do this.<br />
I believe the power of OLAP is drag n&#8217; drop to<br />
minimize coding along with all the data&#8217;s permutations pre-indexed ( cube ).  I wonder are<br />
there any OLAP appliances out there that are<br />
specifically designed for just OLAP cubes&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sreeenivas</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-102954</link>
		<dc:creator>sreeenivas</dc:creator>
		<pubDate>Fri, 28 Nov 2008 10:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-102954</guid>
		<description>why we have to go to data ware housing</description>
		<content:encoded><![CDATA[<p>why we have to go to data ware housing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: okumu wilfred mayira</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-101894</link>
		<dc:creator>okumu wilfred mayira</dc:creator>
		<pubDate>Fri, 14 Nov 2008 11:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-101894</guid>
		<description>Some of the critical success factors which must considered and kept in the dataware house like the mission of the business. The duration of the business are missing.</description>
		<content:encoded><![CDATA[<p>Some of the critical success factors which must considered and kept in the dataware house like the mission of the business. The duration of the business are missing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-100191</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Wed, 22 Oct 2008 18:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-100191</guid>
		<description>Chris,

It sounds as if you buy into both halves of Ted Codd&#039;s original &quot;OLAP&quot; argument on behalf of Essbase:

1. Performance
2. Easier calculations

I share Richard&#039;s question -- which aspects of the metadata do you regard as particularly important?

Thanks,

CAM</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>It sounds as if you buy into both halves of Ted Codd&#8217;s original &#8220;OLAP&#8221; argument on behalf of Essbase:</p>
<p>1. Performance<br />
2. Easier calculations</p>
<p>I share Richard&#8217;s question &#8212; which aspects of the metadata do you regard as particularly important?</p>
<p>Thanks,</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Gowan</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-100158</link>
		<dc:creator>Richard Gowan</dc:creator>
		<pubDate>Wed, 22 Oct 2008 09:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-100158</guid>
		<description>Chris...can you clarify re this missing metadata?

It seems to me that in a traditional ROLAP situation, there is still metadata (rich or otherwise).  This information is entered into the BI tool - which keeps it in a &#039;stash&#039; somewhere.

It&#039;s this &#039;metadata stash&#039; that then allows the BI tool to translate business data requests into SQL.</description>
		<content:encoded><![CDATA[<p>Chris&#8230;can you clarify re this missing metadata?</p>
<p>It seems to me that in a traditional ROLAP situation, there is still metadata (rich or otherwise).  This information is entered into the BI tool &#8211; which keeps it in a &#8216;stash&#8217; somewhere.</p>
<p>It&#8217;s this &#8216;metadata stash&#8217; that then allows the BI tool to translate business data requests into SQL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Webb</title>
		<link>http://www.dbms2.com/2008/09/25/other-notes-on-oracle-data-warehousing/#comment-98198</link>
		<dc:creator>Chris Webb</dc:creator>
		<pubDate>Tue, 30 Sep 2008 14:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=573#comment-98198</guid>
		<description>I think you&#039;re missing at least half the point of OLAP here, and that&#039;s the half that explains why Oracle is apparently increasing its commitment to Essbase.

It&#039;s certainly true that one of the main drivers for adoption of &#039;disk-based OLAP&#039; is to improve query performance, and you&#039;re right that improving the performance of relational data warehouses will stop many people looking at OLAP in the first place. But OLAP is much more than raw performance for simple queries, it&#039;s a rich metadata layer over your data - and this rich metadata layer in turn enables you to express the kind of complex multidimensional calculations that are simply not feasible in SQL, and to be able to do these calculations quickly. This is what MDX calculations in Analysis Services allow you to do, and what Essbase calc scripts (among other features) do too. These types of calculations are especially important in financial applications, which are of course Essbase&#039;s traditional sweet spot, and building a high-performance multidimensional calculation engine that can handle everything a finance department can think up is by no means a trivial task. So if Oracle is indeed increasing its commitment to Essbase, it&#039;s probably in recognition of this fact.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re missing at least half the point of OLAP here, and that&#8217;s the half that explains why Oracle is apparently increasing its commitment to Essbase.</p>
<p>It&#8217;s certainly true that one of the main drivers for adoption of &#8216;disk-based OLAP&#8217; is to improve query performance, and you&#8217;re right that improving the performance of relational data warehouses will stop many people looking at OLAP in the first place. But OLAP is much more than raw performance for simple queries, it&#8217;s a rich metadata layer over your data &#8211; and this rich metadata layer in turn enables you to express the kind of complex multidimensional calculations that are simply not feasible in SQL, and to be able to do these calculations quickly. This is what MDX calculations in Analysis Services allow you to do, and what Essbase calc scripts (among other features) do too. These types of calculations are especially important in financial applications, which are of course Essbase&#8217;s traditional sweet spot, and building a high-performance multidimensional calculation engine that can handle everything a finance department can think up is by no means a trivial task. So if Oracle is indeed increasing its commitment to Essbase, it&#8217;s probably in recognition of this fact.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

