Deadlock captures: "FETCH API_CURSOR..." but not query behind it......

Question

This article shows how to "unmask" the sql query behind a FECTH API_CUSOR
http://www.sqlskills.com/blogs/joe/hunting-down-the-origins-of-fetch-api_cursor-and-sp_cursorfetch/
that is shown in a deadlock graph. But if only applies if one can capture the event while it is ongoing.  Is there a counter in Sql profier (2005) to indicate\capture the query behind the FETCH?  (because most of the time I find out about
deadlocks long after the victim spid has been killed.)
TIA,
edm2
P.S.Of course it I captured every sql statement executed on the server that may do it but I'm trying not to overburden the server by collecting excessive info

Answer 1

Quite honestly you are hitting a very old and continuing problem:
If the original query is out of the system, for whatever reason (cash flushes etc), you cannot get if after the fact.
- when the alert/event notification occurs, it may be too late
If you are hitting this problem frequently you indeed have to set up a trace which captures all possible initiators statements, just to have them once the deadlock occurs.
I don't see the version of SQL Server you are using, but from 2012 on you can stick to Extended Events for such. Otherwise, yes, get a SQL Trace (no Profiler/GUI) in place.
Deadlocks are captured by default from SQL 2008 on, and in 2012 you have all events available - in 2008 some that you may need might not be there yet.
Andreas Wolter
Microsoft Certified Master SQL Server 2008
Microsoft Certified Solutions Master SQL Data Platform, SQL Server 2012
Blog: www.insidesql.org/blogs/andreaswolter
Web: www.andreas-wolter.com |
www.SarpedonQualityLab.com