We noticed that performance wasn't stellar but didn't bother us that much because it was a background process then we were contacted by our DBA who informed us that each stored procedure call was spanning a second call to get metadata from the DB.
Obviously nowhere in our code do we make any such calls and no, we're not using any ORM framework that might be issuing them behind the scenes.
Here's our setup:
- Standalone (no container) Java application
- spring-jdbc-3.2.2 is being used for data access
- we're using Microsoft JDBC Driver 4.0 for SQL Server
- we're using this syntax: CALL SPROC_NAME(:PAR_1)
Any pointers on how remove this extra call are really appreciated. I haven't been able to turn on logging for the SQL Server driver so my next step is to try to debug the spring JDBC code.
Thanks,
MV
Obviously nowhere in our code do we make any such calls and no, we're not using any ORM framework that might be issuing them behind the scenes.
Here's our setup:
- Standalone (no container) Java application
- spring-jdbc-3.2.2 is being used for data access
- we're using Microsoft JDBC Driver 4.0 for SQL Server
- we're using this syntax: CALL SPROC_NAME(:PAR_1)
Any pointers on how remove this extra call are really appreciated. I haven't been able to turn on logging for the SQL Server driver so my next step is to try to debug the spring JDBC code.
Thanks,
MV