Description

This wait type accumulates while SQL Server is waiting for a page to be retrieved from disk and loaded into memory. The page collected while SQL Server is still determining the level of latch the page requires, this can occur in Read-Ahead operations. If this value is high it is likely that disk or available memory are not keeping up with the workload

Resolved by

DBAs

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

SQL Authority: PAGEIOLATCH Waits

⇐ Back to index