Yeah, that's exactly what I'm looking for. I don't know what tool the other team is using, I do believe that it's an ODBC connection. I just know that the tables that the service account has access to are all read only. If they have a process that is starting a transaction, i want it to fail/return an error to them. They cannot write to any tables, so they shouldn't be able to start a transaction.
we have an external system that is querying the data via SQL (ODBC/JDBC). The tool that's being used on the other server was built to start a transaction (TSTART) before the query runs. The query only reads data and the service account has read only access to the tables in the database. the problem is that it keeps starting the transaction.
I can't stop the other process from starting a transaction, but i need its request to start a transaction to fail.
Though I don't agree that the why is relevant (since none of the tables that the service account has access to are able to be written to), i would suspect that it's a system setting or a default value somewhere in their tool that tells it to automatically send a TSTART.
I've been told that the 3rd party system that's querying our InterSystems database does NOT start a transaction, but clearly it is, evidenced by the console message that the transaction for that process has been open for more than 20 minutes. I don't have access to their system to help them find it. And they'd be fine if we can lock out their ability to start a transaction (ie, make everything read only for that service account). Unfortunately, I've only been able to make the tables read only and not everything. Make sense?