This is not just esoteric innards of SQL Server that can be easily dismissed. jdbc drivers follow the dblib pattern for implicit_transactions whereas ODBC/OLEDB does not. The latter also issues (when configured) "sp_reset_connection" that handles weirdness such as "dangling transactions" that sometimes occur due to deadlocking at the business tier. jdbc/dblib doesn't have the luxury of calling sp_reset_connection. Our application is having issues where some pooled connections have their implicit_transactions set incorrectly. It's been impossible to figure out where though. We would like to be able to monitor this with the DMV, but cannot since it handles these situations inconsistently.
Here is the attachment.