<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tracking Performance Problems &#8211; Inserting a Hint into SQL in a Compiled Program</title>
	<atom:link href="http://hoopercharles.wordpress.com/2009/12/18/tracking-performance-problems-inserting-a-hint-into-sql-in-a-compiled-program/feed/" rel="self" type="application/rss+xml" />
	<link>http://hoopercharles.wordpress.com/2009/12/18/tracking-performance-problems-inserting-a-hint-into-sql-in-a-compiled-program/</link>
	<description>Miscellaneous Random Oracle Topics: Stop, Think, ... Understand</description>
	<lastBuildDate>Thu, 23 May 2013 04:02:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Blogroll Report 11/12/2009-18/12/2009 &#171; Coskan&#8217;s Approach to Oracle</title>
		<link>http://hoopercharles.wordpress.com/2009/12/18/tracking-performance-problems-inserting-a-hint-into-sql-in-a-compiled-program/#comment-90</link>
		<dc:creator><![CDATA[Blogroll Report 11/12/2009-18/12/2009 &#171; Coskan&#8217;s Approach to Oracle]]></dc:creator>
		<pubDate>Sat, 02 Jan 2010 17:50:55 +0000</pubDate>
		<guid isPermaLink="false">http://hoopercharles.wordpress.com/?p=389#comment-90</guid>
		<description><![CDATA[[...] 28-How to tune by hacking stored outlines ? Charles Hooper-Tracking Performance Problems – Inserting a Hint into SQL in a Compiled Program [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 28-How to tune by hacking stored outlines ? Charles Hooper-Tracking Performance Problems – Inserting a Hint into SQL in a Compiled Program [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
