none
Concurrency errors RRS feed

  • Question

  • I have an application that's been running error free in production for over a year.

    It's doing sql updates/inserts/deletes using ado.net dataadapter using stored procedures to apply the updates.

    All of a sudden it started throwing concurrency exceptions all over the place. 

    We figured out that it was due to the nocount on being set in our update stored procedures and by

    setting nocount off the errors went away. 

    I have to answer the hard questions of how these errors came to be.

    Anybody know what kind of server change/patch or anything could have caused the 'sudden'

    appearance of these errors, barring any application code change or stored procedure changes?

     

    Thanks,

     

    Leigh

    Monday, November 5, 2007 4:27 PM

All replies

  • One thing to watch for is triggers.  Maybe someone added a trigger to a table that this application is using?

     

    Generally, all triggers should have a SET NOCOUNT ON as the first thing they do.  Otherwise, they may conflict with the way SqlDataAdapters work.

     

    Tuesday, November 6, 2007 3:44 AM
  • I just checked for triggers and there aren't any.

    Tuesday, November 6, 2007 1:39 PM