This wait type accumulates while SQL Server is waiting for a page to be retrieved from disk and loaded into memory. The page collected will be used for an exclusive purpose (read or write operations). If this value is high it is likely that disk or available memory are not keeping up with the workload

Resolved by


Suggested solutions

  1. Add additional memory
  2. Investigate disk latency
  3. Increase the maximum memory allocation
  4. Indexing, look for high disk I/O queries
  5. Enable data page compression if CPU usage is not suffering

Additional research

PAGEIOLATCH_SH and how to reduce it
SQL Authority: PAGEIOLATCH Waits

⇐ Back to index