Device Is Not Ready is the Windows text behind operating system error 21, which SQL Server reports inside error 823. This post explains what the message means, lists the common causes, and gives read-only checks to run before any restart. It ends with the DBCC CHECKDB step that proves the database is healthy.
Logging Free Space per Volume Into a Table Each Day
Log free space per volume from SQL Server volume metadata, keep one daily sample per mount point, and compare change with LAG.
Setup Error 1603: Patch Fails With Not Enough Disk Space on the Volume
Setup error 1603 appeared for three features in a SQL Server patch, all pointing to one component log. That log said Disk full: there is not enough disk space on the volume D. Freeing space on the drive was the corrective action.
Where is Table Variable Created? – Interview Question of the Week #243
Question: Where is Table Variable Created?
Answer: On Hard Disk and NOT in Memory.
I suggest you read the following blogs
IO Stalls by Database File: Find the File to Move
IO stalls measure how long SQL Server waited for the disk, file by file. This post ranks the files of a demo database by stall time, measures a workload with two snapshots, lists the busiest files of a whole instance, and explains how to pick the one file that belongs on the new drive.
Runnable vs Suspended: What Each sp_who2 Status Means
Runnable vs suspended is the question I hear most about the sp_who2 status column. A Runnable session waits for CPU, and a Suspended one waits for a resource such as I/O. Here are all five statuses in plain words.
SQL SERVER – Timeout Occurred While Waiting for Latch: Class FGCB_ADD_REMOVE
Latch FGCB_ADD_REMOVE timeouts mean a data file is growing slowly. Measured on SQL Server 2025: 4 GB of data in 98 ms, 4 GB of log in 2.3 seconds.