CompTIA DataSys+ (DS0-001)Database Management and MaintenanceEasy
A database administrator is reviewing the database's error logs and notices a recurring warning about 'insufficient disk space for transaction logs'. The database is configured for full recovery mode. Which of the following actions should the administrator take FIRST to address this issue?
- AChange the database recovery model to simple.
- BPerform a transaction log backup.
- CMove the transaction log files to a different drive.
- DIncrease the size of the transaction log files.
Show answer & explanationAnswer & explanation
Correct answer: B. Perform a transaction log backup.
In full recovery mode, transaction logs are not truncated until a log backup occurs. Performing a log backup will free up space by marking inactive VLF (Virtual Log Files) for reuse, addressing the immediate 'insufficient disk space' warning.
Why the other options are wrong
- A. Changing the recovery model to simple would prevent point-in-time recovery and is a drastic measure that should only be considered after understanding the implications.
- C. Moving log files might resolve a disk space issue on the current drive but doesn't address the log growth caused by the full recovery model without backups.
- D. While increasing log file size might provide temporary relief, it doesn't address the underlying issue of unbacked-up logs in full recovery mode.
Transaction Log Truncation
The process by which inactive portions of the transaction log are marked for reuse, preventing the log file from growing indefinitely.
- In full recovery mode, log truncation typically occurs after a successful transaction log backup.
- In simple recovery mode, truncation occurs automatically after a checkpoint.
- Regular log backups are crucial for managing disk space and enabling point-in-time recovery.
Memory trick: Logs need love, or they'll get too big!