A backup you have never restored is a hypothesis. What coverage checks prove, what they do not, and how to run a restore drill that measures your real recovery time.
Four questions in order: what is this, what is it supposed to do, what is it short of, and what is unprotected. The order matters more than the speed, and nothing gets changed.
A linked server that works on the server and fails from your desktop is the double hop. The query that proves it, the four login mappings and what each one fails with, plus error 7391 and MS DTC.
SQL Server Agent jobs queued with message [398]: how to see what is waiting for a thread right now, which of 3 similarly named limits you hit, and the Windows desktop heap value that cleared it on a clustered distributor.
Wait statistics accumulate from startup, so on a long-running instance they describe history rather than the problem in front of you. Two snapshots and a subtraction fix that.
SQL Server cannot obtain a LOCK resource at this time. What error 1204 actually means, the 1 query and the 1 ERRORLOG line that find the cause, and the fix in the order worth trying.
Mid restore is the wrong moment to work out how differential and log backups differ. What each one contains, which files you actually need, and the trap that any ordinary full backup taken by anyone silently becomes the new base for your differentials.
Two settings decide when SQL Server splits a query across processors, and both ship with values you are probably meant to change. Microsoft’s current MAXDOP table, what they actually say about cost threshold, and why CXPACKET is no longer the evidence it used to be.
A transaction log is filling a disk and the backup job says it succeeded. SQL Server already knows why it cannot reuse the space, and it tells you in one column of sys.databases.
Ever wondered what is happening inside your SQL Server instance right now? sp_who, sp_who2 and sp_whoisactive all answer that question, at very different depths. The first ships documented, the second ships undocumented but better, and the third is a free community procedure that most working DBAs treat as the real answer. This post is the…