August 31, 2011 at 5:53 am
Our database has just moved servers and I noticed that via SQl profiler the application's SQL is now enclosed in sp_executesql. How can I stop this?
Many thanks
August 31, 2011 at 6:03 am
Wild guess: it's a Java application, isn't it?
If so, there are connection properties that handle how the statements are submitted to the RDBMS.
If not... can you share more details please?
-- Gianluca Sartori
August 31, 2011 at 6:14 am
Yes its!!! coming through a jboss layer
August 31, 2011 at 6:22 am
Edward-445599 (8/31/2011)
Yes its!!! coming through a jboss layer
😀
OK, what's the jdbc driver? JTDS or Microsoft's?
-- Gianluca Sartori
August 31, 2011 at 7:26 am
Gianluca Sartori (8/31/2011)
Edward-445599 (8/31/2011)
Yes its!!! coming through a jboss layer😀
OK, what's the jdbc driver? JTDS or Microsoft's?
ITS JDBC . many thanks
August 31, 2011 at 7:34 am
Edward-445599 (8/31/2011)
Gianluca Sartori (8/31/2011)
Edward-445599 (8/31/2011)
Yes its!!! coming through a jboss layer😀
OK, what's the jdbc driver? JTDS or Microsoft's?
ITS JDBC . many thanks
OK, which driver?
-- Gianluca Sartori
August 31, 2011 at 7:36 am
sorry jtds
August 31, 2011 at 7:44 am
See http://jtds.sourceforge.net/faq.html.
The property to set in the connection string is "prepareSQL". To leave the original SQL untouched, you can set it to 0.
-- Gianluca Sartori
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply