Ken Henderson's WebLog

Stalled/stuck I/O and SQL Server 2000 SP4

Service Pack 4 for SQL Server 2000, due out any day now, has a number of new features oriented toward making the product easier to support.  One of these is the new detection and reporting of stalled or stuck I/O operations.  A stalled I/O is an I/O operation that SQL Server has submitted to the operating system and is taking an inordinant amount time to complete.  A stuck I/O is an I/O operation that has been submitted by the server to the OS and never completes.  Usually, these types of problems are due to either driver problems or hardware problems -- that is, they're completely outside of SQL Server.  They're notoriously difficult to debug and troubleshoot.  To the typical SQL Server end user, they manifest themselves as poor performance or what seems like a hang.  SP4 features detection and reporting of these conditions via messages written to the error log.  My next column in MSDN Magazine (also due out any day now) will give you the details and lay out some example scenarios where the new functionality makes all the difference.
Published Sunday, April 17, 2005 3:07 PM by khen1234

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

sarai alamgir said:

neatly and wisely elaborrated. Thanks.
May 24, 2005 5:28 AM
 

R.Prakash said:

Nil is the best comm
August 16, 2005 5:17 AM

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Submit

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker