Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CanadaDBA
583 Posts |
 Posted - 2007-10-12 : 11:06:21
|
| My developers complain about errors and intrruptions from SQL Server on one of the servers. I checked the server's log and found there are error messages like as below:SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL\data\templog.ldf] in database [tempdb] (2). The OS file handle is 0x000003B8. The offset of the latest long IO is: 0x0000000006f000SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [E:\Program Files\Microsoft SQL Server\MSSQL\Data\WebDev.mdf] in database [WebDev] (28). The OS file handle is 0x00000558. The offset of the latest long IO is: 0000000000000000What is it related to? What should I do?Thanks,Canada DBA |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-10-12 : 11:10:02
|
Possible multiple-retries on the disk (eventually successful, but disk could be failing).Or RAID running slowly because it is rebuilding.Or rubbish hardware  |
 |
|
|
CanadaDBA
583 Posts |
Posted - 2007-10-12 : 12:41:31
|
| I think your last guess is correct :)The users get this error: "A transport-level error has occured when receiving results from the server. (provider: TCP Provider, error: 0-An existing connection was forcibly closed by the remote host."Canada DBA |
|
|
|
OldHippy
Starting Member
5 Posts |
Posted - 2007-10-12 : 16:08:04
|
| What is your disk configuration? Are log files on the same drives as your data files?It's possible you can move them away from the data files for better fault tolerance and performance.Mike |
|
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2007-10-12 : 16:14:58
|
| CanadaDBA, your first error message is a disk error and the second is a network error.We saw these on a system attached to a SCSI drive array (sorry, don't know the details). They churned through the log looking for any problems but never found anything. The problem never occurred again. No idea what caused it.=================================================Creating tomorrow's legacy systems today. One crisis at a time. |
|
|
|
|
|
|
IO delay error