I have a parent package which has three sequence containers which run independently ( for parallel process). Within each sequence container i call a package(same package). the called package has an execute sql task which calls update statement on a table. the update statement is based on a unique primary key and call to update has this key passed as parameter. the primary key is not repeated across the calls and are unique, but still the packages are failing with deadlocks. eg:- all are happening in parallel thread1 - update table set col=value where key=1 thread2 - update table set col=value where key=2 ( this update fails because of deadlock and other two run fine). thread3 - update table set col=value where key=3 Can you please suggest what is going on, i have tried making transaction level to "not supported " on all packages and containers and tasks, still i am getting issue.I have tried changing the escalation level to false, page locks to false, but still having issues.

Hi, have you tried to debugging the deadlock to check what resource is being the cause for the deadlock? Check the article below on how-to steps: Basic SQL Server Deadlock Debugging David.

thanks for the suggestion, i found the issue.

thanks for the suggestion, i found the issue. Please post it then... thanksSincerely SH -- MCITP , MCTS -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).

i ran the sql profiler, the problem was not in the table i was trying to do updates, there were multiple triggers defined on the source table which were doing the table lock on the target table. the issue is because of the triggers and not because of the update. the triggers were defined by prior team and does truncate and insert for every update on the source table... hope this explanation is okay, else i will post more details... for my testing i disabled the triggers and it ran fine..