Microsoft
<div class="msame_Header msame_unauth" role="button" tabindex="0" aria-label="请登录你的帐户" title="请登录你的帐户" data-mc-m="{"id":"headerClick","aN":"Me Control Header","cT":"Button"}" "="" style="box-sizing: inherit; outline: none; display: -webkit-inline-flex; cursor: pointer; font-size: 14px; border-width: 1px; border-style: solid solid none; border-color: transparent; width: 56px; border-image: initial; min-width: 56px; position: relative; z-index: 3000001; height: 48px;">
请登录你的帐户
登录
Symptoms
When I/O requests take longer than 15 seconds, Microsoft SQL Server reports "Msg 833" to the event log, and the following text is logged in the ERRORLOG file:
Other symptoms may occur, such as the following:
Other symptoms may occur, such as the following:
- High wait times for PAGEIOLATCH waits
- Errors in the System event log
Note For more information about typical errors that Microsoft has recorded and that could accompany this SQL Server message, click the following article number to view the article in the Microsoft Knowledge Base:2091098 Windows System Event Log Errors that indicate possible I/O problems can be associated with database inconsistency or performance problems for SQL Server - Indications of disk latency problems from performance monitor counters such as disk secs/transfer
Cause
This problem is caused by some issue in the operating system, by device drivers, by firmware, or by hardware that is used to support the devices to store SQL Server database and/or transaction log files. SQL Server records the time that it initiated an I/O request and records the time that the I/O was completed. If that difference is 15 seconds or more, this condition is detected. This also means that SQL Server is not the cause of a delayed I/O condition that this message describes and reports.
Resolution
A problem exists in the system I/O path that causes an I/O to be delayed for 15 seconds or longer. Therefore, you should use the necessary methods and techniques to determine the cause of the delay in the operating system, with the drivers, or with the I/O hardware. Resolution of this problem could involve updating all device drivers and firmware or performing other diagnostics that are associated with your disk system.
More Information
This condition is generally known as "stalled I/O." Most disk requests occur within the typical speed of the disk. This typical disk speed is frequently known as "disk seek time." Disk seek time for most standard disks occurs in 10 milliseconds or less. Therefore, 15 seconds is a very long time for the system I/O path to return to the SQL Server.
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table :
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table :
| Rule software | Rule title | Rule description | Product versions against which the rule is evaluated |
| SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) |
I/O Delay Problems reported by SQL Server |
The Microsoft SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect whether SQL Server reports "Msg 833." The SQL Server 2008 R2 BPA supports both Microsoft SQL Server 2008 and SQL Server 2008 R2. Consider the following scenario. You run the BPA tool, and the tool detects that an Event ID 833 is logged in the Application log. Also, the tool detects that this event has a Source that contains the instance name of the SQL Server. In this scenario, you see a warning in the BPA tool that has the following title: Engine - I/O Delay Problems reported by SQL ServerBPA does not filter on any date or time. Therefore, BPA reports the number of occurrences of Event ID 833 in the current Application log. |
SQL Server 2008 SQL Server 2008 R2 |
| SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) |
I/O Delay Problems reported by SQL Server |
The Microsoft SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect whether SQL Server reports "Msg 833."Consider the following scenario. You run the BPA tool, and the tool detects that an Event ID 833 is logged in the Application log. Also, the tool detects that this event has a Source that contains the instance name of the SQL Server. In this scenario, you see a warning in the BPA tool that has the following title: Engine - I/O Delay Problems reported by SQL ServerBPA does not filter on any date or time. Therefore, BPA reports the number of occurrences of Event ID 833 in the current Application log. |
SQL Server 2012 |
上次更新时间：2012年7月9日
这是否解决了你的问题？
是
否
Microsoft
<div class="msame_Header msame_unauth" role="button" tabindex="0" aria-label="请登录你的帐户" title="请登录你的帐户" data-mc-m="{"id":"headerClick","aN":"Me Control Header","cT":"Button"}" "="" style="box-sizing: inherit; outline: none; display: -webkit-inline-flex; cursor: pointer; font-size: 14px; border-width: 1px; border-style: solid solid none; border-color: transparent; width: 56px; border-image: initial; min-width: 56px; position: relative; z-index: 3000001; height: 48px;">
请登录你的帐户
登录
Symptoms
When I/O requests take longer than 15 seconds, Microsoft SQL Server reports "Msg 833" to the event log, and the following text is logged in the ERRORLOG file:
Other symptoms may occur, such as the following:
Other symptoms may occur, such as the following:
- High wait times for PAGEIOLATCH waits
- Errors in the System event log
Note For more information about typical errors that Microsoft has recorded and that could accompany this SQL Server message, click the following article number to view the article in the Microsoft Knowledge Base:2091098 Windows System Event Log Errors that indicate possible I/O problems can be associated with database inconsistency or performance problems for SQL Server - Indications of disk latency problems from performance monitor counters such as disk secs/transfer
Cause
This problem is caused by some issue in the operating system, by device drivers, by firmware, or by hardware that is used to support the devices to store SQL Server database and/or transaction log files. SQL Server records the time that it initiated an I/O request and records the time that the I/O was completed. If that difference is 15 seconds or more, this condition is detected. This also means that SQL Server is not the cause of a delayed I/O condition that this message describes and reports.
Resolution
A problem exists in the system I/O path that causes an I/O to be delayed for 15 seconds or longer. Therefore, you should use the necessary methods and techniques to determine the cause of the delay in the operating system, with the drivers, or with the I/O hardware. Resolution of this problem could involve updating all device drivers and firmware or performing other diagnostics that are associated with your disk system.
More Information
This condition is generally known as "stalled I/O." Most disk requests occur within the typical speed of the disk. This typical disk speed is frequently known as "disk seek time." Disk seek time for most standard disks occurs in 10 milliseconds or less. Therefore, 15 seconds is a very long time for the system I/O path to return to the SQL Server.
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table :
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table :
| Rule software | Rule title | Rule description | Product versions against which the rule is evaluated |
| SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) |
I/O Delay Problems reported by SQL Server |
The Microsoft SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect whether SQL Server reports "Msg 833." The SQL Server 2008 R2 BPA supports both Microsoft SQL Server 2008 and SQL Server 2008 R2. Consider the following scenario. You run the BPA tool, and the tool detects that an Event ID 833 is logged in the Application log. Also, the tool detects that this event has a Source that contains the instance name of the SQL Server. In this scenario, you see a warning in the BPA tool that has the following title: Engine - I/O Delay Problems reported by SQL ServerBPA does not filter on any date or time. Therefore, BPA reports the number of occurrences of Event ID 833 in the current Application log. |
SQL Server 2008 SQL Server 2008 R2 |
| SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) |
I/O Delay Problems reported by SQL Server |
The Microsoft SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect whether SQL Server reports "Msg 833."Consider the following scenario. You run the BPA tool, and the tool detects that an Event ID 833 is logged in the Application log. Also, the tool detects that this event has a Source that contains the instance name of the SQL Server. In this scenario, you see a warning in the BPA tool that has the following title: Engine - I/O Delay Problems reported by SQL ServerBPA does not filter on any date or time. Therefore, BPA reports the number of occurrences of Event ID 833 in the current Application log. |
SQL Server 2012 |
上次更新时间：2012年7月9日
这是否解决了你的问题？
是
否