<?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: Spend Analysis Expectations</title>
	<atom:link href="http://www.esourcingforum.com/archives/2007/04/11/spend-analysis-expectations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.esourcingforum.com/archives/2007/04/11/spend-analysis-expectations/</link>
	<description>The source of information and best practices in strategic sourcing.</description>
	<pubDate>Tue, 02 Dec 2008 17:40:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Eric Strovink</title>
		<link>http://www.esourcingforum.com/archives/2007/04/11/spend-analysis-expectations/#comment-6942</link>
		<dc:creator>Eric Strovink</dc:creator>
		<pubDate>Wed, 11 Apr 2007 14:43:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.esourcingforum.com/?p=423#comment-6942</guid>
		<description>Ken's point is that it needs to be easy to create analysis datasets from the data sources lying around the enterprise.  It shouldn't be a big deal.  

So when a BIQ customer tells me (as one did just yesterday) that they have 24 datasets loaded on their server, and far more floating around the PC's of individual users -- of which only one is an A/P dataset -- that tells me the "ETL barrier" isn't much of an issue any more.  

That's the way things should be.</description>
		<content:encoded><![CDATA[<p>Ken&#8217;s point is that it needs to be easy to create analysis datasets from the data sources lying around the enterprise.  It shouldn&#8217;t be a big deal.  </p>
<p>So when a BIQ customer tells me (as one did just yesterday) that they have 24 datasets loaded on their server, and far more floating around the PC&#8217;s of individual users &#8212; of which only one is an A/P dataset &#8212; that tells me the &#8220;ETL barrier&#8221; isn&#8217;t much of an issue any more.  </p>
<p>That&#8217;s the way things should be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
