I administrate a database where IT has recently enabled transaction log shipping. Over the weekend, some index reorgs caused the transaction log to grow substantially--approximately 10x its usual capacity. I'd like to use DBCC SHRINKFILE to reduce the size
back to normal, but IT has raised concerns re: whether this can break log shipping.
My research has shown mixed results, as it seems people only consider use of SHRINKFILE coupled with some other point-in-time backup. In my situation, the backups are fine, I'm merely trying to reclaim free space in the log.
My analysis indicates that backup operations break shipping, as they interfere w/ the backup chain. Since DBCC SHRINKFILE effects only the virtual log files, it should be safe. Could someone clarify whether this conclusion is correct?
