September 8, 2008 at 9:26 am
We have a sql server 2000 db that is being accessed from multiple web servers (external clients) through stored proc calls. There are times when we experience latency within a proc when a specific statement hangs up that we need to troubleshoot ASAP. In these cases I grab the problem SPID and HOSTNAME from SP_WHO and the offending stored proc name from DBCC INPUTBUFFER. What would really be helpful is to get the full RPC call, with parameter values, from within Query Analyzer. I know I can get it from Profiler, however, if it's stuck on a specific statement it needs to progress before we can pick it up. Any ideas?
_____________________________________________________________________
- Nate
September 12, 2008 at 1:14 pm
Ok, found the answer to my question...stumbled across this link (below) in another discussion. Gives background of sysprocesses columns added through SQL Server 2000 SP3 and stored proc example to display the line of code that is currently being executed.
http://vyaskn.tripod.com/fn_get_sql.htm
_____________________________________________________________________
- Nate
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply