Three incidents that look alike and share nothing: a BACKUP that failed, a RESTORE that failed, and a restore that is still running. This page routes each one to the post that owns it.
A routing page for every out of space incident on SQL Server: which drive, which file, what log_reuse_wait_desc is telling you, and why shrinking comes last.
Which msdb history table is actually holding the space, why one far back cutoff makes sp_delete_backuphistory hang, and the date stepped purge that finishes.
The job outcome row never carries a cause. Read the step row in msdb.dbo.sysjobhistory first, then route the real message to the owner, proxy, permission, path or truncation behind it.
A router for every SQL Server login and permission failure. Find your error number, read the real 18456 state from the ERRORLOG, and go straight to the page that owns the fix.
BULK INSERT fails with 4861 and Access is denied on a file you can open in Notepad. With a SQL Server login the file is opened by the service account, not by you. The reproduction, the operating system error codes that mean something else, and the double hop.
Msg -2 comes from the client library, not from SQL Server. Here is how to tell the execution timeout from the connection timeout, find out whether the query was blocked when the client gave up, and why raising the timeout is not a fix.
Nobody has sysadmin, sa is disabled or its password is gone, and the instance is still running. The supported recovery is single-user mode, and it needs local admin on the box, not a SQL permission.
The backup is from a newer version of SQL Server than the server restoring it, and no option changes that. What the two version numbers mean, why attach fails with 948, and the routes that work.
SSMS refuses to save your Table Designer change because it needs the table dropped and re-created. Write it as ALTER TABLE instead, and here is what the re-creation would have cost, measured on 300,000 rows.