This sounds pretty strange, but there is ocurring in a databases of a bunch we’ve got in a server, we can tell by the output on the log, but this seems to be affecting another databases, since the systems hungs when the deadlock occur.
We’ve identified the objects involved in the deadlock event, but none lives in the databases from the system we are using.
I still need to look at the procedure bodies, but is this possible? processes from other databases entering in deadlock and hunging the entire server or other databases?
A deadlock is not a fatal event in MS Sql Server (unlike, eg., in code). This is because Sql Server will periodically scan for deadlocks, and then pick one of the of the processes to kill. That’s when you get the log messages.
Absent a Sql Server bug (which I’ve never encountered), I’d think it’s more likely that the order is reversed – the hung server/database prevents normal execution of queries, resulting in deadlocks as procedures take longer to execute.