In my SQL 2005 database, the log file is 12 GB and won't shrink. The initial size also is 12 GB. Does that mean that's the size of the active log, and is that why it cannot shrink smaller than that? The initial size used to be
around a MB or so. I understand why the file grows, but not why the initial size increases.
The transaction log grew even though the recovery mode was "Simple". I switched it to "Full" and backed up the transaction log (with the "truncate" option), but doing that didn't allow the log file to shrink.
Running dbcc shrinkfile generated the message "Cannot shrink log file ... because all logical log files are in use".
This database has been in use many years without having this problem. This problem might have started around the time I set up replication for this database. This server is the publisher and the distributor. Could this cause this problem?
Do I need to remove the replication before shrinking the log file?
I've read numerous other postings on similar problems, but haven't found the answer.
View Complete Post