SQL Server Performance Forum – Threads Archive

I/O issue

I have this error in SQL server log ** Message SQL Server has encountered 33 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [N:Microsoft SQL ServerDATABizTalkDTADbBizTalkDTADb_Data2.ndf] in database [BizTalkDTADb] (<img src=’/community/emoticons/emotion-11.gif’ alt=’8)’ />. The OS file handle is 0x000008BC. The offset of the latest long I/O is: 0x0000001d48e000 ** can anyone help me make understand why I am getting this error. I am not familiar with this error. any help is appreciated thanks in advance sam

SQL Server 2000 SP4 includes logic for database and log file I/Os (reads and writes) to detect stalled and stuck conditions. When an I/O operation has been pending completion for 15 or more seconds, SQL Server detects this and reports the condition. Detecting and Resolving Stalled and Stuck I/O Issues in SQL Server 2000 SP 4
http://msdn2.microsoft.com/en-us/library/aa175396(SQL.80).aspx Mohammed U.

Anyways this a warning, not an Error. Roji. P. Thomas
SQL Server MVP
http://toponewithties.blogspot.com

And also I would check for any tempdb contention at the same time, have a health check of performance to ensure nothing is wrong at this time. Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing. The greatest discovery of my generation is that a human being can alter his life by altering his attitudes of mind.

forgot to mention that i am running sql server 2005 on that machine

Z – what type of disks are you using on this box? If you get a *few* of these errors it’s normal – normally when the disks are thrashing heavily due to heavy disk activity. Eg. transactional replication with distributor on same box can give these errors. BUT – be warned – I saw these errors recently on one of our live boxes and it was an early indication of disk controller failure. We swapped out the disks, swapped everything until we found the culprit (the ICP RAID card apparently) – since that’s been changed we hardly ever get these errors now. If you have a RAID controller – check the RAID error log to see if the disks are becoming corrupt.

]]>