<?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>EveryDay Practical Solutions for an Oracle&#124;SQL Server DBA &#187; Index Tuning</title>
	<atom:link href="http://www.oracledbasupport.co.uk/category/tuning/index-tuning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oracledbasupport.co.uk</link>
	<description>This is my (Sagar PATIL ) blog to list day to day issues</description>
	<lastBuildDate>Fri, 20 Jan 2012 22:39:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Display partition information for a specified index</title>
		<link>http://www.oracledbasupport.co.uk/displays-partition-information-for-specified-index-2/</link>
		<comments>http://www.oracledbasupport.co.uk/displays-partition-information-for-specified-index-2/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 19:01:45 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[General DBA Tasks]]></category>
		<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[index Displays]]></category>
		<category><![CDATA[Online]]></category>
		<category><![CDATA[partitions]]></category>
		<category><![CDATA[Rebuild]]></category>
		<category><![CDATA[SET VERIFY]]></category>
		<category><![CDATA[WHERE]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/11/12/displays-partition-information-for-specified-index-2/</guid>
		<description><![CDATA[Displays partition information for the specified index, or all indexes. SET LINESIZE 500 SET PAGESIZE 1000 SET FEEDBACK OFF SET VERIFY OFFSELECT a.index_name, a.partition_name, a.tablespace_name, a.initial_extent, a.next_extent, a.pct_increase, a.num_rows FROM   dba_ind_partitions a WHERE  a.index_name  = Decode(&#8216;BRANCH_STATS_IX&#8217;,'ALL&#8217;,a.index_name,&#8217;BRANCH_STATS_IX&#8217;) ORDER BY a.index_name, a.partition_name; Replace &#8216;BRANCH_STATS_IX&#8217; with valid index_name select &#8216;Alter Index &#8216;&#124;&#124; index_owner &#124;&#124;&#8217;.'&#124;&#124;index_name &#124;&#124;&#8217; Rebuild Partition &#8216; [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/displays-partition-information-for-specified-index-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Function Based Indexes</title>
		<link>http://www.oracledbasupport.co.uk/function-based-indexes/</link>
		<comments>http://www.oracledbasupport.co.uk/function-based-indexes/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 18:25:19 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[first_name]]></category>
		<category><![CDATA[Function]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[SELECT STATEMENT]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/11/12/function-based-indexes/</guid>
		<description><![CDATA[Traditionally, performing a function on an indexed column in the where clause of a query guaranteed an index would not be used. Oracle 8i introduced Function Based Indexes to counter this problem. Rather than indexing a column, you index the function on that column, storing the product of the function, not the original column data. [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/function-based-indexes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When to Rebuild a B-Tree Index</title>
		<link>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index-2/</link>
		<comments>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index-2/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 18:14:20 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[BLEVEL]]></category>
		<category><![CDATA[HIGH]]></category>
		<category><![CDATA[index statistics]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[ROWS]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/11/12/when-to-rebuild-a-b-tree-index-2/</guid>
		<description><![CDATA[You have to periodically check your indexes to see if they become skewed and, therefore, good candidates for rebuild. A skewed index has many records clumped close together on the index tree due to their similar indexed values. When an index is skewed, parts of an index are accessed more frequently than others. As a [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Index Monitoring</title>
		<link>http://www.oracledbasupport.co.uk/index-monitoring/</link>
		<comments>http://www.oracledbasupport.co.uk/index-monitoring/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 17:49:50 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[DML]]></category>
		<category><![CDATA[Key]]></category>
		<category><![CDATA[lock]]></category>
		<category><![CDATA[OBJECT]]></category>
		<category><![CDATA[parent]]></category>
		<category><![CDATA[parent table]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/11/12/index-monitoring/</guid>
		<description><![CDATA[Index monitoring could be initiated and stopped using ALTER INDEX syntax shown below. ALTER INDEX my_index_i MONITORING USAGE; ALTER INDEX my_index_i NOMONITORING USAGE; Information about the index usage can be displayed using the V$OBJECT_USAGE view. SELECT index_name, table_name, monitoring, used, start_monitoring, end_monitoring FROM v$object_usage WHERE index_name = 'MY_INDEX_I' ORDER BY index_name; The V$OBJECT_USAGE view does [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/index-monitoring/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building virtual index using the NOSEGMENT clause.</title>
		<link>http://www.oracledbasupport.co.uk/building-our-virtual-index-using-the-nosegment-clause-2/</link>
		<comments>http://www.oracledbasupport.co.uk/building-our-virtual-index-using-the-nosegment-clause-2/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 17:48:05 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[department]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[NON]]></category>
		<category><![CDATA[orcl]]></category>
		<category><![CDATA[segment]]></category>
		<category><![CDATA[virtual index]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/11/12/building-our-virtual-index-using-the-nosegment-clause-2/</guid>
		<description><![CDATA[Let&#8217;s create a virtual index 07:59:12 orcl&#62; create index hr.emp2_emp_id_virtual on hr.employees2(employee_id) nosegment; Index created. I am going to set a hidden startup parameter &#8220;_use_nosegment_indexes&#8221; to TRUE so that our session will recognize our new virtual index. 08:00:09 orcl&#62; alter session set &#8220;_use_nosegment_indexes&#8221; = true; Running our statement again to see if it will use [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/building-our-virtual-index-using-the-nosegment-clause-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tuning SQL to drop execution cost</title>
		<link>http://www.oracledbasupport.co.uk/tuning-sql-to-drop-execution-cost-from-758319-to/</link>
		<comments>http://www.oracledbasupport.co.uk/tuning-sql-to-drop-execution-cost-from-758319-to/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 13:43:59 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[Cardinality]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[INDEX RANGE]]></category>
		<category><![CDATA[NUMR]]></category>
		<category><![CDATA[pnh]]></category>
		<category><![CDATA[ptc]]></category>
		<category><![CDATA[Rang]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/10/30/tuning-sql-to-drop-execution-cost-from-758319-to/</guid>
		<description><![CDATA[SELECT n.MSISDN, (SELECT ptc2.PRIMARY_ACCOUNT_NUMBER FROM p_topup_cards ptc2 WHERE ptc2.NUMR_MSISDN = n.MSISDN --AND ptc2.CARD_TYPE = 1 AND ptc2.PRIMARY_ACCOUNT_NUMBER LIKE '894428%' AND ROWNUM &#60; 2) pan FROM numbers n ,p_number_history pnh WHERE n.MSISDN = pnh.NUMR_MSISDN AND n.STATUS = 'A' AND n.Barred = 'N' AND n.spid_spid = '416' --AND n.first_transaction IS NOT NULL --AND pnh.END_TIMESTAMP IS NULL AND [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/tuning-sql-to-drop-execution-cost-from-758319-to/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How optimizer stats with Histograms can change execution Plan</title>
		<link>http://www.oracledbasupport.co.uk/how-histograms-can-change-execution-plan/</link>
		<comments>http://www.oracledbasupport.co.uk/how-histograms-can-change-execution-plan/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 08:41:42 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[MAX]]></category>
		<category><![CDATA[Mode]]></category>
		<category><![CDATA[Optimizer]]></category>
		<category><![CDATA[table]]></category>
		<category><![CDATA[WHERE]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/07/03/how-histograms-can-change-execution-plan/</guid>
		<description><![CDATA[Optimizer stats can play a key part in deciding execution plan. Here is an example Table &#8220;RSODSACTREQ&#8221; has 313783 of total rows Database with NO histograms : For following 4 statements the SQL plan is always same i.e FULL TABLE SCAN 1. SELECT MAX( &#8220;TIMESTAMP&#8221; ) FROM SAPLIVE.&#8221;RSODSACTREQ&#8221; WHERE &#8220;ODSOBJECT&#8221; = &#8216;ZPNPCAMP&#8217; 2. SELECT MAX( [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/how-histograms-can-change-execution-plan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Backup/Export Oracle Optimizer Statistics into Table</title>
		<link>http://www.oracledbasupport.co.uk/how-to-backupexport-oracle-optimizer-statistics-into-table/</link>
		<comments>http://www.oracledbasupport.co.uk/how-to-backupexport-oracle-optimizer-statistics-into-table/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 23:54:00 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[CREATE]]></category>
		<category><![CDATA[DBA]]></category>
		<category><![CDATA[Export statistics]]></category>
		<category><![CDATA[imp]]></category>
		<category><![CDATA[STAT]]></category>
		<category><![CDATA[statistics]]></category>
		<category><![CDATA[statistics table]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/04/16/how-to-backupexport-oracle-optimizer-statistics-into-table/</guid>
		<description><![CDATA[Exporting and Importing Statistics Caveat: Always use import/export and use imp/exp utility on schema user who owns tables. I have wasted a week where I was exporting as DBA for XYZ user and then importing into different system under different username. Statistics can be exported and imported from the data dictionary to user-owned tables. This [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/how-to-backupexport-oracle-optimizer-statistics-into-table/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identifying a Poor performing SQL</title>
		<link>http://www.oracledbasupport.co.uk/identifying-a-poorly-performing-sql/</link>
		<comments>http://www.oracledbasupport.co.uk/identifying-a-poorly-performing-sql/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 21:31:00 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[Utilties]]></category>
		<category><![CDATA[disk]]></category>
		<category><![CDATA[executions]]></category>
		<category><![CDATA[physical disk]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[run]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[text]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/04/16/identifying-a-poorly-performing-sql/</guid>
		<description><![CDATA[Our preferred v$sqlarea query is to actually report on physical disk I/O per statement execution. Hit ratios are informative but sometimes misleading. Logical I/O is less relevant. If the statement executes 1,000,000 logical I/Os but still only takes less than one-tenth of a second, who cares? It is the total physical I/O that consumes nearly [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/identifying-a-poorly-performing-sql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When to Rebuild a B-Tree Index</title>
		<link>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index/</link>
		<comments>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index/#comments</comments>
		<pubDate>Sun, 13 Jan 2008 23:00:00 +0000</pubDate>
		<dc:creator>Sagar Patil</dc:creator>
				<category><![CDATA[Index Tuning]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[b-tree]]></category>
		<category><![CDATA[BLEVEL]]></category>
		<category><![CDATA[HIGH]]></category>
		<category><![CDATA[index statistics]]></category>
		<category><![CDATA[indexes]]></category>
		<category><![CDATA[ROWS]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[statistics]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://www.oracledbasupport.co.uk/2008/01/13/when-to-rebuild-a-b-tree-index/</guid>
		<description><![CDATA[A skewed index has many records clumped close together on the index tree due to their similar indexed values. When an index is skewed, parts of an index are accessed more frequently than others. As a result, disk contention may occur, creating a bottleneck in performance.This is a tricky question for every DBA. It is [...]]]></description>
		<wfw:commentRss>http://www.oracledbasupport.co.uk/when-to-rebuild-a-b-tree-index/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

