Announcement Announcement Module
No announcement yet.
PreparedStatement's and tracing Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • PreparedStatement's and tracing

    We are considering replacing an in-house JDBC framework with Spring JDBC. While the developers LOVE Spring JDBC, our DBA's are worried about supportability. When performing database-level traces, the tracing tools (i.e. SQL Profiler) don't display adequate information when prepared statements are used. We are using MS SQL 2005.

    While Spring JDBC provides excellent logging, our data volumes overflow the logs.

    The in-house JDBC framework deals with this issue by supporting an option that dynamically switches from prepared statements to dynamically generated SQL, purely for tracing purposes.

    Does the Spring JDBC have techniques to help alleviate issues with prepared statement tracing?