we have a production system SQL2008R2 regular with single snapshot replication to same server.
The transaction log will grow out of control from time to time (1 month, 4 months after fix). Transaction log backup and full backup won't solve it.
select name, log_reuse_wait_desc from sys.databases
show its used by "6" replication.
Other than simple jobs, transacation log backup, indexing etc, I only have disable the "Replication Transaction- Log Reader" job. That was created by SQL when creating snapshot replication.
So far research only tell me to drop and redo replication, which I want to minimize as much as possible.
Any help how to local the problem? Thanks in advance.
Simon