March 12, 2009 at 11:21 am
Toward the end of the "TechEd - IO and Wait Stats" article By Steve Jones of 06-11-2008 there is a statement saying "ASync_NETWORK_IO - client isn't getting data as quickly as SQL sends. May be network issues, but likely the client is to blame."
We are experiencing an issue with one of our applications (vendor written/poorly supported) since moving the backend database from SQL 2000 to SQL 2005. When our users submit a particular request for data and they do not enter a date range in the provided form, we get a suspended process with a ASYNC_NETWORK_IO wait type. We have to manually kill the process to remove it from the server. The suspension did not occur in SQL 2000.
Can you please explain why you say "..., but likely the client is to blame" so we can get a better understanding of how to go about mitigating this issue?
March 12, 2009 at 11:41 am
Link to the online article
http://www.sqlservercentral.com/blogs/steve_jones/archive/2008/06/11/teched-io-and-wait-stats.aspx
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply