Find the real bottleneck
Every second of waiting is attributed to a category — disk, locking, memory, network, parallelism, log — so you argue from measurement, not instinct.
SQL Planner · Wait-Time Analysis
SQL Planner samples every active session once a second and turns it into wait-time analysis your whole team can read: which statement, which wait, which minute. One console for all four database engines, on-premise or in any cloud.
SQL Server · PostgreSQL · MySQL · Oracle
No agents on your servers · Read-only access · Setup in minutes
sqlplanner.app/wait-analysis
Wait time by category
Last 60 minutes
Top waiting statements
by wait timeSELECT … FROM Orders o JOIN … WHERE o.Status = @p
UPDATE inventory SET qty = qty − $1 WHERE …
SELECT /*+ … */ cust_id FROM payments WHERE …
SELECT COUNT(*) FROM sessions WHERE last_seen …
Monitors across
SQL Server 2012–2022 · PostgreSQL 10+ · MySQL 5.7 / 8.x · Oracle 11g–23c · On-premise · Azure SQL · Amazon RDS & Aurora · Google Cloud SQL · OCI
Why Wait-Time Analysis
Every second of waiting is attributed to a category — disk, locking, memory, network, parallelism, log — so you argue from measurement, not instinct.
The top 50 waiting statements are ordered by total wait time, so the query hurting people most is always at the top of the list.
Compare the same window before and after a change. The wait profile either dropped or it didn't — no interpretation required.
Features
One stacked chart for every server you monitor, whatever the engine. Click a bar to drill from a day, into an hour, into a five-minute slice — the statement list narrows with you.
sqlplanner.app/wait-analysis
Wait time by category
Last 60 minutes
Open any waiting statement and SQL Planner reads its execution plan for you — in the dialect of that engine — then says plainly what is wrong and what to try.
SQL Server plans render the way you already know them. PostgreSQL, MySQL and Oracle plans get the same treatment — a real operator tree, not a wall of text.
How It Works
1 sec
Sampling interval
0
Agents installed
Read-only
Permissions needed
4
Engines, one console
Built for the People Who Run It
A built-in wizard writes the exact CREATE USER and GRANT statements for your engine and hosting. Run them yourself, or let SQL Planner run them once with an admin login it never stores.
Passwords are encrypted at rest. Every server chooses its own SSL mode — none, required, or full certificate verification — and the collector honours the same setting.
A live page shows every server's last sample, hourly coverage and last error — so a collector that quietly stopped can't hide from you.
Adding a server runs a real connection test with that engine's own driver and checks it can read the monitoring views. A server that can't be monitored never gets saved.
Per-second samples roll up to the minute, then to the hour, then age out on a schedule you set. The repository stays fast without a maintenance ritual.
An ASP.NET web console and a Windows collector service, with a SQL Server repository. Your telemetry never leaves your network.
Complete Feature List
Questions
Wait-time analysis measures how long your database sessions spend waiting, and on what. Instead of reporting that CPU is busy or disks are slow, it attributes every second of delay to a specific SQL statement and a specific wait category — disk I/O, locking, memory, network and so on. Because it measures the delay users actually experience, it ranks work by real impact rather than by server-level symptoms.
SQL Server 2012–2022, PostgreSQL 10 and later, MySQL 5.7 and 8.x, and Oracle 11g–23c. Each is supported on-premise and on managed cloud services including Azure SQL Database and Managed Instance, Amazon RDS and Aurora, Google Cloud SQL, and Oracle Cloud. All four engines appear together in one console.
No. SQL Planner connects over the network like any other client and reads the session and statistics views your database already publishes. Nothing is installed on a monitored server, which is why it works unchanged on managed cloud services where you cannot install software.
Read-only rights, and nothing more: VIEW SERVER STATE on SQL Server, the pg_monitor role on PostgreSQL, PROCESS plus SELECT on performance_schema for MySQL, and SELECT_CATALOG_ROLE on Oracle. No access to your application tables is granted. A built-in wizard generates the exact statements for your engine and hosting, and can run them for you.
Very little. Each sample is a single indexed read of a session view once a second, and results are buffered in memory and written once a minute. Execution plans are captured with a plain EXPLAIN, which asks the optimiser for a plan without running the statement, and each statement is captured only once. In steady state, plan capture stops entirely until a new statement shape appears.
In a SQL Server repository that you own, on your own network. SQL Planner is self-hosted — an ASP.NET web console and a Windows collector service. No telemetry leaves your environment.
Trusted by teams that run critical database environments
Ready to stop guessing?
Request a demo or start free — and find the SQL that is actually waiting.