⏳Part of the SQL Server Wait Types Library, every wait type explained.Related deep dive: IO_COMPLETION Wait TypeRelated pillar: Performance & Troubleshooting Is It a Problem? Not in itself. It follows the length and parallelism of your offline index builds, and it was zero on our SQL Server 2025 lab. Get Wait Statistics does not filter…
⏳Part of the SQL Server Wait Types Library, every wait type explained.Related deep dive: IO_COMPLETION Wait TypeRelated pillar: Performance & Troubleshooting Is It a Problem? In the cumulative totals, no. It is commonly filtered as benign, and Get Wait Statistics filters it out by default. On our SQL Server 2025 lab it had over a…
⏳The complete SQL Server Wait Types Library, every wait type explained, with a verdict on whether it is worth investigating or normally just noise.Related pillar: Performance & Troubleshooting Something on the server is slow and you need to know what it is waiting on. Pick what you are seeing below, or paste the wait name…
⏳Part of the SQL Server Wait Types Library, every wait type explained.Related pillar: Performance & Troubleshooting RESOURCE_SEMAPHORE means a query is waiting for a workspace memory grant, memory SQL Server reserves up front for sorts, hashes, and other operators before the query is allowed to run at all, and there isn’t enough available right now.…
🚨Part of the SQL Server Errors series, the exact messages and what actually causes them.Related pillar: Performance & Troubleshooting What Msg 207 Says Msg 207 · Level 16 · State 1 Invalid column name ‘no_such_column’. ⚡The column does not exist in the context the query is running in. Before assuming a typo, check the object’s…
🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Server & Configuration › Server Inventory Choose the linked-server check you need Start with Get-LinkedServerConnectivity to check whether a linked server is reachable and see the returned error detail. For a migration pre-check, run Get-LinkedServerAndJobInventory for logins, linked servers, and SQL Agent jobs.…
Blocking isn’t a bug, it’s SQL Server enforcing correctness: one session holds a lock, another wants a conflicting one, and it has to wait. Most blocking resolves in milliseconds and nobody notices. The problem is blocking that doesn’t resolve fast, a query queued behind a session that’s holding a lock far longer than it should,…
🚨Part of the SQL Server Errors series, the exact messages and what actually causes them.Related pillar: Blocking & Locking What Msg 1205 Says Msg 1205 · Level 13 · State 51 Transaction (Process ID 93) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. ⚡The…
🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Migration & Deployment From Finding Orphaned Users to Actually Fixing Them Restored a database onto another server and the application now gets Cannot open database “…” requested by the login. The login failed., even though its user is still in the database? The…
🔧Part of the DBA-Tools Project, copy/paste SQL Server scripts and health checks.In: Backup & Recovery A Backup You’ve Never Restored Is a Guess, Not a Plan Every DBA can point to a backup schedule. Far fewer can point to proof that any of those backups actually restore. A backup job finishing green tells you the…