ASYNC Network IO error in calls from one server to linked server
Posted on 2011-05-10
I am not a DBA, I am expericanced coding TSQL and dealing with the more software oriented tasks.
We have 2 servers. Server A is 2008, Server B is 2005. Up until this morning when all heck broke loose on our network everything was working fine. After our network engineers "fixed" the problem everything is working except this one thing (so far). A stored procedure that returns data to a webapplication was working fine on Server A, is not longer working. The stored procedure selects data from Server B using synonyms, along with tables existing on ServerA When the stored procedure runs now Server B locks up with ASYNC network IO waits.
I moved the procedure completely over to Server B, including copies of the tables on Sever A and it works fine now.
I think that possibly the problem has to do with Server A's network settings or maybe even the hardware. From what I understand with the Network IO error it has to do with the ability of the client to accept the data.
So, basically I'm looking for opinions or ideas for what to look into.
I beleive something has gone wrong with