Sept 5, 2025
| Description: Users are leaving their "Run SQL Scripts" sessions open for an extended period of time. | ||
| Although there is a configurable option to "automatically close cursor to release locks", | ||
| this does not disconnect the session. This can present a security risk if physical access | ||
| to the connected workstation is compromised. | ||
| How can we use SQL to identify ODBC/JDBC connections that have been idling for a long time | ||
| and proactively disconnect them? |
@Steve Riedmuller of KISCO Systems has a Gist Site containing SQL code that can assist you with this task. His Gist site can be found here. | |
