Culprit SQL Studio - Pinpoints the costly query dragging your database down

Read access to the server's statistics. SQL Server needs VIEW SERVER STATE (VIEW DATABASE STATE on Azure SQL Database). PostgreSQL needs pg_read_all_stats or pg_monitor. MySQL and MariaDB need PROCESS and SELECT on performance_schema. When a check can't run with your login, Culprit names the exact grant that unlocks it

No. There's no agent or collector: Culprit connects like any client and reads the statistics the database already keeps (Query Store, pg_stat_statements, performance_schema). If one of them is switched off, it shows the one statement that turns it on.

No. Scans only read statistics and catalog views. The SQL editor runs reads read-only, and anything that could change data on a production connection asks you first. Suggested fixes are shown, never applied.

It's an investigation tool: open it when something is slow, or let your coding agent ask it. History comes from Query Store and from Culprit's own saved scans, so there's no server to run and nothing collecting around the clock.

Yes. Azure SQL Database and Amazon RDS for PostgreSQL are tested, Entra ID sign-in uses your az login, and Culprit can find your Azure and AWS databases with your existing CLI login.

Those show the numbers. Culprit reads them for you: it ranks what costs the most time, explains it in one sentence, gives the fix and tells you how to verify it, with the same views on all four engines.