Cannot truncate logs full when transaction cannot rollback
Hello, I recently experienced the problem when my database has a full transaction log but I can't truncate it via SSMS. I had to pass commands manually in T-SQL, but since the log was full, a query in progress was killed and proceeded to a rollback. However, the rollback was blocked at 0% because the logs were full, and the log files were locked because a transaction was in progress… Is there any other way of getting out of this situation without restarting the instance? (I've tried a backup + log shrink, adding log files, changing the recovery model to Simple, etc. But nothing works)
Full Transaction Log disk
Hello all, I have two databases and problems with the transaction disk growing up too much and getting don't less. Using the query: select name, recovery_model_desc, log_reuse_wait_desc from sys.databases I can see both databases have the Recovery Model set to FULL. The files .ldf get values too high. How can I change the default configuration to NEVER have problems with the full disk? Because once the disk is full the web application can't do more transactions/requests queries. Thank you.Lesson Learned #356: Transaction log full in Azure SQL due to CDC job.
Today, we faced a service request where our customer got the following issue Msg 9002, Level 17, State 2, Line 8 The transaction log for database '2d7c3f5a-XXXX-XZY-ZZZ-XXX' is full due to 'REPLICATION' and the holdup lsn is (194XXX:24X:1). Following I would like to share with you what was the lesson learned here.
