Dear experts,
We are experiencing time-out expired in our .NET application accessing SQL Server 2005 database.
I have look around and using SQL Server 2005 Base Practice Analyzer I found critical error like this : "A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 41364<c/> committed (KB): 105592<c/> memory utilization: 39%." Actually I am not sure that this error cause the time-out error. Moreover the above error only occures at database startup process.
So far, I have added more datafiles to tempdb to 8 datafiles, because the server has 8 CPUs and applying trace flag T1118.
Other changes are:
- network packet size changed to 8060 (maximum allowed)
- remote query time out, changed to 0 (no time-out, or unlimited?)
- cursor threshold, changed to 500 (result set 500 and higher consider large)
But, the time-outs still happen.
We have several similar installations and this one is actually not the most busy database in terms of data volume or transaction volume, but no other having this problem.
Is it possible that the disk configuration (RAID-5) cause this?
The SQL Server 2005 SP3 64 bit is running on Windows Server 2008 R2 64-bit on 8 CPU machine. Please let me know if you need more information to help me find the root cause.
Thanks in advance.
Dapid Candra
