Hi,



Every now and again a long running transaction will occur (a poorly
written query by a junior technical team member for example). In these
examples the cpu time is being maxed out for long long periods and when
customers get busy this action still being run can degrade performance
slightly.



Is there anyway till identify this transaction and kill it inside the
server engine ? in either current versions of within the new FB 2
development ? ( I think IB 7.0 upwards contains this feature and I think
it would be very beneficial).



Just a question, currently the only way to kill it is get everyone out
of the system and restart the firebird server, which is not exactly
ideal for customers..



Thanks



Mart



[Non-text portions of this message have been removed]