Issues with Log Shrink

playerz I think the roadblock you're encountering is tied to ongoing activity within the database. Specifically, active checkpoints and uncommitted transactions are preventing a direct shrink or truncation of the LDF file.

The "status 2" entries in DBCC LOGINFO indicate these active checkpoints, while the "CHECKPOINT" in log_reuse_wait_desc reinforces this. Unfortunately, these checkpoints are vital, and you can't eliminate them directly. To address this, consider executing DBCC CHECKPOINT (ALL) to forcibly complete all active checkpoints. Keep tabs on the status using the DBCC CHECKPOINT command. Additionally, examine uncommitted transactions using DBCC OPENTRAN and ensure they are either committed or rolled back. Resolving these transactions is crucial for successful shrinkage.

Remember, when shrinking the transaction log, gradually reduce its size in increments of 10-20%. Also, ensure the database is in simple recovery mode, as direct shrinkage isn't feasible in full recovery mode. Monitor the log size post-shrinkage to avoid unexpected growth.