<?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: Fixing Performance in Vendor Apps</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/sql-server/fixing-performance-in-vendor-apps/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/sql-server/fixing-performance-in-vendor-apps/</link>
	<description></description>
	<lastBuildDate>Thu, 06 Jun 2013 18:56:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Kekline</title>
		<link>http://itknowledgeexchange.techtarget.com/sql-server/fixing-performance-in-vendor-apps/#comment-1584</link>
		<dc:creator>Kekline</dc:creator>
		<pubDate>Mon, 12 Dec 2011 16:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/sql-server/fixing-performance-in-vendor-apps/#comment-1584</guid>
		<description><![CDATA[Another option that is occassionally available is to use Plan Guides, telling SQL Server to use a plan that I provide for it rather than one that the vendor uses.  I wouldn&#039;t use plan guides in SQL2005 because they&#039;re too brittle and break to easily.  But they&#039;re a useable alternative in SQL2008 or later versions.

One other recommendation I like to give with regards to third-party applications is to document bad performance and complain LOUDLY every time it comes up for maintenance renewal.  Maybe even drag your feet on paying, email the Sales team and cc the Sales executives, and otherwise make yourself the squeaky wheel.  The R&amp;D organization of most vendors are someone tone-deaf to complaints, but Sales leaves and breaths by positive referrals.  Use that power to your advantage to get the Sales team to put internal pressure on the R&amp;D team to make fixes and improve performance.

-Kevin Kline
[A href=&quot;http://twitter.com/kekline&quot;]Twitter @kekline[/A]]]></description>
		<content:encoded><![CDATA[<p>Another option that is occassionally available is to use Plan Guides, telling SQL Server to use a plan that I provide for it rather than one that the vendor uses.  I wouldn&#8217;t use plan guides in SQL2005 because they&#8217;re too brittle and break to easily.  But they&#8217;re a useable alternative in SQL2008 or later versions.</p>
<p>One other recommendation I like to give with regards to third-party applications is to document bad performance and complain LOUDLY every time it comes up for maintenance renewal.  Maybe even drag your feet on paying, email the Sales team and cc the Sales executives, and otherwise make yourself the squeaky wheel.  The R&amp;D organization of most vendors are someone tone-deaf to complaints, but Sales leaves and breaths by positive referrals.  Use that power to your advantage to get the Sales team to put internal pressure on the R&amp;D team to make fixes and improve performance.</p>
<p>-Kevin Kline<br />
[A href="http://twitter.com/kekline"]Twitter @kekline[/A]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
