Which is the best strategy for addressing this scenario?

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?

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?

A.
Use HCC in archive mode.

B.
Batch write operations to increase the efficiency of HCC.

C.
Avoid HCC at all costs.

D.
Partition table and use HCC on older, less updated partitions.

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
http://blogs.oracle.com/datawarehousing/entry/new_whitepaper_on_exadata_hybr



Leave a Reply 0

Your email address will not be published. Required fields are marked *