1Z0-536 · Question #26
Your customer wants to use Hybrid Column Compression, but they are concerned because they update recent data frequently. Which is the best strategy for addressing this scenario?
The correct answer is D. Partition table and use HCC on older, less updated partitions. Oracle partitioning provides the ability to divide a single table into smaller partitions. These partitions are typically based on date ranges (although other options are available). Using the combination of partitioning and EHCC (Exadata Hybrid Columnar Compression) it is…
Question
Your customer wants to use Hybrid Column Compression, but they are concerned because they update recent data frequently. Which is the best strategy for addressing this scenario?
Options
- AUse HCC in archive mode.
- BBatch write operations to increase the efficiency of HCC.
- CAvoid HCC at all costs.
- DPartition table and use HCC on older, less updated partitions.
How the community answered
(25 responses)- A16% (4)
- B8% (2)
- C4% (1)
- D72% (18)
Explanation
Oracle partitioning provides the ability to divide a single table into smaller partitions. These partitions are typically based on date ranges (although other options are available). Using the combination of partitioning and EHCC (Exadata Hybrid Columnar Compression) it is possible to develop something like this: * Active Partitions (0-6 months) - up to 10x compression using Exadata Hybrid Columnar Compression - Query Mode. * Historical Partitions (7- 24 months) - up to 10x compression using Exadata Hybrid Columnar Compression - Query mode * Archive Partitions (25 - 60 months) - up to 50x compressing using Exadata Hybrid Columnar Compression - Archive mode
Topics
Community Discussion
No community discussion yet for this question.