Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
carumuga
Posting Yak Master
174 Posts |
 Posted - 2009-11-18 : 07:58:43
|
| Hi,My SSIS Package was running for a while and on overlooking the log file, the process id 64 was deadlocked and i killed the process manually before rerunning the job again.Now, I want to identify the query that belongs to Process ID 64 in order to know the root cause of the issue. How do i get it?Thanks in advance. |
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2009-11-18 : 08:28:39
|
| It's a pretty horrible process. I don't think you can after the fact. I've got a very similar problem with scheduled jobs randomly deadlocking.In 2005 and up you can issue a try catch block if you know which segment of code is likely to deadlock. You can then catch the deadlock and query some system tables. To get the info out I've been using sending an email to myself with the details.There's a much more complete way with service broker that madhivanan (I think) has written a good guide for but I don't use service broker.If there IS any way to find out what a particular process was doing after it has been killed then I'd love to see it.Charlie===============================================================Msg 3903, Level 16, State 1, Line 1736The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION |
 |
|
|
|
|
|
Process - Query