We have noticed a strange behavior with an application that uses the Microsoft JDBC 4.0 driver, we are unsure if its the application or the driver. This application makes use of the sp_prepexec function for all of the queries. What we are seeing is the application passes the sp_prepexec through to sql, sql executes & returns the results then we se a sp_unprepare almost right away. Annoying we see the exact same query come in a millisecond late and it goes through the same prep and de-prep process every time.
We where wondering if it is the driver that is issuing the de-prep statment, or would that have to be initiated from the application? While vendor is suggesting that it is not their application doing this, I have my doubts due to the half hearted response.