I am getting complaints from our DBAs that they cannot turn on the sql profiler like they normally do and view the sql statements coming across from our app which is using hibernate. Everything just shows as a sp_prepare. Has anyone figured out a workaround for this??

What I am doing now is turning on tracing in our app and shipping the DBAs the logs but this is tedious/painful.

Any suggestions/help is MUCH appreciated.

Thanks!

is it a ms sql server? have you tested it with another jdbc driver?

using google I found alot of stuff regarding sp_prepare and it all looked good (sp_prepare indicates that statements are being reused = better performance)

Since I was doing this anyway out of personal interest im going to paste the links here (but try to use google ;)

Search for sp_prepare on each of these pages:

http://www.dbforumz.com/JDBC%20Driver-P ... 54125.html

http://jtds.sourceforge.net/faq.html

http://groups.google.com/group/microsof ... 13a18f3f5b

so apparently the sp_prepare has a preceding number which can be linked to a sp_execute ...but it seems to require having a full trace....