PAGEIOLATCH_XX Wait
Usually caused by IO outside of the SQL Server in the underlying operating System.
Suggestions:
- Increase memory on your SQL Server so that more of the database remains in memory and does not need to be paged in and out of memory.
- Increase the drive speed on your disk system.
- Add a second drive system and shift the logs or part of the database to that other disk.
- Check for missing indexes or eliminate duplicate indexes to avoid excess paging.
From Book On-Line:
PAGEIOLATCH_DT
Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Destroy mode. Long waits may indicate problems with the disk subsystem.
PAGEIOLATCH_EX
Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Exclusive mode. Long waits may indicate problems with the disk subsystem.
PAGEIOLATCH_KP
Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Keep mode. Long waits may indicate problems with the disk subsystem.
PAGEIOLATCH_SH
Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Shared mode. Long waits may indicate problems with the disk subsystem.
PAGEIOLATCH_UP
Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Update mode. Long waits may indicate problems with the disk subsystem.
Enroll Today!
![SteveStedman5](http://databasehealth.com/wp-content/uploads/2021/10/DHMimage1-1.png)
![SteveStedman5](https://stevestedman.com/wp-content/uploads/2021/03/button-16.png)
Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!
Leave a Reply