The idea
Analytical queries often read a few fields across many rows. A columnar layout stores values by column, which can reduce unnecessary reading and improve compression for suitable data. It is a different access pattern from updating one complete record at a time.
Design choice
Choose row-group sizes and compression with actual workloads, not a universal default. Preserve logical types such as decimals and timestamps. Check that all readers interpret the chosen representation consistently.
Worked example
A report reads date, region and revenue from a wide dataset. Column selection avoids loading unrelated descriptive fields, while a transactional application keeps its own update-oriented store.
Before you ship
- Benchmark the columns actually read
- Verify decimal and timestamp handling
- Keep transactional needs separate
Examples are illustrative. Adapt the checks to your own environment.