I was reading the [Handling Deadlocks][1] page and I came upon this quote-> Implementing an error handler that traps error message 1205 allows an application to handle the deadlock situation and take remedial action (for example, automatically resubmitting the query that was involved in the deadlock). By resubmitting the query automatically, the user does not need to know that a deadlock occurred.
My problem is that I have several SSIS packages that run simultaneously and interact(Read/Write) with many of the common SQL Server physical tables between them. Many a time, the SQL processes/SSIS tasks in these packages enter into a deadlock state, and then one of the process inside one of those package is chosen as the victim with the 1205 error message, thereby failing that package. The remediation currently is to manually re-run the SSIS package/process that failed.
I would like to know how would the remedial action (automatically resubmit the query that was involved in the deadlock) be implemented inside SSIS package(s)?
[1]: https://technet.microsoft.com/en-us/library/ms177453(v=sql.105).aspx
↧