Those trace flags are reset by an implicit "EXEC sp_reset_connection" called every time you take a connection out of the pool.

See: https://github.com/dotnet/SqlClient/issues/767#issuecomment-...

"So, let's say you created a new pooled connection and closed it, driver will pool this connection but the physical connection is already active on server side. When the driver reactivates this pooled connection, it's only done on client side by taking it out of pool stack and setting it's state Active. But when next query is executed, we ensure a "RESET" bit is set in TDS header with next command on this newly reactivated pooled connection to cleanup any stale state, as per standard behavior."

Oracle requires an opt-in(!) flag that is incomplete and configured on the server instead of the client, which is a "special" kind of nonsense that I have no patience for: https://docs.oracle.com/en/database/oracle/oracle-database/2...