I'm running SQL Server 2000.  The SP is dynamically compiled, and is stored in 
memory on the DB.  The dynamic SP is accessed by handlers instead of actually 
calling the SP from disk (aka The true way).   But tomato, tomato.  (:) that 
doesn't type well does it?)

For the filter, I'm limiting my search to reads greater or equal to 5000.  

For the data columns, I'm selecting everything.

For the events, I'm selecting Security Audit: Audit login, logout; Sessions: 
ExistingConnection; Stored Procedures: All; TSQL: SQL:BatchCompleted.

Unfortunately, I'm still unable to trace back to the original query.  I'll run 
ethereal to sniff what's going to the DB & back to CF.  It'll give me an idea 
of what app is keeping track of the handler ID.  

I'll post results in a few hours.



>As noted, it is not an true SP in the way you have a pre-compiled set of SQL
>(it is not stored within the DB itself)- it is straight forward dynamic SQL.
>
>
>What version of SQL are you running? When you run a trace (not on a
>production server) you get a choice of what columns/params you want
>log...they can be as deep or as limited as possible....look at the Trace
>Settings/Options and see what you are actually logging,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246914
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to