Apologies if this has been asked before, but is there a method of diconnecting idle connections to an OE database? We are trying to maximise the available licenses under our concurrent user allowance and all attempts to fix the humans (i.e. get them to log off the sytem at end of shift) have failed. Is there a way to disconnect them if there has been no activity for a preset time? Switching to Named User or Registered Client licensing is not currently an option due to excessive cost.
This applies to both ABL and SQLC conenctions. For ABL connections the users are just locking their screens and going home with the application logged in, sometimes with uncommitted transactions and open locks. For SQLC connections there are a few SSIS and SAS packages that are not disconnecting properly.
Ideally the solution would be run every hour on the data server disconnecting idle connections that have read or writtne to the database. I have looked through the VST tables and can determine the connection time from the _Connect table, but cannt find a field for last DBread or similar. How can I tell if the connection has been idle for a certain period of time?
Details: -
OE Enterprise 10.2B07 X64
Windows Server 2008 R2 X64
Regards
Andrew Bremner
This applies to both ABL and SQLC conenctions. For ABL connections the users are just locking their screens and going home with the application logged in, sometimes with uncommitted transactions and open locks. For SQLC connections there are a few SSIS and SAS packages that are not disconnecting properly.
Ideally the solution would be run every hour on the data server disconnecting idle connections that have read or writtne to the database. I have looked through the VST tables and can determine the connection time from the _Connect table, but cannt find a field for last DBread or similar. How can I tell if the connection has been idle for a certain period of time?
Details: -
OE Enterprise 10.2B07 X64
Windows Server 2008 R2 X64
Regards
Andrew Bremner