Re: HASH Partitioning question
- From: "Deepak Sharma" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "sharmakdeep_oracle@xxxxxxxxx" for DMARC)
- To: "tim@xxxxxxxxx" <tim@xxxxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 13 Feb 2015 02:00:51 +0000 (UTC)
Sure Tim (btw, I attended your DW seminar several years ago in Minneapolis and
have implemented a few ideas that have really helped).
600gb table with 14 Billion rows. It's currently partitioned on a loading date
column by range, and has a rolling window retention. Someone suggested changing
it to HASH Partition on another column (lets say ABC) which is more frequently
used, but may not have even distribution (so Range would have skewed data). My
guess is that in order for the queries to use that new ABC HASH partitioned
column (it could be equi-join, In-List etc.), PX is needed.
Let me know if you need more details.
-Deepak
On Thursday, February 12, 2015 3:19 PM, Tim Gorman <tim@xxxxxxxxx> wrote:
C'mon, you need to give us more than that, please?
Query for one row? Query for 10 million rows? Aggregating? Not aggregating?
Exadata or laptop or something in between? Oracle7? Oracle8i? Windows?
Linux? Android?
On 2/12/15 13:55, Deepak Sharma (Redacted sender sharmakdeep_oracle@xxxxxxxxx
for DMARC) wrote:
Is it true that if a table (say 1 billion rows) is HASH Partitioned, then the
most efficient way to query it needs to use Oracle parallel threads ?
Other related posts:
