Start a query trace#

The query trace records the statements running through your connection as they happen, one row each. It is how you see what a query actually did: how long it took, whether it succeeded, and how many rows it touched. On a SQLite database this is the whole Query Log. On a server it is the Activity sub-view.

Capture does not run on its own. Select the play button to start it, and the trace fills as statements run. Select it again to pause. The toolbar keeps a running count of events. An empty trace prompts you to select play to begin.

Read a captured statement#

Each row shows the time the statement started and how long it took. It also shows the statement type, such as SELECT or INSERT, whether it finished OK or with an error, the number of rows, and the SQL itself. Select a row to open the Query detail panel beside the list. The panel shows the full statement and, on request, its execution plan.

Filter the trace#

The filter bar above the list keeps a busy trace readable. Filter by statement type, by status (OK or error), and by a free-text match on the SQL. A minimum duration filter surfaces only the slow statements. Filters apply to what is already captured as well as to new statements.

Export or clear the trace#

The export button saves the trace to a file, as JSON or as CSV depending on the extension you choose. The bin button clears the trace so you can start a fresh capture.