2011-04-05 15:47:56.62 spid2 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15
2011-04-05 15:53:03.15 spid77 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15
2011-04-05 16:02:16.62 spid2 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15
2011-04-05 16:07:28.56 spid110 SQL Server has encountered 62 occurrence(s) of IO requests taking longer than 1
2011-04-05 16:33:07.62 spid2 SQL Server has encountered 1 occurrence(s) of IO requests taking longer than 15
2011-04-05 16:38:07.98 spid115 SQL Server has encountered 68 occurrence(s) of IO requests taking longer than 1
数据库出错，请帮忙解决呀! SQL Server has encountered 1 occurrence(s) of IO requests taking longer t
答案:4 悬赏:10 手机版
解决时间 2021-04-12 17:19
- 提问者网友：戎马万世
- 2021-04-11 16:58
最佳答案
- 五星知识达人网友：想偏头吻你
- 2021-04-11 18:07
A database management system (DBMS), such as SQL Server, relies on the timeliness of file input and output (I/O) operations. Any one of the following items may create stuck or stalled I/O problems. These problems can quickly have an adverse affect on SQL Server responsiveness and performance:
Faulty hardware
Hardware that is not configured correctly
Firmware settings
Filter drivers
Compression
Bugs
Other conditions in the I/O path
These I/O problems may cause the following behavior to occur:
Blocking
Latch contention and time-outs
Slow response time
Stretching of resource boundaries
Starting in Microsoft SQL Server 2000 Service Pack 4 (SP4), SQL Server includes logic that helps detect stalled and stuck conditions for database I/O reads and writes and log file I/O reads and writes. When an I/O operation has been pending for 15 seconds or longer, SQL Server performs the following steps:
Detects that the operation has been pending.
Writes an informational message to the SQL Server error log. The text of the message is similar to the following:
2004-11-11 00:21:25.26 spid1 SQL Server has encountered 192 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [E:\SEDATA\stressdb5.ndf] in database [stressdb] (7). The OS file handle is 0x00000000000074D4. The offset of the latest long IO is: 0x00000000022000”.
Faulty hardware
Hardware that is not configured correctly
Firmware settings
Filter drivers
Compression
Bugs
Other conditions in the I/O path
These I/O problems may cause the following behavior to occur:
Blocking
Latch contention and time-outs
Slow response time
Stretching of resource boundaries
Starting in Microsoft SQL Server 2000 Service Pack 4 (SP4), SQL Server includes logic that helps detect stalled and stuck conditions for database I/O reads and writes and log file I/O reads and writes. When an I/O operation has been pending for 15 seconds or longer, SQL Server performs the following steps:
Detects that the operation has been pending.
Writes an informational message to the SQL Server error log. The text of the message is similar to the following:
2004-11-11 00:21:25.26 spid1 SQL Server has encountered 192 occurrence(s) of IO requests taking longer than 15 seconds to complete on file [E:\SEDATA\stressdb5.ndf] in database [stressdb] (7). The OS file handle is 0x00000000000074D4. The offset of the latest long IO is: 0x00000000022000”.
全部回答
- 1楼网友：英雄的欲望
- 2021-04-11 22:09
重启服务看看，应该可以，
- 2楼网友：污到你湿
- 2021-04-11 21:07
是不是冲突了
重新启动一下服务试试
- 3楼网友：轮獄道
- 2021-04-11 19:31
你好！
的说RAID能不能提高数据库的访问能力。
RAID不会影响客户端的软件程序。
打字不易，采纳哦！
我要举报
如以上回答内容为低俗、色情、不良、暴力、侵权、涉及违法等信息，可以点下面链接进行举报！
点此我要举报以上问答信息
大家都在看
推荐资讯