If your customer wants to save storage space by compressing tables that are read frequently but rarely updated, which compression technique would you recommend?

The correct answer is C. QUERY HIGH. 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"…

Smart Scan and Hybrid Columnar Compression

Question

Options

AOLTP
BARCHIVE HIGH
CQUERY HIGH
DARCHIVE LOW
EBASIC

How the community answered

(30 responses)

B
3% (1)
C
77% (23)
D
13% (4)
E
7% (2)

Explanation

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

Topics

#QUERY HIGH compression#HCC#read-optimized tables#storage savings

Community Discussion

No community discussion yet for this question.

Full 1Z0-485 Practice