An event table is frequently filtered by an event_time range.
Reduce block reads for queries that exclude old data.
Which physical design is most appropriate?
Use event_time as a Redshift SORTKEY candidate so zone maps can prune blocks for range predicates.
Detailed explanation
Distribution controls node placement and does not guarantee range-ordered blocks.
Distribution controls node placement and does not guarantee range-ordered blocks.
Archiving data does not improve scans that still need to run in Redshift.
Archiving data does not improve scans that still need to run in Redshift.
Time-ordered blocks enable predicate filtering and block pruning for range queries.
Time-ordered blocks enable predicate filtering and block pruning for range queries.
A logging service does not improve Redshift table physical design.
A logging service does not improve Redshift table physical design.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift sort keys、zone maps、predicate filteringの公式説明を確認する。
What to confirm
SORTKEYが範囲検索のブロックプルーニングに使われることを説明できる。
Key points
- SORTKEY
- Zone map
- Range scan
- VACUUM
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Sort versus distribution
SORTKEY helps block pruning; DISTKEY controls node placement and join movement.
Maintenance state
Load order and updates can reduce sorted-region benefits and require maintenance or automation.