A large number of UPDATE and DELETE operations made range scans slower.
Inspect unsorted regions and deleted rows before selecting maintenance work.
Which maintenance approach is most appropriate?
Inspect table state such as unsorted and deleted rows, then use VACUUM, ANALYZE, or redesign as evidence requires.
Detailed explanation
S3 lifecycle rules cannot reorganize Redshift blocks.
S3 lifecycle rules cannot reorganize Redshift blocks.
Rebuilding is costly and does not replace normal table maintenance.
Rebuilding is costly and does not replace normal table maintenance.
Measurement identifies unsorted regions and deleted rows that table maintenance can improve.
Measurement identifies unsorted regions and deleted rows that table maintenance can improve.
Removing audit records does not change the physical table state.
Removing audit records does not change the physical table state.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift VACUUM、SVV_TABLE_INFO、automatic table sortの公式説明を確認する。
What to confirm
表の論理更新と物理保守を区別し、計測後にVACUUMする理由を説明できる。
Key points
- VACUUM
- Unsorted rows
- Deleted rows
- ANALYZE
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Maintenance impact
VACUUM duration, locks, and concurrent workload must be considered.
Automation
Automatic optimization can help, but its scope and effect still require monitoring.