If your customer wants to save storage space by compressing tables that are read frequently but
rarely updated, which compression technique would you recommend?
A.
OLTP
B.
ARCHIVE HIGH
C.
QUERY HIGH
D.
ARCHIVE LOW
E.
BASIC
which compression technique would you recommend?
If your customer wants to save storage space by compressing tables that are read frequently but
rarely updated, which compression technique would you recommend?
Answer is B
Answer C
The clause “for query” compresses it in hybrid columnar manner. The clause “low” does not compress it as aggressively. So more space is consumed but compression and decompression do not consume as much CPU. A more aggressive compression can be achieved by replacing the “low” clause with “high”. This type of HCC is known as warehouse compression since it is useful for data warehouses where a lot of data is stored but they are queried frequently.
(Not B: Archive Compression is intended for tables or partitions that store
data that is rarely accessed.)
Matt is right. Correct answer should be C.
Get latest exam materials from http://www.exadata-certification.com
C
Table 1. Compression Technologies
Table Compression Method Create/Alter Table Syntax Direct-Path Insert Notes
Basic compression COMPRESS [BASIC] Rows are compressed with basic compression. Does not maintain compression for Data Manipulation Language (DML) INSERT/UPDATE operations after bulk load.
OLTP compression COMPRESS FOR OLTP Rows are compressed with OLTP compression. Maintains compression for DML operations.
Warehouse compression (Hybrid Columnar Compression) COMPRESS FOR QUERY [LOW|HIGH] Rows are compressed with warehouse compression. Ideal for active data warehouses.
Archive compression (Hybrid Columnar Compression) COMPRESS FOR ARCHIVE [LOW|HIGH] Rows are compressed with archive compression. Ideal for archive/historic data.