Hi!
There are cases for database servers in general:
- incorrect end of connection is suspending user process on a database server;
- a process is active, but this process is blocking other important processes with
locks;
- process is executing a query that is using necessary system resources.
In ideal, system should trace such processes and close them itself, however
some database servers
(MS SQL for example) give such opportunity to admin too (T-SQL --> KILL {spid}).
For SAP DB:
- Is there such opportunity?
- Can developer program monitor and forcibly detach individual client connections?
Konstantin Karpov
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
