ASYNC_NETWORK_IO 426123.522000 Seconds
In the last two months, SQL Server has spent 118 hrs 22 min 3 sec waiting for Sage 300 to process data.
A Query with 31k rows is returned by SQL Server in only a few ms, but SQL is waiting for 2,5 hours for the application to receive these results while keeping a lock on the table during this duration, rendering Sage 300 unusable for all users during this wait.
ASYNC_Network waits are not hardware related but rather caused by the application due to inefficient querying and processing of data. On very rare occasions, they can be related to the network, but this is not the case here.
In regards to Sage 300, the reason is that calculations are made on each row in the package before the next package is requested from the server, rather than waiting for all the data to reach the client before processing the results.
Since there are locks on the tables until the queries are finished and all data is sent, and in some cases even until the UI’s are closed, this impedes the ability of all users using the software.
by: Tomas B. | over a year ago | General Enhancements
Comments
I agree
I agree
I agree
Posted June 2022.
Agree that is is using RBAR (Row by Agonsign Row).
Disagree that this locks users out. It doesnt, mostly.