I/O requests taking longer than 15 seconds to complete

We get below error in MS SQL 2005 server which is fail over virtual server on
windows 2000 advanced servers clusterring.
SQL Server has encountered 16 occurrence(s) of I/O requests taking longer
than 15 seconds to complete on file [Y:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file
handle is 0x00000768. The offset of the latest long I/O is: 0x00000000652000
..
what is the cause and solution ?
NOTE:- 1- there are no sql 2005 service packs installed.
2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
updated upto date .
3- this error is generated on application peak hours .
This blog entry explains the error and offers suggestions
for addressing the issue:
http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
-Sue
On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
<maslooki@.discussions.microsoft.com> wrote:

>We get below error in MS SQL 2005 server which is fail over virtual server on
>windows 2000 advanced servers clusterring.
>SQL Server has encountered 16 occurrence(s) of I/O requests taking longer
>than 15 seconds to complete on file [Y:\Microsoft SQL
>Server\MSSQL.1\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file
>handle is 0x00000768. The offset of the latest long I/O is: 0x00000000652000
>.
>what is the cause and solution ?
>NOTE:- 1- there are no sql 2005 service packs installed.
>2- all HP Servers hardwares and HP SAN Storage drivers and firmwares are
>updated upto date .
>3- this error is generated on application peak hours .
>
|||Thank you MR.Sue Hoegemeier for reply
We also get the below error on the application side :-
" Transaction (Process ID 57) was deadlocked on lock resources with another
process and has been chosen as the deadlock victim. Return the transaction. "
Please again what is the cause and solution for this error ?
Note :- This happens on peak hours when they generate Reports and upload
transactions .
Thanks for cooperation
"Sue Hoegemeier" wrote:

> This blog entry explains the error and offers suggestions
> for addressing the issue:
> http://blogs.msdn.com/sqlserverstorageengine/archive/2006/06/21/642314.aspx
> -Sue
> On Mon, 19 Mar 2007 03:02:11 -0700, maslooki
> <maslooki@.discussions.microsoft.com> wrote:
>
>
|||You may consider ensuring that your reporting queries (I assume SELECT only)
use snapshot isolation level. Better still would be to replicate or mirror
to a reporting server which will handle the queries independent of the true
OLTP activity.
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
"maslooki" <maslooki@.discussions.microsoft.com> wrote in message
news:1D25A567-53FF-4667-9D3D-39F50D1F7FD7@.microsoft.com...[vbcol=seagreen]
> Thank you MR.Sue Hoegemeier for reply
> We also get the below error on the application side :-
> " Transaction (Process ID 57) was deadlocked on lock resources with
> another
> process and has been chosen as the deadlock victim. Return the
> transaction. "
> Please again what is the cause and solution for this error ?
> Note :- This happens on peak hours when they generate Reports and upload
> transactions .
> Thanks for cooperation
> "Sue Hoegemeier" wrote:
|||Thank you all,
Our programmers are working on it.
"Aaron Bertrand [SQL Server MVP]" wrote:

> You may consider ensuring that your reporting queries (I assume SELECT only)
> use snapshot isolation level. Better still would be to replicate or mirror
> to a reporting server which will handle the queries independent of the true
> OLTP activity.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>
>
> "maslooki" <maslooki@.discussions.microsoft.com> wrote in message
> news:1D25A567-53FF-4667-9D3D-39F50D1F7FD7@.microsoft.com...
>
>