|
Posted by birju on 10/02/85 11:49
Erland Sommarskog wrote:
> As far as I know, it should be enough to kill that connection. But it sounds
> strange that there is no sp_prepare. It could be the case that the
> sp_prepare is filtered out for some reason?
The statement is prepared before I start the profiler and the client
keeps that connection - so I can't see its preparation without
restarting the server (it's a web application).
> By the way, if you don't see the query text, how do you know that it's
> the execution of a stored procedure? Stored procedure calls should be
> called through RPC, and RPC calls are not prepared...
Sorry, my bad! It was a prepared statment I was referring to and not a
stored procedure.
What I had to do was copy the database somewhere else and run the
application there so could restart it at will and see the statement
getting prepared.
I never thought about killing the connection - it was a bit too obvious
for me!
Many thanks,
Birju
Navigation:
[Reply to this message]
|