• Thanks I will try and see what I get, but not sure that it will show much if I am just checking for deadlocks. All the job (at that step does) is copy records from one table to update a different table. PerfMon did not show anything abnormal (CPU,Mem,Phy IO), so my guess is that a user was in making changes to the forecast and did not file the screen... but that is just a guess. If I am right it would not have created a deadlock, just blocking.