Results 1 to 6 of 6
  1. #1
    Join Date
    Oct 2003
    Posts
    268

    Unanswered: Wait Type: NETWORKIO

    I have an ASP.NET web application that hangs on a single database UPDATE command for 5+ minutes. I can see this occur in SQL Profiler. This is a one row UPDATE statement on a small table (~600 rows). There are no JOINs or sub queries. There are no other users using the system. During this 5+ minutes, I can see the job in Enterprise Manager with a wait type of NETWORKIO. Since both IIS And SQL Server are running on the same system, the network shouldn't be an issue. Any ideas?

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    Typically, a waittype of NETWORKIO means that SQL Server is waiting on the front end application to do something. I have seen this much more often with programs that loop through a record set. The select statement that generates the recordset must wait for the program to say "OK, I have all the data, now. You can close out." I am not sure how this would happen with an update statement, though.

  3. #3
    Join Date
    Dec 2004
    Location
    CA, USA
    Posts
    63
    See http://sqldev.net/misc/waittypes.htm

    Has interesting comment on this wait type.

  4. #4
    Join Date
    Feb 2005
    Posts
    1

    Check this hotfix

    http://support.microsoft.com/kb/884554 - Just ran across this problem myself.

  5. #5
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    Won't have this problem if they only had execute to stored procedures
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  6. #6
    Join Date
    Jan 2005
    Location
    TempDb
    Posts
    228
    First, Note These symptoms are the same as the symptoms that are seen when a client application does not fully fetch query results. Incomplete result set processing is a much more common cause of the symptoms. In other words, this hotfix won't fix poorly designed applications.

    Next, the total size (width x height or rowsize x rows) is what matters.

    Finally, see http://www.dbforums.com/showthread.php?t=1089583 for more information on what you may be experiencing.
    Last edited by MaxA; 02-09-05 at 00:19.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •