A forgotten BEGIN TRAN can pin your log for hours. Here is how to find the owner, read its age, and confirm the transaction is the reason.
Msg 2555: Cannot Empty a TempDB File With EMPTYFILE
Msg 2555 stopped a client from emptying and removing extra TempDB files with DBCC SHRINKFILE and EMPTYFILE. The messages window showed a work table page that could not be moved. Cache-clearing commands and a restart did not help, but the -f startup parameter did.
SQL SERVER – Cannot Shrink Log File 2 (SQLAuthorityDB_log) Because the Logical Log File Located at the End of the File is in Use
Diagnose a cannot shrink log file message with read-only SQL, active VLF checks and log reuse waits. Keep backup protection and size for the workload.
Only Two VLFs: Cannot Shrink the Log File Any Further
A log file with only two VLFs cannot shrink any further, and DBCC SHRINKFILE tells you so. The message says the number of logical log files cannot be fewer than 2. Here is the script that reproduces it and the DBCC LOGINFO output that explains it.
SQL SERVER – Information Message: Cannot shrink file in database to xxxx pages as it only contains yyyy pages.
A reader hardcoded 1 GB in my log shrink script and got: Cannot shrink file in database to xxxx pages as it only contains yyyy pages. I explain why it appears.
How to Shrink All the Log Files for SQL Server? – Interview Question of the Week #203
Question: How to Shrink All the Log Files for SQL Server? Here is the script, plus why you should shrink only log files and never data files.
Recording Who Granted What With a Database Audit Specification
Current permissions never say who changed them. Set up a small audit, run a grant, a revoke and a failed attempt, and read the events back.