Shrink maintenance rule
Purpose:
- To reclaim unused space in the database
Why It’s Important:
- Shrinking reduces database file size when there is significant free space (e.g., after deleting large amounts of data).
- However, caution is required because frequent shrinking can cause fragmentation and performance issues.
- It is best used after significant cleanup or archiving operations to optimize storage usage.
Shrink rule wizard step 1 – Optimization Options
Shrink Operation Configuration
1. Shrink Data Files
- Specify whether the operation should shrink data files.
- Define the desired amount of free space to leave in the data files after the shrink operation is complete.
2. Shrink Log Files
- Specify whether the operation should shrink log files.
- Define the desired amount of free space to leave in the log files after the shrink operation is complete.
3. Backup Log Files
Indicate whether the log file should be backed up before the shrink operation begins, ensuring data recovery capabilities.
4. Log File Truncate Only
Enable support for the truncate-only log file option, primarily for legacy system compatibility.