Hello,
I have been reading up on the causes of having a processes go into sleeping status and display a PAGEIOLATCH_SH in the wait type column, as far as I can see it references a lack of memory available to process the request.
Oddly the process will run for a while then go into the sleep status for about 10 min the continue running the request. the process does this for over an hour.
I have checked for memory locks and it looks fine, also SQL process is not utilizing the maximum amount of memory available to SQL.
another thing I have been seeing in he PERFMON is the spiking of the Read and Write per sec on the Physical disks
I have the sever setup in a RAID 0 + 1 configuration
1 disk for OS and SQL
2 disks for data file
2 disks for log files
I have all tables that are involved in the INSERT index with non-clustered indexes.
any ideas on what’s going on or how I may correct this issue
thanks
talenx
I have been reading up on the causes of having a processes go into sleeping status and display a PAGEIOLATCH_SH in the wait type column, as far as I can see it references a lack of memory available to process the request.
Oddly the process will run for a while then go into the sleep status for about 10 min the continue running the request. the process does this for over an hour.
I have checked for memory locks and it looks fine, also SQL process is not utilizing the maximum amount of memory available to SQL.
another thing I have been seeing in he PERFMON is the spiking of the Read and Write per sec on the Physical disks
I have the sever setup in a RAID 0 + 1 configuration
1 disk for OS and SQL
2 disks for data file
2 disks for log files
I have all tables that are involved in the INSERT index with non-clustered indexes.
any ideas on what’s going on or how I may correct this issue
thanks
talenx