CODEWITHSUNDEEP
sqlsql-serverdeadlock
jgemedina
jgemedina

Reputation: 526

Can a deadlock in a databases affect other databases or hung entire server?

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?

Upvotes: 2

Views: 1858

Answers (3)

Phill Wade
Phill Wade

Reputation: 21

I have seen this happen when two processes that are in a deadlock also have objects locked in TempDB.

The locked objects in tempdb then stop other processes from being able to create objects and thus hang.

This was an issue on older versions of SQL Server (2000), but I can't recall seeing it on more recent version.

Upvotes: 2

Mark Brackett
Mark Brackett

Reputation: 85665

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.

Upvotes: 4

Alex
Alex

Reputation: 1957

it is possible. if your server can't react to any interupt it can't execute other requests (correctly).

Upvotes: 0

Related Questions