Your database has been running with a peak load for the past hour. You want to preserve the performance statistics collected during this period forcomparison when you analyze the performance of the…

Increasing the window size of a moving window baseline only extends the rolling period for which AWR snapshots are preserved, but does not specifically target and permanently retain a particular historical peak load period.

Creating an AWR baseline on a pair of snapshots that encompass the peak load period explicitly preserves those specific snapshots from being purged, allowing for their use in future performance comparisons against current or other historical data.

While generating Active Session History (ASH) reports provides detailed performance insights, it only displays data from existing snapshots and does not prevent the underlying AWR or ASH data from being automatically purged.

Setting the AWR snapshot retention period extends the retention for *all* snapshots, consuming more storage space broadly, rather than precisely preserving only the performance statistics relevant to the identified peak load period.