SQL Server would not start due to a corrupted model database with error 5125. Here is how to restore a corrupted model database from backup the right way.
Keeping msdb Small With sp_delete_backuphistory
Use sp_delete_backuphistory to control msdb growth, choose a retention window, and schedule weekly SQL Server Agent cleanup.
Recovering a Deleted Agent Job From an msdb Backup
Someone deleted the wrong Agent job. Here is how to get it back from an msdb backup without touching the live msdb.
Rebuilding System Databases With Setup When master Is Lost
Plan rebuilding system databases with Setup when master has no usable backup, then restore logins, jobs, and configuration.
What the model Database Passes to Every New Database
Audit the model database template for recovery model, options, objects, and file size, then verify growth settings on new databases.
Rehearsing a master Database Restore on a Test Instance
Rehearse a master database restore on a matching test instance, including single-user sqlcmd, automatic shutdown, and configuration checks.
Guest User in msdb: Keep CONNECT and Avoid Error 916
The guest user in msdb needs CONNECT permission for features that run under logins without a user there. I reproduced error 916 in a test database on SQL Server 2025, with a query to check guest in msdb and a way to list every database where guest can connect.