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 a shared purpose (read operation). If this value is high it is likely disk or memory available 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

Handling excessive SQL Server PAGEIOLATCH_SH wait types
Knee-Jerk Wait Statistics : PAGEIOLATCH_SH
SQL Authority: PAGEIOLATCH Waits

⇐ Back to index