Home » RDBMS Server » Performance Tuning » Create partition Index on Non-partition column (19)
Create partition Index on Non-partition column [message #690344] Mon, 28 April 2025 07:20 Go to next message
deepakdot
Messages: 93
Registered: July 2015
Member
Greetings !

Lets say table definition is :

CREATE TABLE TEST_PART
(COL1 NUMBER(10),
COL2 NUMBER(10),
COL3 NUMBER(10));

Table is partitioned (Range Partition ) on 2 columns Col1 and Col2.

When i have partition index on both Col1 and col2 as index column, its good.

My Que is : My Question is, does it benefit if WE create a LOCAL Partition index but the columns in the table is not partitions.
i.e. If I am creating an index on COl1 and COL3 ( where Col3 is not partition key column), is it good to have this as a partition index or we should keep this as a non- partitioned index ? What is the recommendation.

CREATE INDEX TEST_PART_II  ON TEST_PART (
COl1 ASC
,COL3 ASC
) LOCAL;

[Updated on: Mon, 28 April 2025 08:05]

Report message to a moderator

Re: Create partition Index on Non-partition column [message #690345 is a reply to message #690344] Mon, 28 April 2025 09:54 Go to previous messageGo to next message
John Watson
Messages: 8977
Registered: January 2010
Location: Global Village
Senior Member
A local index like that might not be very attractive to the optimizer, depending on how many index partitions would have to be searched.
Re: Create partition Index on Non-partition column [message #690346 is a reply to message #690345] Mon, 28 April 2025 12:26 Go to previous message
deepakdot
Messages: 93
Registered: July 2015
Member
Its around 10 partition. as the table is partitioned with some other column than the index column, its scanning all the partition .
Previous Topic: Simple Query on Table with Billions of rows getting ORA-01652
Next Topic: Performances and tuning
Goto Forum:
  


Current Time: Sun May 18 14:40:59 CDT 2025