Chapter 9: DBA Suite & Server Health
Info: This chapter explains the live process list, safe methods for terminating queries/connections, and the server health scan. These are server administration tools and are unavailable for SQLite connections.
In this chapter:
9.1 Live Process List & Safe Termination
To monitor which user is running which query on the server and how long it has been locked, follow these steps.
- Open the Tools → Processlist panel from an active MySQL, MariaDB, or PostgreSQL connection.
- Choose an auto-refresh interval (1, 3 or 5 seconds).
- Filter out sleeping connections in the
Sleepstate and inspect only the active queries.
Right-clicking a process offers two termination options:
- Kill Query (safe): Terminates only the query while keeping the session open.
- Kill Connection: Fully closes the connection at the server level.
Important: Kill Connection also ends any open transactions in the session. Use Kill Query if you only need to stop the query.
Tip: For detailed lock-tree and root-blocker analysis, see Chapter 18: OzLockTree - Lock Resolver.
9.2 Server Health Scan & Security Linter
Run an automatic scan to find the checks exposed by the connected server. Results include provenance and can report permission failures; a missing fact is not treated as a healthy value.
- Run Tools → DB Check-Up Wizard….
- The scanner inspects the server settings:
- Is the Buffer Pool RAM ratio optimal?
- Are there user accounts left open without a password?
- Is the maximum connection limit being approached?
- Review the checks, score, and recommendations. Checks are vendor and permission dependent, so an unavailable check remains visible as unavailable rather than being treated as a pass.
