<?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: ParAccel pricing</title>
	<atom:link href="http://www.dbms2.com/2009/06/23/paraccel-pricing-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2009/06/23/paraccel-pricing-2/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Wed, 08 Feb 2012 22:51:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Yvonne Cook</title>
		<link>http://www.dbms2.com/2009/06/23/paraccel-pricing-2/#comment-255270</link>
		<dc:creator>Yvonne Cook</dc:creator>
		<pubDate>Sun, 30 Oct 2011 23:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=820#comment-255270</guid>
		<description>The only certain way to establish an accurate price and price/performance comparison is for the customer to run a competitive onsite POC based on the customers data and range of analysis and reporting workload, include data loading and transformation processes. 

Most Vendors are resistant to this because getting performance isn&#039;t easy for all vendors - this is highly visible in an onsite POC and so the true Total Cost of Ownership becomes the basis for the decision not a list price comparison per TB - which is as said above totally meaningless and a marketeers metric rather than a customer buying guideline. 

The customers who include the POC step in their buying cycle will be best positioned to understand for their requirements the best vendor to choose. The value of getting away from the corporate slides and into execution with the vendor before you buy adds to the safety of the vendor decision. Its also an excellent tool for the customers&#039; procurement team - to ensure they negotiate the total cost of ownership over 5 years aspects - often overlooked or underplayed by vendors during the evaluation. 

Hope this helps!</description>
		<content:encoded><![CDATA[<p>The only certain way to establish an accurate price and price/performance comparison is for the customer to run a competitive onsite POC based on the customers data and range of analysis and reporting workload, include data loading and transformation processes. </p>
<p>Most Vendors are resistant to this because getting performance isn&#8217;t easy for all vendors &#8211; this is highly visible in an onsite POC and so the true Total Cost of Ownership becomes the basis for the decision not a list price comparison per TB &#8211; which is as said above totally meaningless and a marketeers metric rather than a customer buying guideline. </p>
<p>The customers who include the POC step in their buying cycle will be best positioned to understand for their requirements the best vendor to choose. The value of getting away from the corporate slides and into execution with the vendor before you buy adds to the safety of the vendor decision. Its also an excellent tool for the customers&#8217; procurement team &#8211; to ensure they negotiate the total cost of ownership over 5 years aspects &#8211; often overlooked or underplayed by vendors during the evaluation. </p>
<p>Hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2009/06/23/paraccel-pricing-2/#comment-127071</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Thu, 25 Jun 2009 23:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=820#comment-127071</guid>
		<description>A few huge problems in writing about pricing:

1.  Quantity discounts are major.  (Or negotiated prices.)
2.  Quantity discounts are severe.
3.  The mapping between TB of user data and hardware or storage is very imprecise.
4.  Vendors aren&#039;t particularly forthcoming, and even if one tried to get the info from users, each situation is different.

I do the best I reasonably can. :)</description>
		<content:encoded><![CDATA[<p>A few huge problems in writing about pricing:</p>
<p>1.  Quantity discounts are major.  (Or negotiated prices.)<br />
2.  Quantity discounts are severe.<br />
3.  The mapping between TB of user data and hardware or storage is very imprecise.<br />
4.  Vendors aren&#8217;t particularly forthcoming, and even if one tried to get the info from users, each situation is different.</p>
<p>I do the best I reasonably can. <img src='http://www.dbms2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerome Pineau</title>
		<link>http://www.dbms2.com/2009/06/23/paraccel-pricing-2/#comment-126750</link>
		<dc:creator>Jerome Pineau</dc:creator>
		<pubDate>Wed, 24 Jun 2009 03:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=820#comment-126750</guid>
		<description>Man, I sure wish you&#039;d do a whole post on pricing in this industry. It&#039;s really all over the place (or maybe I&#039;m just not getting it) but I suspect many people could use some of your insight on that issue.  What does &quot;per TB&quot; really mean anyway?  Are there finite ways to price in this market or is it really just all over the place or &quot;à la tète du client&quot; as we say in French?!? :)</description>
		<content:encoded><![CDATA[<p>Man, I sure wish you&#8217;d do a whole post on pricing in this industry. It&#8217;s really all over the place (or maybe I&#8217;m just not getting it) but I suspect many people could use some of your insight on that issue.  What does &#8220;per TB&#8221; really mean anyway?  Are there finite ways to price in this market or is it really just all over the place or &#8220;à la tète du client&#8221; as we say in French?!? <img src='http://www.dbms2.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

