The storage team asks which query hit the disks. Here is how to answer with physical reads, and why the answer depends on how you rank them.
Capping File Growth So One Query Cannot Fill a Whole Disk
One runaway load can fill a shared drive and take every database down with it. A MAXSIZE cap moves the failure to one database.
SQL SERVER – Disk Space Monitoring – Detecting Low Disk Space on Server
A common question I get: how do you go about detecting low disk space on SQL Server? Here are two ways, including xp_fixeddrives, and the one I prefer.
Choosing Hardware for SQL Server Now
Choosing hardware for SQL Server Now means matching core cost, memory, and storage latency to measured workload needs and future growth.
Reading Pending I/O Requests During a Storage Slowdown
Sample pending I/O requests during PAGEIOLATCH or WRITELOG stalls, map each request to a file, and share timed evidence.
Finding Orphaned Data and Log Files Nobody Attached
Inventory orphaned data and log files by comparing data-folder contents with sys.master_files, then review candidates before cleanup.
PAGEIOLATCH_SH Waits: Slow Storage or Too Many Reads
Diagnose PAGEIOLATCH_SH waits by comparing file read latency with Query Store physical reads before blaming storage or changing indexes.