Post reply

ASYNC_Network_IO on BULK INSERT

  • April 13, 2015 at 4:28 am

    #295972

    Hi there,

    I'm seeing an issue with a "BULK INSERT" waiting on a ASYNC_Network_IO....Everywhere I look seems to say that its likely the application not keeping up with how quickly SQL is "returning" the query results. I can understand this with a SELECT but why would an application be waiting for responses from SQL on for an INSERT? Apologies if this seem like a silly question but its something that makes sense in part to me but articulating it is proving difficult 🙂

    Also is there anything I should be actively checking from a Network or Server level if it proves not to be application related?

    Thank you for any responses.

  • April 13, 2015 at 5:14 am

    #1790470

    It's usually kind of rare to see major network issues. Are doing the bulk load from an external source? I'd work with the network people to see if there's some sort of bottleneck occurring anywhere there, switches, firewalls, whatever.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

  • April 13, 2015 at 8:28 am

    #1790531

    Hi Grant,

    Thank you for the reply.

    We've already confirmed that the network is not under pressure during the wait times. Really what I'm trying to understand is does a Bulk insert send some information back to the client (from which is running)? I understand a SELECT will return a results to can see how that could tie in with the "application cannot keep up with SQL Server" argument but an Insert(bulk or otherwise)?

    Thanks

  • April 13, 2015 at 8:53 am

    #1790543

    Yeah, it absolutely sends confirmation messages back. I wouldn't imagine that those, under most circumstances, are going to cause huge performance issues, but they absolutely do happen.

    ----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply