Contents
Why is my log file not replicating properly?
No is it not replicating properly to one or more subscribers. Replication must happen in order it was executed. If command 2 fails to replicate, it will never continue until command 2 succeeds. 1 or more of your subscribers is not taking transactions. You will not be able to shrink the log file until you resolve the issue.
Why does log backup show as ” log _ backup “?
If the log backup ran but still log_reuse_wait_desc shows as “LOG_BACKUP”, it’s probably because of the 2nd reason. What this means is that there are very few transactions on the database and these are all on the same VLF. When the log backup runs it cant clear the current VLF; so log_reuse_wait_desc can’t be reset.
How to shrink transaction log in SQL Server?
Shrink the transaction log. Put the database back into full recovery mode. Make a full database backup. Start again your transactional backups regular jobs. PS : Also make sure your transactional backups are not “copy-only” tagged.
Why is my log file growing but not shrinking?
Indicates replication is not working and has never replicated any data to at least one subscription. This is the reason for your log file growing and not able to be shrunk. Until you resolve this problem, or reinit all your subscriptions, you will not be able to shrink the log file.
Why does my log file grow to 72 GB?
I had issue before where the log file size grew to 72 GB, noticed that log_reuse_wait_desc is replication, and noticed that replication has an X on it. Okay, so I fixed replication and was able to truncate the log file down to 5 GB.
Why is my database transaction log file full?
The transaction log for database is full due to ‘REPLICATION’. Upon investigation, I found that my log file was capped at 100GB on ServerB.DBB which was causing the issue. To fix this, I added a new log file as I was unable to extend the existing log file due to same error. This fixed my issue and replication caught up in some time.