These screens show the sessions connected to the database server now, the locks blocking each other, the status statistics the server has collected, and the server settings. You can cancel a long-running query, end a session and change a server setting. All four screens have the same structure as the Object tabs, and they run statements directly on the database server.
What's on the screen
| No. | Name | Description |
|---|---|---|
| 1 | Title | The screen name and the connection name. |
| 2 | Refresh and auto refresh | The Refresh button reads the list again. Session Manager and Lock Manager have an auto refresh switch on its right (see 'Auto refresh' below). |
| 3 | List | One session, lock, statistic or setting per row. Type in the Filter objects... field above it to filter. Click a row to open its details below. |
| 4 | Detail buttons | The Cancel Query and Kill Session buttons for the selected session, and the Save button that writes edited values. Only those the DBMS supports appear. |
| 5 | Details | The fields of the selected row. Fields for which the DBMS gives no value are hidden. |
| 6 | Detail tabs | Information attached to the selected row, such as the Active Query tab of Session Manager. |
- Drag the border between the list and the details to change their heights, and double-click the border to collapse or expand the list.
- Global Status shows only the list, without details.
Opening a screen
- In the explorer, expand a connection and then its Server Objects item.
- Double-click the Session Manager, Lock Manager, Global Status or server settings item. That screen opens as a work document tab.
The server settings item is named the way each DBMS names it. The screens available per DBMS are as follows. SQLite does not have these screens.
| DBMS | Session Manager | Lock Manager | Global Status | Server settings |
|---|---|---|---|---|
| MySQL, MariaDB | Yes | Yes | Yes | Global Variables (editable) |
| PostgreSQL | Yes | Yes | Yes | Configuration (editable) |
| Oracle | Yes | Yes | Yes | System Parameters (editable) |
| SQL Server | Yes | Yes | Yes | Server Configuration (editable) |
| H2 | Yes | No | Yes (file databases only) | Settings (read-only) |
These screens read the server's system views. If the connected database account is not allowed to read them, the list is empty or a permission notice appears (for example SELECT_CATALOG_ROLE in Oracle and VIEW SERVER STATE in SQL Server).
Viewing and ending sessions
Session Manager lists the sessions connected to the server. The list's fields follow the DBMS's session view (SHOW PROCESSLIST in MySQL, pg_stat_activity in PostgreSQL). In MySQL and MariaDB, the session of a SQL editor tab with Auto Commit turned off has the My Session mark. Other DBMSs do not show this mark.
| Detail tab | When it appears | Content |
|---|---|---|
| Active Query | Always | The SQL the session is running now. It is empty for an idle session. |
| Session Status | Oracle and SQL Server. MySQL, MariaDB and PostgreSQL 18 or later when you may read the source | Cumulative counters per session. They are read when you click the tab. |
| Session Variables | MySQL 5.7.6 or later, Oracle and SQL Server | The settings in effect for the session. For a session with the My Session mark, edit the changeable values in place and write them with the Save button. |
| Long Operations | Oracle | The session's long-running operations. |
- Click a session in the list.
- Click the Cancel Query or Kill Session button.
- In the SQL Preview window, check the statement and the target session number, and click the Execute button. The list is read again.
| DBMS | Cancel Query | Kill Session |
|---|---|---|
| MySQL, MariaDB | KILL QUERY | KILL CONNECTION |
| PostgreSQL | pg_cancel_backend | pg_terminate_backend |
| Oracle | ALTER SYSTEM CANCEL SQL. The button appears only on 18c or later | ALTER SYSTEM KILL SESSION … IMMEDIATE |
| SQL Server | None | KILL |
| H2 | CANCEL_SESSION | None |
- The Cancel Query button stops only the running statement and keeps the session. The Kill Session button disconnects it, and the database rolls back that session's uncommitted transaction.
- In the SQL Preview window, the Open Editor button moves the statement to a SQL editor and the Copy SQL button copies it.
Viewing locks
Lock Manager lists the locks on the server now. A lock that blocks or waits for another session has a status mark, and a deadlock has the Dead Lock mark.
- Click a lock with a status mark. Below it, the blocking sessions (1) and the waiting sessions (2) appear side by side, each with the SQL it is running.
- Check the sessions to end.
- Click the Cancel Query or Kill Session button (3) above them, check the SQL Preview window and run it.
- Click a session number in the list to open that session in Session Manager.
- The blocking and waiting sides are shown only for a conflicting lock. Other locks show only their detail fields.
- SQL Server has no Cancel Query button.
Auto refresh
Session Manager and Lock Manager can read their lists again at a set interval.
- Turn on the switch to the right of the refresh button. It starts off, and the default interval is 5 seconds.
- Click the text next to the switch to set the interval (seconds) and whether to stop on errors. The interval is saved on this device.
- The time of the last read appears next to the switch. Nothing is read while you are looking at another project or the window is hidden.
Viewing server status and settings
Global Status shows the statistic counters the server has collected since it started, as names and values. It is read-only. The source differs per DBMS.
| DBMS | Source |
|---|---|
| MySQL, MariaDB | SHOW GLOBAL STATUS |
| PostgreSQL | Selected values from pg_stat_database (summed over all databases), pg_stat_bgwriter and pg_stat_archiver |
| Oracle | V$SYSSTAT |
| SQL Server | Server-level counters of sys.dm_os_performance_counters |
| H2 | info.* rows of INFORMATION_SCHEMA.SETTINGS. Empty for an in-memory database |
The server settings screen shows each setting's name, current value, default, when it can be changed (Context) and where its value comes from (Source). Fields the DBMS does not provide are empty.
- Click a setting in the list.
- Edit the Value field in the details. The field is locked for settings the server does not let you change.
- Click the Save button, check the statement in the SQL Preview window and run it.
| DBMS | Statement that runs |
|---|---|
| MySQL, MariaDB | SET GLOBAL name = value |
| Oracle | ALTER SYSTEM SET name = value SCOPE=…. A setting that cannot change immediately uses SCOPE=SPFILE and takes effect from the next startup |
| SQL Server | EXEC sp_configure followed by RECONFIGURE |
| PostgreSQL | Choose in the Apply to field of the preview window. Cluster-wide (ALTER SYSTEM) runs ALTER SYSTEM SET followed by pg_reload_conf(), and This session (SET) runs SET |
Things to keep in mind
- What you run on these screens happens on the server right away, with no save or apply step. There is no undo button.
- Ending a session rolls back its uncommitted transaction. You can also end the session of a NeoSQL SQL editor tab (the My Session mark), so on a production database check the target session's user and running SQL before you run it.
- Changing a server setting affects every connection to that server. MySQL's
SET GLOBALis lost when the server restarts. - PostgreSQL's This session (SET) applies to the connection this screen uses to read the server, not to the session of a SQL editor tab.
- The list shows the state when it was opened or last read. Read it again with the Refresh button before ending a session.
- In a signed-in account project, a member whose DDL execution is restricted cannot run statements in the SQL Preview window (You do not have permission to execute DDL.).
- The web app connects to databases from the server, so it sees only databases open to the internet. See Connections and execution targets.
Related screens
- Object explorer: the tree with the Server Objects item.
- Object tabs: list and detail screens with the same structure as these screens.
- SQL execution and transactions: how SQL editor tabs, database sessions and transactions relate.
- Dashboards: watch the database's state with tiles.