How dbtempo analyzes a query | Docs

Detect, analyze, and fix

Detect

Identify a query pattern and inspect the query text, workload statistics, schema, indexes, and execution plan that are available for it.

Analyze

Turn the supporting artifacts into a diagnosis, confidence level, evidence, expected impact, and risk notes.

Fix

Propose a concrete next step such as migration SQL, suggested SQL, a query rewrite, a configuration change, or manual investigation.

What uses your allowance

Credits pay for the written analysis: the explanation of a finding and its proposed fix. The current share of the monthly allowance is shown in Settings → Usage.

Missing context

A ready database can add schema, index, statistics, and execution-plan context. If a required artifact is missing, the thread asks you to attach a connection, run a displayed read-only statement yourself, or continue with the context that is already available.

By default, automated plan probes read the plan without running the query. On PostgreSQL a probe uses EXPLAIN ANALYZE, which does run it, only after a project owner turns on query execution for that project. Source indexing can add call-site evidence when a connected source is available.

What the result means

A completed analysis may create a durable recommendation or report that the available evidence did not reveal an issue. Treat each recommendation as a reviewable engineering decision: read its evidence, fix zone, risk notes, and rollback guidance before acting.

Detect, analyze, and fix

Detect

Identify a query pattern and inspect the query text, workload statistics, schema, indexes, and execution plan that are available for it.

Analyze

Turn the supporting artifacts into a diagnosis, confidence level, evidence, expected impact, and risk notes.

Fix

Propose a concrete next step such as migration SQL, suggested SQL, a query rewrite, a configuration change, or manual investigation.

Missing context