I support a dozen developers who use C++ Accessors and XML update grams
extensively. When I capture trace event data with Profiler I have a lot of
trouble finding what they are trying to do (and where :)) because most of the
queries are sequences similar to sp_CursorOpen, sp_CursorFetch,
sp_CursorOption, sp_Cursor, sp_CursorFetch, sp_Cursor, sp_CursorClose. I
need to find documentation (preferably a complete reference) on the
parameters and options associated with these calls so I can explain to the
developers what is happening.
For Example, what does "exec sp_cursor <id>, 40, 1" mean? How about "exec
sp_cursorOption <id>, 3, 4" or "exec sp_cursorFetch <id> 32, 1, 1?
Thanks
--
Ray Herring