MSDB growth from the queue_messages tables means a Service Broker queue holds messages that nobody reads. This post builds a queue with unread messages in a test database, finds it with a size query, ends only its conversations with the CLEANUP option, and watches the space come back. It also says why you should never end every conversation in msdb.
Msg 3168: Backup Made by a Different SQL Server Version
Msg 3168 stopped a client from restoring master after a ransomware attack, because the backup and the new server had different build numbers. The fix is to make the two builds match, by patching up or uninstalling patches, and then restore again.
Reverting a Failed Deployment With a Database Snapshot
A snapshot can undo a bad release in minutes. See what comes back, what is lost for good, and why your log backups need a fresh start.
SQL SERVER – Master Database in Single User Mode – A Serious Issue
A client found the master database in single user mode, yet everything worked and switching back to MULTI_USER failed with Msg 5058. Here is the story.
SQL SERVER – Script Upgrade Failure – RsFxFt.Dll::RsFxMgmtInitialize failed: Error 0x80070002
A script upgrade failure left SQL Server down with RsFxFt.Dll error 0x80070002 and error 5597. Tested on SQL Server 2025: the FILESTREAM cause.
Error 913: Could Not Find Database ID 3, SQL Server Will Not Start
Error 913 means SQL Server could not find database ID 3, which is the model database, so the service will not start. A client had no backup of it and attaching the files failed. Rebuilding the system databases brought the instance back.
Error 468: Could Not Use View sysdac_instances Because of Binding Errors
Error 468 appeared as soon as we right clicked a database in SQL Server Management Studio. The view msdb.dbo.sysdac_instances could not be used because of binding errors. A collation mismatch between master and msdb caused it, and rebuilding the system databases fixed it.