In short, can replication cause a transaction log file to grow and not be shrinkable? Specifically:
My database (now SQL 2005) had done fine for several years. The transaction log would occasionally get too large, and I'd back it up and shrink it. The "initial size" was something less than 10 MB, and so the file could shrink to a small size.
A few months ago I set up the database as a publisher and a distributor to replicate to another server. It's a snapshot push replication (runs continiuously, replicates once daily). I think it's around that time that the transaction log
starting growing significantly, and the "initial size" increased. Now the "initial size" is around 12 GB, over 1000 times larger than the actual original "initial size". Since SQL doesn't allow the transaction log file to decrease in size less
than the "initial size", it won't shrink. It doesn't seem good to have an MDF size of 3 GB and an LDF size of 13 GB.
I tried many things to resolve this, and got help from another Microsoft SQL forum, but no solution.
When I run dbcc shrinkfile, it generates the message "Cannot shrink log file ... because all logical log files are in use". Is it possible that the replication is what's keeping the logical log file
View Complete Post