Re: Can not partition existings tables
Around 30 values? And it is a BIGINT?
You will probably have to give up your AUTO_INCREMENT.
A Partitioned table MUST _either_
* Have no PRIMARY KEY, nor UNIQUE key; _or_
* Have the partition key in EVERY PRIMARY KEY and UNIQUE key.
Without those constraints, it is too costly to assure that an INSERT does not violate UNIQUEness.
Note: All those extra indexes are pretty useless once you Partition the table -- any query that wants to use any of them would have to touch every partition. That is, Partition "pruning" cannot be used to speed things up (in those cases).
What is your goal in Partitioning? I ask this because there are some goals for which Partitioning does not help as much as one would hope.
Subject
Views
Written By
Posted
3120
June 03, 2010 04:06AM
Re: Can not partition existings tables
1836
June 04, 2010 08:22PM
1750
June 07, 2010 03:55AM
1688
June 07, 2010 11:18PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.