Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2012

    Unanswered: Best Partitioning Strategy to use

    I have a table called LOCATION which will grow to 60M records within a 2 year period. This is a historical dimension, for which there is a unique sequence primary key, and a unique business key which is the LOCATION_ID + CHANGE_DATE + CHANGE_TIME. I'm not sure what the best partitioning strategy would be. I think users will want to pull for a specific LOCATION ID all of the changes to it over time. That would suggest a hash - range, but that isn't an option. This is 11G btw. I want to take advantage of partition pruning. I don't want to enable FK constraints due to load performance, so don't want to use REF parititioning. Interval limits me to just single level. What should I try? Thank you!

  2. #2
    Join Date
    Aug 2003
    Where the Surf Meets the Turf @Del Mar, CA
    Provided Answers: 1
    post results from following SQL using COPY & PASTE

    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  3. #3
    Join Date
    Oct 2011
    Hamburg, Germany
    i would say if it historical data, so i would try a range partition

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts