Transaction Deadlock workbench error

Options

Good morning. I am curious if anyone has had this error before. One of our workbench jobs has been getting it more and more. I don't know if it is a domo workbench issue, or if it is an issue on the database side where we query the workbench job from

Error 40001 Microsoft ODBC SQL Server Driver SQL Server Transaction was deadlocked on lock resources with another process and has been chosen as the deadlock victim

Tagged:

Answers

  • ArborRose
    Options

    I haven't been using the ODBC driver myself. “Transaction was deadlocked” happen when 2 or more sessions are trying to lock a resource which has already locked by another session. The sessions cannot complete and SQL Server has to intervene. It gets rid of the deadlock by choosing one of the sessions as a victim and kills it allowing the other session to continue. The killed session is rolled back.

    ** Was this post helpful? Click Agree or Like below. **
    ** Did this solve your problem? Accept it as a solution! **