Run an aggregation SQL statement every hour and update a result table.
Record failures and prevent duplicate updates for the same time window.
Which automation approach is most appropriate?
Use a Redshift scheduled query with time parameters and an idempotent MERGE or replacement strategy.
Detailed explanation
The schedule and SQL are managed together, while a time-keyed update prevents duplicate aggregation.
The schedule and SQL are managed together, while a time-keyed update prevents duplicate aggregation.
Runs can be missed, mistimed, and difficult to audit.
Runs can be missed, mistimed, and difficult to audit.
An object rename is not a Redshift SQL scheduler.
An object rename is not a Redshift SQL scheduler.
TTL deletion does not directly schedule Redshift SQL.
TTL deletion does not directly schedule Redshift SQL.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift scheduled query、query editor v2、SQL parametersの公式説明を確認する。
What to confirm
SQLスケジューラと手動・無関係イベント起動の違いを説明できる。
Key points
- Scheduled query
- SQL parameter
- Idempotency
- Aggregation
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Duplicate protection
Use a date or window key with MERGE or replacement instead of unconditional append.
Operational evidence
Track query failure, duration, locks, and workload-management waits.