|
-
Any particular reason to do hash partitioning?
What's the specific problem expected to be solved by this partitioning strategy?
- Hash partitioning doesn't help during archiving/purging.
- Hash partitioning doesn't help queries doing scattered read.
Suggested number of partitions will create partitions around 450K rows each, a little too small on my personal view. Depending on application needs and partitioning strategy we take advantage of much larger partitions, from 5M rows up.
In general I favor range-partitioning for large tables in reporting/dwh environments.
Having said that I have implemented with great success hash partitioning on high volatility tables part of oltp systems - tables that are hit by a very high rate of insert/deletes, kind of virtually replacing the content of the whole table in a few hours.
Last edited by PAVB; 07-02-2010 at 08:57 AM.
Reason: typo
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote