Useful intro on identifying deadlocks.

The part that concerned me more was:

"As part of the upgrade, the application team performed modifications to the stored procedure code such that every insertion may cause up to 10 updates in the table."

Why would so many updates need to happen on the same table from a single insert? The sprocs/functions used in between must be low level and small to have caused so many updates?

If it's status updates, that's ALOT of status updates.

I guess as long as the code works now and it's no deadlocking it's ok?