<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Striving for Optimal Performance &#187; Oracle Database</title>
	<atom:link href="http://antognini.ch/category/oracledatabase/feed/" rel="self" type="application/rss+xml" />
	<link>http://antognini.ch</link>
	<description></description>
	<lastBuildDate>Thu, 02 Sep 2010 04:05:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Parallel Processing With Standard Edition</title>
		<link>http://antognini.ch/2010/09/parallel-processing-with-standard-edition/</link>
		<comments>http://antognini.ch/2010/09/parallel-processing-with-standard-edition/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 08:55:59 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Parallel Processing]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1258</guid>
		<description><![CDATA[As clearly stated in the Licensing Information guide, all features related to parallel processing (parallel backup and recovery, parallel query/DML, parallel statistics gathering, parallel index build/scans, parallel Data Pump export/import, in-memory parallel execution, parallel statement queuing and parallel spatial index builds) are only available with the Enterprise Edition. However, as of Oracle Database 11g Release [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/09/parallel-processing-with-standard-edition/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Exadata Storage Server and the Query Optimizer – Part 4</title>
		<link>http://antognini.ch/2010/08/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-4/</link>
		<comments>http://antognini.ch/2010/08/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-4/#comments</comments>
		<pubDate>Mon, 09 Aug 2010 15:37:40 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[Exadata]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1227</guid>
		<description><![CDATA[When I started writing the series of posts about Exadata Storage Server and the query optimizer, I didn’t expect to write more than three posts (part 1, part 2, part 3). Of course, things change. Hence, here is part 4 to cover a couple of things that I learned in the next couple of months.
In [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/08/exadata-storage-server-and-the-query-optimizer-%e2%80%93-part-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Partially Index a Table</title>
		<link>http://antognini.ch/2010/08/partially-index-a-table/</link>
		<comments>http://antognini.ch/2010/08/partially-index-a-table/#comments</comments>
		<pubDate>Wed, 04 Aug 2010 07:31:40 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Indexes]]></category>
		<category><![CDATA[Partitioning]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1214</guid>
		<description><![CDATA[Recenty the following question was posted on oracle-l (I paraphrase&#8230;): 
With Oracle Database it is possible to create something similar to Teradata&#8217;s sparse indexes?
Since the question is an interesting one, I decided to write this short post.
First of all, I have to say that such a feature is not supported by the CREATE INDEX statement [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/08/partially-index-a-table/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Partition-Wise Join of List-Partitioned Tables</title>
		<link>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/</link>
		<comments>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 09:59:08 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Partitioning]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1202</guid>
		<description><![CDATA[When two tables are equi-partitioned on their join keys, the query optimizer is able to take advantage of partition-wise joins. To make sure that the tables are equi-partitioned, as of Oracle Database 11g reference partitioning can be used. In fact, per definition, with reference partitioning all “related” tables have exactly the same partitioning schema. If [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/08/partition-wise-join-of-list-partitioned-tables/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Related-Combine Operation „UNION ALL (RECURSIVE WITH)“</title>
		<link>http://antognini.ch/2010/06/related-combine-operation-union-all-recursive-with/</link>
		<comments>http://antognini.ch/2010/06/related-combine-operation-union-all-recursive-with/#comments</comments>
		<pubDate>Thu, 10 Jun 2010 06:53:37 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Query Optimizer]]></category>
		<category><![CDATA[TOP]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1160</guid>
		<description><![CDATA[To make easier the interpretation of execution plans, in chapter 6 of TOP I defined three types of operations: standalone operations, unrelated-combine operations, and related-combine operations. For combine operations I also added a list of all operations of each type. Since in 11.2 a new related-combine operation is available, I decided to write this short [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/06/related-combine-operation-union-all-recursive-with/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Evolution of a SQL Plan Baseline Based on a DELETE Statement</title>
		<link>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/</link>
		<comments>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/#comments</comments>
		<pubDate>Mon, 07 Jun 2010 14:21:26 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Query Optimizer]]></category>
		<category><![CDATA[SQL Trace]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1139</guid>
		<description><![CDATA[During an evolution the database engine compares the performance of two execution plans. The aim is to find out which one provides the better performance. For that purpose it has to run the SQL statement on which the SQL plan baseline is based and compare some execution statistics. The following output of the DBMS_SPM.EVOLVE_SQL_PLAN_BASELINE function [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/06/evolution-of-a-sql-plan-baseline-based-on-a-delete-statement/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Optimizer Mode Mismatch Does Not Prevent Sharing of Child Cursor!?!?</title>
		<link>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/</link>
		<comments>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/#comments</comments>
		<pubDate>Thu, 03 Jun 2010 17:40:03 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR1]]></category>
		<category><![CDATA[10gR2]]></category>
		<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[9iR2]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[Query Optimizer]]></category>
		<category><![CDATA[SQL Trace]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1113</guid>
		<description><![CDATA[The aim of this post is to describe a strange (buggy) situation that I observed recently. But before doing that, I shortly summarize what a parent cursor and a child cursor are as well as when they can be shared. By the way, I borrowed this description from the pages 20/21 of my book. Hence, [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/06/optimizer-mode-mismatch-does-not-prevent-sharing-of-child-cursor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How Good Are the Values Returned by DBMS_COMPRESSION.GET_COMPRESSION_RATIO?</title>
		<link>http://antognini.ch/2010/05/how-good-are-the-values-returned-by-dbms_compression-get_compression_ratio/</link>
		<comments>http://antognini.ch/2010/05/how-good-are-the-values-returned-by-dbms_compression-get_compression_ratio/#comments</comments>
		<pubDate>Thu, 20 May 2010 00:00:17 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[Exadata]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1078</guid>
		<description><![CDATA[According to the documentation the GET_COMPRESSION_RATIO procedure of the DBMS_COMPRESSION package can be used to assess the impact of different compression options for a given table. In other words, it allows us to find out the expected compression ratio for a given set of data without having to really create a compressed table. The question [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/05/how-good-are-the-values-returned-by-dbms_compression-get_compression_ratio/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Exadata Storage Server and the Query Optimizer &#8211; Part 3</title>
		<link>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/</link>
		<comments>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/#comments</comments>
		<pubDate>Wed, 05 May 2010 14:55:26 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[11gR1]]></category>
		<category><![CDATA[11gR2]]></category>
		<category><![CDATA[Exadata]]></category>
		<category><![CDATA[Parallel Processing]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1018</guid>
		<description><![CDATA[In the first and second post of this series I shared with you some basics about smart scan and gave some details about projection and restriction. The aim of this post is to cover the third basic technique: join filtering.
Join filtering is not something specific to the Exadata Storage Server. In fact, it is an [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/05/exadata-storage-server-and-the-query-optimizer-part-3/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Native Full Outer Join Officially Available in 10.2.0.5</title>
		<link>http://antognini.ch/2010/05/native-full-outer-join-officially-available-in-10-2-0-5/</link>
		<comments>http://antognini.ch/2010/05/native-full-outer-join-officially-available-in-10-2-0-5/#comments</comments>
		<pubDate>Tue, 04 May 2010 11:25:26 +0000</pubDate>
		<dc:creator>Christian Antognini</dc:creator>
				<category><![CDATA[10gR2]]></category>
		<category><![CDATA[Query Optimizer]]></category>

		<guid isPermaLink="false">http://antognini.ch/?p=1041</guid>
		<description><![CDATA[Today I installed for the first time the patchset 10.2.0.5. While reading the README file, I noticed the following piece of information.
To enable a new native full outer join implementation in the database, a user has to set the following underscore parameter:
_optimizer_native_full_outer_join =force
You can set this parameter for the system or for a specific session.
Besides [...]]]></description>
		<wfw:commentRss>http://antognini.ch/2010/05/native-full-outer-join-officially-available-in-10-2-0-5/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
