Which Redshift distribution style suits a small dimension table?
Why C is the answer
ALL
ALL keeps a copy on each node, which speeds joins.
In detail
- ALL copies a small table to each node, so joins are fast.
- ALL costs storage, so keep it to small tables.
Use case
An illustrative scenario, not a real incident.
A small country table is joined everywhere, and ALL keeps a copy on each node, so joins need no data movement.
See it in different ways
flowchart TD
A{"Redshift table"} -->|"Large, joined on one key"| B["KEY distribution"]
A -->|"Small dimension table"| C["ALL distribution"]
A -->|"No clear join key"| D["EVEN distribution"]mindmap
root((Distribution))
ALL
Small dimensions
KEY
Large joined tables
Care
VACUUM
ANALYZEflowchart TD
Q{"What kind of table?"}
Q -->|"Small dimension"| A0["ALL"]
Q -->|"Large joined table"| A1["KEY"]
Q -->|"No clear join key"| A2["EVEN"]Key point: ALL suits small dimensions.
Why the other options are wrong
- A. A style with one copy of the table per query
- That is not a distribution style.
- B. A style that stores the table only in S3
- That is not a distribution style.
- D. A style that sends each row to one node at random
- That describes EVEN, which does not help joins.