Wow, that's an impressive deadlock. Was that a once off, or is it reoccurring?

I would suggest that you enable either 1204 or 1222, not both. They have the same purpose, just different output formats.

Now, what can be gleaned from this:

Node 1:

procedure sps_SERVER_IProcessing_Day 2456 'FTWSTKSQL02' deadlocked on Line #: 347, doing an update. Resource: Page 7:1:1930780

To find the table involved, run the following

DBCC TRACEON (3604) -- output to client

DBCC PAGE (7,1,1930780) -- dump page headers

DBCC TRACEFF (3604)

You will see a lot of info from the page headers. Look for the object ID, then run SELECT OBJECT_NAME(<ObjectID>) in the database that this lot is in.

Node 4 - executing a procedure with the ID 345678234. Deadlocked on line 734 doing an update. Resource on key 7:72057600365101056

To find the name of the proc, run SELECT OBJECT_NAME(345678234)

To find the table it was deadlocking on, run the following

select o.name

from sys.partitions p

inner join sys.objects o on p.object_id = o.object_id

where p.partition_id = 72057600365101056

Node:5 - deadlocked on PAGE: 7:1:1594571

Can't see the input buffer. Use same method as for node 1 to locate the table.

Node 7, I'm not sure how to interpret. There are references to stored procs that you could check.

SERVER.dbo.sps_SERVER_Processing_Day line=41

SERVER.dbo.sps_SERVER_ImportProcessing line=776

SERVER.dbo.sps_SERVER_UpdateExceptions line=117

Could be a stack trace.

The resource it mentions is the same as for node 4 - key 7:72057600365101056

Does that help at all?

Also, 700 line long stored procs? :ermm: