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 |
|
jmilora
Starting Member
1 Post |
 Posted - 2008-01-11 : 11:03:25
|
| Hi all,We've been experiencing application lock ups lately at a rate of once or twice a day. The application hangs, which I can correct quickly by killing the process on the database that is holding the locks. I know there are some architecture issues that need to be fixed on the application side, but right now I just want to identify the sql being executed by the blocking process. I've tried looking at syscacheobjects but I don't know how to resolve the bucketid to user process id.Is there a way, short of using the profiler tool, to identify the sql being executed by a user process in sql server 2000? Thanks. |
|
|
jstormoen
Starting Member
30 Posts |
Posted - 2008-01-11 : 11:54:44
|
| the DBCC inputbuffer allows you to see the last SQL statements run for a specified spid. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-12 : 12:38:30
|
| Or 'sp_who2 active'. |
|
|
|
|
|
|
Tracing sql to a process