A Recovery Pending state means SQL Server could not finish opening a database, most often because it could not open a file. I reproduced two file errors on SQL Server 2025, show what each leaves in the error log, and explain how AUTO_CLOSE and antivirus scanning caused one client case.
SQL SERVER – Unable to Start SQL After Patching – Database SSISDB is Enabled for Database Mirroring
After patching, SQL Server would not start. The SSIS hotfix script failed because database SSISDB is enabled for Database Mirroring. Here is the fix.
SQL SERVER – Be Careful with Logon Triggers – Don’t use Host_Name
A reader used HOST_NAME() in a logon trigger to limit access. Here is why that is risky, and why Logon Triggers can lock everyone out if you are not careful.
Error 5511: FILESTREAM File System Log Record Is Corrupted
Error 5511 kept a production database offline after a SQL Server restart, because a FILESTREAM log record under the log folder was corrupted. We moved the corrupted file to another folder and the database came online. CHECKDB came out clean and the client saw no problems for weeks.
SQL SERVER – Upgrade Error – ALTER DATABASE Statement Not Allowed Within Multi-statement Transaction
A failed SQL Server 2014 SP2 left the service down with: ALTER DATABASE statement not allowed within Multi-statement Transaction. Here is how to fix it.
Error 14001 in SQL Server: Side-by-Side Configuration Is Not Correct
Error 14001 reports a side-by-side configuration failure before a program starts, and the Application log event names the missing assembly. This post reads that event, matches the assembly to its architecture and checks WinSxS and the installed runtimes with tested PowerShell commands.
SQL SERVER – Fix Error 3271: A nonrecoverable I/O error occurred on file. The remote server returned an error: (404) Not Found
Error 3271 during backup to URL has many causes. After the 403 and 400 versions, here is what causes the (404) Not Found error and how to fix it.