By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,850 Members | 972 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,850 IT Pros & Developers. It's quick & easy.

Range Partitioning

P: 2
I have 2 questions regarding DB2 9's Range Partitioning.
1. Do the Partition fields have to reside on the table being Partitioned? We have a Fact table we would like to Partition and the Week identifier resides on the table. This identifier's parent Dimension table has a month value. In order to Partition the Fact table by month, somehow the Dimension table would need to be referenced.

2. The Fact table mentioned in the above paragraph is approximately 1 Terabyte and as mentioned, contains weekly level data. There are approximately 4 to 6 million rows per week. Are there enough rows to create a partition at this level or would we need to create the partition at a monthly level, which would be approximately 24 million rows. Is there a lot of overhead in creating 52 partitions per year versus 12. We plan on having 5 years of history and on that 6th year, begin dropping partitions either weekly or monthly, depending on the partitioning strategy we use. Is there much more overhead in the weekly versus monthly partition dropping.
May 23 '07 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.